# Installation without subdomain not working **URL:** https://meta.discourse.org/t/installation-without-subdomain-not-working/241399 **Category:** Self-hosting **Created:** [October 9, 2022, 1:54pm UTC](https://meta.discourse.org/t/installation-without-subdomain-not-working/241399 "2022-10-09T13:54:39Z") **Posts on this page:** 1 **Showing post:** 19
### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma) #### Post date: [October 10, 2022, 5:02am UTC](https://meta.discourse.org/t/installation-without-subdomain-not-working/241399/19 "2022-10-10T05:02:03Z")
If you’ve tried rebuilding more than a couple times, You probably might be getting rate-limited by letsencrypt. You can workaround this by adding another hostname to your cert. > [@Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains/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… --- _[View the full topic](https://meta.discourse.org/t/installation-without-subdomain-not-working/241399)._