# Getting 'welcome to nginx' with no access to internet

**URL:** <https://meta.discourse.org/t/getting-welcome-to-nginx-with-no-access-to-internet/148900>\
**Category:** Self-hosting\
**Created:** [April 22, 2020, 7:19pm UTC](https://meta.discourse.org/t/getting-welcome-to-nginx-with-no-access-to-internet/148900 "2020-04-22T19:19:31Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [May 9, 2020, 8:55pm UTC](https://meta.discourse.org/t/getting-welcome-to-nginx-with-no-access-to-internet/148900/6 "2020-05-09T20:55:37Z")

</div>

> [@FunTec](#):
>
> The server has access to the Internet, but is not accessible from the Internet and the DNS ends with .lan

From the [Install Guide](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)

> 🔔 Discourse will not work from an IP address, you must own a domain name such as `example.com` to proceed.

If you’re not using a publicly valid FQDN then the normal install route won’t work for you. Local DNS entries and domain names aren’t interchangeable here. Let’s Encrypt will fail because the DNS entry isn’t valid.

You’re going to need to modify the app.yml by hand to eliminate HTTPS and Let’s Encrypt. Comment out the unnecessary templates and the entry which exposes port 443.

Unless you plan on issuing a self-signed certificate you will be serving everything over HTTP.

---

_[View the full topic](https://meta.discourse.org/t/getting-welcome-to-nginx-with-no-access-to-internet/148900)._