# Discourse in a closed intranet

**URL:** https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449
**Category:** Self-hosting
**Created:** [April 12, 2016, 1:47pm UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449 "2016-04-12T13:47:14Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![carbo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/carbo/32/54170_2.png) [@carbo](https://meta.discourse.org/u/carbo)
#### Post date: [April 15, 2016, 7:03pm UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/13 "2016-04-15T19:03:48Z")

</div>

This actually did not fix the problem. Inserted the setting in the database and it was still failing. Everything was pointing to an issue with nginx. `nginx -t` fails if the container cannot access the internet. Changed the discourse.conf file at line 220.

from:

`proxy_pass https://avatars.discourse.org/;`

to:

`proxy_pass https://localhost/;`

ran `nginx -t` and it passed

then `sudo service nginx start` it started fine.

Intranet site is now up. Gonna test and see if I still have any issues. Thanks for everyones help.

[https://meta.discourse.org/t/restarting-container-when-internet-is-down-causes-discourse-to-fail/42615?u=carbo](https://meta.discourse.org/t/restarting-container-when-internet-is-down-causes-discourse-to-fail/42615)

---

_[View the full topic](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449)._