# Discourse installation on Azure not reachable

**URL:** <https://meta.discourse.org/t/discourse-installation-on-azure-not-reachable/36880>\
**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:** 1

<div class="post-metadata">

**Author:** ![Abhay\_Ghatpande](https://avatars.discourse-cdn.com/v4/letter/a/0ea827/32.png) [@Abhay\_Ghatpande](https://meta.discourse.org/u/Abhay_Ghatpande)\
**Post date:** [December 18, 2015, 7:14am UTC](https://meta.discourse.org/t/discourse-installation-on-azure-not-reachable/36880/1 "2015-12-18T07:14:07Z")

</div>

I created a new Ubuntu 14.04 VM on Microsoft Azure and installed Discourse using the guide here: [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)

The entire installation went perfectly, but the instance is not reachable publicly. I have the A record configured to the public IP given by Azure. I also tried using the IP address directly.

I suspect this has something to do with the Docker IP and the Eth0 IP address, but not sure how to solve it.

```plaintext
# ifconfig
docker0 Link encap:Ethernet HWaddr 02:42:4c:29:e0:92  
          inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
          inet6 addr: fe80::42:4cff:fe29:e092/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:6144 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21683 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:414603 (414.6 KB) TX bytes:30771613 (30.7 MB)

eth0 Link encap:Ethernet HWaddr 00:0d:3a:00:15:21  
          inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0
          inet6 addr: fe80::20d:3aff:fe00:1521/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1079091 errors:0 dropped:0 overruns:0 frame:0
          TX packets:634212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1254465906 (1.2 GB) TX bytes:318586926 (318.5 MB)

lo Link encap:Local Loopback  
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:7245 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7245 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:986455 (986.4 KB) TX bytes:986455 (986.4 KB)

vethcb56e42 Link encap:Ethernet HWaddr 6a:43:07:bb:63:3f  
          inet6 addr: fe80::6843:7ff:febb:633f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2717 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2896 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:225111 (225.1 KB) TX bytes:3277314 (3.2 MB)

```

So essentially I have 3 IPs: the public IP, the eth0 IP on the VPN, and then the docker instance IP. I’m guessing I need to somehow route the public IP:80 port to the docker IP?

Please help. Thank you.

---

_[View the full topic](https://meta.discourse.org/t/discourse-installation-on-azure-not-reachable/36880)._