# Issues with an Azure install (need to configure inbound ports)

**URL:** <https://meta.discourse.org/t/issues-with-an-azure-install-need-to-configure-inbound-ports/51614>\
**Category:** Product Support\
**Created:** [2016 年10 月 16 日 21:14 UTC](https://meta.discourse.org/t/issues-with-an-azure-install-need-to-configure-inbound-ports/51614 "2016-10-16T21:14:28Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

作者： ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
发布日期： [2017 年2 月 21 日 14:14 UTC](https://meta.discourse.org/t/issues-with-an-azure-install-need-to-configure-inbound-ports/51614/13 "2017-02-21T14:14:38Z")

</div>

OK, here’s the report:

I created a DS1\_V2 (~$55/month) virtual machine running Ubuntu 16.04 LTS. I did

```
wget -qO- https://get.docker.com/ | sh
apt -y upgrade
./discourse-setup

```

It worked just fine.

> [@daveisbludging](#):
>
> When I connect to the IP address or URL I get a ERR\_CONNECTION\_TIMED\_OUT.

Oh. You see? I knew there would be head banging. Turns out, not being able to access your machine is a feature, not a bug. You need to open the ports, like [this](https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-nsg-quickstart-portal).

Once I managed to convince Azure to open port 80 so that one could access it via a web browser, I enabled Let’s Encrypt and rebuilt. That worked too. (And to make sure that there was no outbound filtering, I sent an activation message with Mailgun. No shenanigans were required.).

[https://azure.ltcmp.net/](https://azure.ltcmp.net/)

---

_[View the full topic](https://meta.discourse.org/t/issues-with-an-azure-install-need-to-configure-inbound-ports/51614)._