mtu 1500 qdisc noqueue m aster docker0 state UP group default
link/ether 5a:da:8a:f7:b4:37 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::58da:8aff:fef7:b437/64 scope link
valid_lft forever preferred_lft forever
```
---
### Author:  [@schungx](https://meta.discourse.org/u/schungx)
#### Post date: [October 13, 2017, 2:35am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/3 "2017-10-13T02:35:10Z")
Does the site work WITHOUT SSL?
I have Discourse on an Azure Ubuntu VM and it worked like a charm with no hassles.
First set it up WITHOUT Lets Encrypt. Make sure that you can access the site over straight HTTP.
Then modify `app.yaml` to include Lets Encrypt and rebuild.
From your error messages, it looks like you have not opened the EndPoint to the public IP address. That’s why Lets Encrypt is not finding the public IP.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 13, 2017, 2:35am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/4 "2017-10-13T02:35:47Z")
Are you saying that [http://your](http://your) [host.com](http://host.com) doesn’t work for your hostname?
---
### Author:  [@CyberSathya](https://meta.discourse.org/u/CyberSathya)
#### Post date: [October 13, 2017, 2:38am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/5 "2017-10-13T02:38:33Z")
I’m saying that the discourse site works ONLY from local host (127.0.0.1:8000), when tunneling is done with PuTTy, and not from the Virtual Machine’s IP Address. Infact, I’m not able to figure-out how to run Discourse outside local host.
---
### Author:  [@CyberSathya](https://meta.discourse.org/u/CyberSathya)
#### Post date: [October 13, 2017, 2:39am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/6 "2017-10-13T02:39:25Z")
> [@schungx](#):
>
> it looks like you have not opened the EndPoint to the public IP address.
Mind letting me know how to do that? Thanks in advance. That’s where i’m stuck.
---
### Author:  [@schungx](https://meta.discourse.org/u/schungx)
#### Post date: [October 13, 2017, 2:41am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/7 "2017-10-13T02:41:41Z")
Scratch your VM, start a new one, do it vanilla without other configurations.
You can add your configuration changes later on and rebuild.
And, do yourself a favor, use the fastest CPU VM you can afford during setup. It should only be a few days, but it saves you heaps of time waiting for a rebuild (which can take up to 15 min).
And do not go below 2GB of RAM, thus do not use things like A0.
---
### Author:  [@CyberSathya](https://meta.discourse.org/u/CyberSathya)
#### Post date: [October 13, 2017, 2:56am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/8 "2017-10-13T02:56:24Z")
> [@schungx](#):
>
> it looks like you have not opened the EndPoint to the public IP address. That’s why Lets Encrypt is not finding the public IP.
I was able to find inbound port rules in Azure Settings, and I enabled TCP/443 and TCP/80.
Thanks a lot.
---
### Author:  [@CyberSathya](https://meta.discourse.org/u/CyberSathya)
#### Post date: [October 13, 2017, 3:08am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/9 "2017-10-13T03:08:31Z")
I’m able to reach the site via domain name now, after port forwarding 443 & 80.
How do we go with SSL now?
rerunning discourse-setup is getting this error.
> Checking your domain name . . .
> WARNING:: [forum.vaaithaa.com](http://forum.vaaithaa.com) does not appear to resolve to 10.0.0.4.
>
> LET’S ENCRYPT cannot work if their servers cannot access your host by name.
> Unless you think you know why this naive check failed, DO NOT USE Let’s Encrypt.
> (A typical reason for failure is an AWS server with an elastic IP.)
>
> You should probably answer “n” at the next prompt and disable Let’s Encrypt.
---
### Author:  [@schungx](https://meta.discourse.org/u/schungx)
#### Post date: [October 13, 2017, 3:10am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/10 "2017-10-13T03:10:48Z")
How do you have an ANAME when you’re using a dynamic public IP? You should be using a static public IP for that, right?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 13, 2017, 3:21pm UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/11 "2017-10-13T15:21:53Z")
> [@CyberSathya](#):
>
> Unless you think you know why this naive check failed, DO NOT USE Let’s Encrypt.
>
> (A typical reason for failure is an AWS server with an elastic IP.)
You’ve demonstrated that you know that the address used to access your host is not 10.0.0.4, so it would seem that _you know why this naive check failed_.
Still, this remains confusing to people and the set of people who are confused by this naive check is growing, especially with people increasingly using Azure.
I’ll try to either make the check more robust or tone down the language to make it less scary sometime soon.
---
### Author:  [@CyberSathya](https://meta.discourse.org/u/CyberSathya)
#### Post date: [October 13, 2017, 3:26pm UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/12 "2017-10-13T15:26:40Z")
I sincerely look forward for a tone-down. Thanks for sharing your knowledge via this community.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [October 13, 2017, 10:42pm UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/13 "2017-10-13T22:42:42Z")
> [@CyberSathya](#):
>
> (A typical reason for failure is an AWS server with an elastic IP.)
@pfaffman you can just add Azure to this text if Azure does things this way too? Very simple fix.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 13, 2017, 10:45pm UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/14 "2017-10-13T22:45:52Z")
I’ve used `nc` and `curl` to check whether [http://hostname](http://hostname) and [http://hostname:443](http://hostname:443) actually connect to that host. I think they’ll give fewer false fails on the check and the “it’s broken” language is toned down a bit.
Done!
[https://github.com/discourse/discourse\_docker/pull/380](https://github.com/discourse/discourse_docker/pull/380)
---
### Author:  [@schungx](https://meta.discourse.org/u/schungx)
#### Post date: [October 14, 2017, 7:31am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/15 "2017-10-14T07:31:00Z")
Yup, Azure has an option to use dynamic public IP’s which change periodically.
My public IP is static (meaning fixed IP), which doesn’t seem to trigger this warning.
But does Let’s Encrypt support dynamic IP’s? If it does, then it should be fine.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:44pm UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/17 "2024-06-08T12:44:10Z")
This topic was automatically closed after 2430 days. New replies are no longer allowed.