# After Discourse installation can’t reach it in browser

**URL:** <https://meta.discourse.org/t/after-discourse-installation-can-t-reach-it-in-browser/106887>\
**Category:** Self-hosting\
**Created:** [18 januari 2019 om 09:30 UTC](https://meta.discourse.org/t/after-discourse-installation-can-t-reach-it-in-browser/106887 "2019-01-18T09:30:19Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![paulraines68](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/paulraines68/32/233905_2.png) [@paulraines68](https://meta.discourse.org/u/paulraines68)\
**Post date:** [3 september 2020 om 03:11 UTC](https://meta.discourse.org/t/after-discourse-installation-can-t-reach-it-in-browser/106887/12 "2020-09-03T03:11:59Z")

</div>

Just wasted hours on this myself. The install instructions at [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) imply if you just hit enter at the Let’s Encrypt line it gets skipped. But it doesn’t. It still sets up things to use a SSL cert it cannot get at email [me@example.com](mailto:me@example.com)

One has to then go into app.yml, comment out the Let’s Encrypt email line and the ssl templates and then launcher rebuilt. I think this should be considered a bug in the discourse-setup. Also discourse-setup should have support for installing your own SSL cert gotten from another authority right at the beginning so you don’t have to rebuild.

---

_[View the full topic](https://meta.discourse.org/t/after-discourse-installation-can-t-reach-it-in-browser/106887)._
