# Let's Encrypt: Azure hostname issue

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

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [13 Octubre, 2017 02:35 UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/3 "2017-10-13T02:35:10Z")

</div>

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.

---

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