# Discourse installation on Azure not reachable **URL:** \ **Category:** Self-hosting\ **Created:** [December 18, 2015, 7:14am UTC](https://meta.discourse.org/t/discourse-installation-on-azure-not-reachable/36880 "2015-12-18T07:14:07Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\ **Post date:** [August 16, 2021, 2:08pm UTC](https://meta.discourse.org/t/discourse-installation-on-azure-not-reachable/36880/10 "2021-08-16T14:08:29Z")
> [@toraritte](#): > > Everything installs beautifully Discourse-wise, all seems fine, but ports 80 and 443 are publicly unreachable. `discourse-setup` should fail if you don’t have ports 80 and 443 open to inbound traffic. > [@toraritte](#): > > The first time I realized I had no swap, and even though the `discourse-setup` script sets it up if missing, I exited to shell to check stuff. Then some of install prompts were different than in [the basic guide](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md), so exited one more time. Ah. That’s true. Some of the questions about email configuration were changed a while back and not changed in the guide. I think most people read the prompts and not the install document, so no one else has complained. > [@toraritte](#): > > was under the impression that I would have to set up HTTPS manually. Why did you think that? The install process has automatically set up let’s encrypt for years. I can’t tell if you’re saying that your site is working or not working. If it’s not working, it’s a good bet that you ran discourse-setup a bunch of times and used up your rate limit at [letsencrypt.org](http://letsencrypt.org). --- _[View the full topic](https://meta.discourse.org/t/discourse-installation-on-azure-not-reachable/36880)._