Lets Encrypt Certificate - Issuing Problem

[Timelord]

Hey gang.
Brand new install on Ubuntu 22.04. I am running into the EXACT same error as found in this thread.

Can't connect to discourse install

Trying to fresh install discourse on bare metal OVH server running Fedora Server 38 and installation went fine but I cannot connect to it using the hostname I specified in the app.yml forums.dogsrv.dev. OVH edge firewall is disabled, firewalld is disabled, iptables is disabled, DNS resolves fine, I’m lost at what else to check at this point, any ideas would be appreciated.

I edited discourse-setup, to remove the -p, however the issue persists. Any ideas here?

[Timelord]

So, it looks like this issue was actually with Lets Encrypt. I had hit the weekly limits of them issuing certs to my domain.

I tested on a subdomain, and it worked without issue. Now, I just need to wait until the timeout resets.

[JammyDodger]

There is a workaround where you can add multiple if you didn’t want to wait?

Set up Let’s Encrypt with multiple domains / redirects

This is to address the problem where you get certificate errors with any redirects or CNAME DNS entries which point to your actual installed Discourse (sub)domain. If you do not have https configured already (you do if you have done a standard install recently) see Setting up Let’s Encrypt as your first step. Add something like the following to your app.yml hooks section (towards the end of the file): after_ssl: - replace: filename: "/etc/runit/1.d/letsencrypt" from: /-d…