# Install discourse with internet access only via proxy

**URL:** https://meta.discourse.org/t/install-discourse-with-internet-access-only-via-proxy/66396
**Category:** Self-hosting
**Created:** [7월 18, 2017, 3:56오후 UTC](https://meta.discourse.org/t/install-discourse-with-internet-access-only-via-proxy/66396 "2017-07-18T15:56:03Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![jimbob](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@jimbob](https://meta.discourse.org/u/jimbob)
#### Post date: [7월 19, 2017, 3:50오후 UTC](https://meta.discourse.org/t/install-discourse-with-internet-access-only-via-proxy/66396/13 "2017-07-19T15:50:34Z")

</div>

Thanks.  
Actually the redis error was/maybe a red herring.  
I can now access the welcome splash once I fixed up access to “[avatars.discourse.org](http://avatars.discourse.org)”  
The problem for me is that my corporate DNS servers resolve only internal hosts.  
nginx expects to resolve the above domain, but cannot - hence ngnix crashes ☹  
This was the key - [Restarting container when internet is down causes discourse to fail - #4 by sam](https://meta.discourse.org/t/restarting-container-when-internet-is-down-causes-discourse-to-fail/42615/4)  
I progress by passing docker args to set /etc/hosts. Its not a production solution though…

---

_[View the full topic](https://meta.discourse.org/t/install-discourse-with-internet-access-only-via-proxy/66396)._