# Let's Encrypt: Azure hostname issue

**URL:** <https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972>\
**Category:** Self-hosting\
**Created:** [October 13, 2017, 12:45am UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972 "2017-10-13T00:45:13Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**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:** [October 13, 2017, 3:21pm UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/11 "2017-10-13T15:21:53Z")

</div>

> [@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.

---

_[View the full topic](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972)._