Workaround for the 1 week Let's Encrypt limit

[tmc1]

Hey guys!

I’m trying to installing Discourse and website is not loading after some rebuilds because of:

Duplicate Certificate Limit - Let's Encrypt

Is there any way to request a new different sets of domains as the workaround explains to bypass the limitation and not have to wait 1 entire week? I’m deploying in Ubuntu Vultr.

Thanks

[tmc1]

For now, I’ve tried to do a rebuild using a subdomain and see if now works.

If I want to switch back to the domain I just do a rebuild again? It auto-updates all permalinks and so?

Because I guess I can’t keep both if desired, right?

Thanks a lot

[itsbhanusharma (Bhanu Sharma)]

Please See:

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. There are two patterns that need to be replaced, one ending in --keylength, and another ending in --fullchainpath (in the actual file, your original domain is before each of these switche…

and

Redirect additional domain(s) to your Discourse instance

2024-04-09 This guide is outdated according 2024-04-09 @pfaffman edited this to say that this is no longer necessary, as the current NGINX config in the standard install redirects everything to https://HOSTNAME. You can test this by entering your IP address and see that it gets redirected. If you want multiple domains pointed to your server, you probably want them to have valid https certificates. To do that, follow instructions at Set up Let’s Encrypt with multiple domains / redirects. Origina…