# Lets Encrypt Certificate - Issuing Problem
**URL:** https://meta.discourse.org/t/lets-encrypt-certificate-issuing-problem/284503
**Category:** Self-hosting
**Created:** [November 5, 2023, 8:38pm UTC](https://meta.discourse.org/t/lets-encrypt-certificate-issuing-problem/284503 "2023-11-05T20:38:47Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Timelord](https://meta.discourse.org/u/Timelord)
#### Post date: [November 5, 2023, 8:38pm UTC](https://meta.discourse.org/t/lets-encrypt-certificate-issuing-problem/284503/1 "2023-11-05T20:38:47Z")
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](https://meta.discourse.org/t/cant-connect-to-discourse-install/266848):
>
> 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?
---
### Author:  [@Timelord](https://meta.discourse.org/u/Timelord)
#### Post date: [November 6, 2023, 1:01pm UTC](https://meta.discourse.org/t/lets-encrypt-certificate-issuing-problem/284503/2 "2023-11-06T13:01:18Z")
So, it looks like this issue was actually with Lets Encrypt. I had hit the [weekly limits](https://letsencrypt.org/docs/rate-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.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [November 6, 2023, 3:05pm UTC](https://meta.discourse.org/t/lets-encrypt-certificate-issuing-problem/284503/3 "2023-11-06T15:05:12Z")
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](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685):
>
> NOTE: @pfaffman says: This page needs to be cleaned up. There is now a new ENV setting that will let you add more hostnames. In your app.yml under your DISCOURSE\_HOSTNAME line (it can go many places but that one makes sense), add DISCOURSE\_HOSTNAME\_ALIASES: domain.com,other.domain.com and early reports suggest that you’ll get valid certs for those domains and that accessing https://domain.com will properly redirect you to your DISCOURSE\_HOSTNAME without a certificate error. If you do that an…