• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

    • ⚠️ Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • ✅ Confirm that the server meets the System Requirements
    • 🔥 Check for any available Hotfix - your issue could be already reported/fixed
    • 📚 Read documentation - It will be required to Debug and understand Errors for a faster support response

Unable to enable HTTPS

W

willdenham

Chevereto Member
Looking for a bit of help, and excuse me for knowing just enough about Linux to be dangerous and certainly not enough to figure my way out of this one.

I am running an Ubuntu 22.04 LTS server with a totally fresh install, updated/upgrade right after install and rebooted.

I ran the prepare.sh from the VPS area on Chevereto's github, rebooted after successful install.

I ran the new.sh from the VPS area as well, and it installs just fine. I can access my site both internally and externally via the URL on HTTP (running nginx proxy manager).

As soon as I want to enable SSL/HTTPS, either through the command found on github or through NPM I run into a total roadblock (which has lead me to fully reinstalling the OS a few times to make sure I'm not mucking things up with settings). On my latest install I've only ran the below and yes I entered my own URL (again, this URL works externally via HTTP confirmed)

certbot --apache -d example.com -d example.com
Click to expand...
I get the below response from this command
Domain: www.REDACTED.com
Type: unauthorized
Detail: IPREDACTED: Invalid response from http://REDACTED.com/.well-known/acme-challenge/515rR07abGh_fTS4mwkQJWBegiz5hKs4uacu025me3Q: 404

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.
Click to expand...

I would humbly appreciate if someone could tell me what on earth I'm doing wrong here. Did I skip a step along the way?
 
Did you point the domain names to the IP? Note that if you want to use www you also need to point www.domain.ext to the server IP.

HTTPS provisioning is on certbot, you should focus there. No need to re-do the entire process.
 
So that is the oddest part about this. Yes the domain is both internally and publicly reachable by the domain name. DNS resolves properly no matter how I look at it. I have records for a wildcard on the domain and www

I'll dig more into certbot today.

Is it normal behavior that https://serverIPhere:443 does not work without that as well? I typically would get a notice about the site being insecure, but I'm getting ERR_CONNECTION_REFUSED when visiting that internally on the same network. UFW does have 443 listed as open and permissible anywhere however.

Thanks again.
 
It is hard to tell without the domain, and in my experience http setup with certbot is usually a 2 minute process.

The only issues I ever had was when I used .dev domains which must be always https. For these domains you need old recipe or use CloudFlare and once https do the cerbot thing.
 
You must log in or register to reply here.
Back
Top