# 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:** 1

<div class="post-metadata">

**Author:** ![CyberSathya](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cybersathya/32/120633_2.png) [@CyberSathya](https://meta.discourse.org/u/CyberSathya)\
**Post date:** [13 Octubre, 2017 00:45 UTC](https://meta.discourse.org/t/lets-encrypt-azure-hostname-issue/71972/1 "2017-10-13T00:45:13Z")

</div>

I’ve installed Discourse via Docker on a Ubuntu as mentioned in [Set up Discourse in the cloud in under 30 minutes](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md). The site works from localhost (ssh & port forward via putty). I’m trying to see if SSL is the reason I’m unable to access the site outside localhost via Virtual Machine’s Public IP Address or domain name (via ‘A’ records). So, here is what I’m trying to do to enable **_Let’s Encrypt_**.

> cybersathya@Vaaithaaforum:/var/discourse$ sudo ./discourse-setup  
> Ports 80 and 443 are free for use  
> The configuration file containers/app.yml already exists!
> 
> . . . reconfiguring . . .
> 
> Saving old file as app.yml.2017-10-13-002911.bak
> 
> Found 3GB of memory and 1 physical CPU cores  
> setting db\_shared\_buffers = 768MB  
> setting UNICORN\_WORKERS = 2
> 
> Hostname for your Discourse? [[forum.vaaithaa.com](http://forum.vaaithaa.com)]: [forum.vaaithaa.com](http://forum.vaaithaa.com)  
> Email address for admin account(s)? [sathya@vaaithaa.com]: [sathya@vaaithaa.com](mailto:sathya@vaaithaa.com)  
> SMTP server address? [[smtp.sendgrid.net](http://smtp.sendgrid.net)]: [smtp.sendgrid.net](http://smtp.sendgrid.net)  
> SMTP port? [587]: 587  
> SMTP user name? [apikey]: apikey  
> SMTP password? [_stmp password as given by sendgrid_]  
> Let’s Encrypt account email? (ENTER to skip) [me@example.com]: [sathya@vaaithaa.com](mailto:sathya@vaaithaa.com)

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.

> * * *
> 
> Does this look right?
> 
> Hostname : [forum.vaaithaa.com](http://forum.vaaithaa.com)  
> Email : [sathya@vaaithaa.com](mailto:sathya@vaaithaa.com)  
> SMTP address : [smtp.sendgrid.net](http://smtp.sendgrid.net)  
> SMTP port : 587  
> SMTP username : apikey  
> SMTP password : [_stmp password as given by sendgrid_]  
> Let’s Encrypt : [sathya@vaaithaa.com](mailto:sathya@vaaithaa.com)
> 
> ENTER to continue, ‘n’ to try again, Ctrl+C to exit: n

IP Address (with context screenshot):

 ![Screenshot (412)](https://global.discourse-cdn.com/meta/original/3X/8/8/88a6f2e095b3c748ef4293bf7351868466df8593.png)

---

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