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

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: after_ssl: - replace: filename: "/etc/runit/1.d/letsencrypt" from: /--keylength/ to: "-d second-domain.com -d www.second-domain.com -d other-domain.com -d www.other-domain.com --keylength" This will allow you to have HTTPS configured for a second domain th…

and

Redirect additional domain(s) to your Discourse instance

So you want to redirect domain(s) to your Discourse instance? Great, let’s get started! In this tutorial we’ll show how to redirect www.example.com and example.com to talk.example.com. Update DNS Record Update the A record for the domain(s) you want to redirect to original domain. Edit Configuration FIle Open configuration file app.yml. From console, run these commands: cd /var/discourse git pull nano containers/app.yml Configuration file will open in nano editor. Search for hooks (with C…