I’ve got the following message: Port 443 of computer does not appear to be accessible using hostname mydomain
When I modify manually the /containers/app.yml I succeed to install correctly discourse only with http but I doesn’t work when I try to open it with https
I get the following message with https:
This site is inaccessible
mydomaine does not allow connection.
Discourse-setup does a rather crude test to see that it’s possible to connect to itself with curl and your hostname. It seems like something is keeping lets encrypt from connecting to the server. If you rebuild enough times time hit rate limits that will keep you from getting a certificate for a week
@pfaffman no reverse proxy. I have installed nothing I just followed tu user install.
sudo systemctl status nginx
Unit nginx.service could not be found.
My only other guess is that your VM has port 443 blocked at the network level (before it gets to your VM). You can check with your VM provider to see if it’s blocked somehow. If it’s AWS then you need to muck with security levels, I think.
Can you provide us the exact configuration of your server, with the option you opted-in?
I rent a a VPS at OVH and I know they propose a bunch of stuff to be checked in or out.
@Canapin, you will find my configuration below:
Model: VPS vps2020-value-1-2-40
Vps with linux distribution
Boot: LOCAL
OS / Distribution: Ubuntu 22.04
Zone: Region OpenStack: os-sbg8*
Memory 2GO SSD NVMe
Storage 40GO
I might leave this topic to more experienced users (I’m just a random passerby ), but by chance do you have any other web software running on your VPS?
I have lauched no other software on my VPS. I get a VPS especialy to set up my Discource. But I don’t know if OVH launch something on the VPS. How can I know ?
Could it be your misconfiguration?
Discourse programs can use HTTPS
Check the templates item “templates/web.ssl.template.yml” in app.yml for the introduction of template files; Next, you have to check the expose entry - “443:443” # https
Whether the template is enabled