# Proxy during discourse bootstrap
**URL:** https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880
**Category:** Self-hosting
**Created:** [May 31, 2018, 10:59pm UTC](https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880 "2018-05-31T22:59:31Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@sudoman](https://meta.discourse.org/u/sudoman)
#### Post date: [May 31, 2018, 10:59pm UTC](https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880/1 "2018-05-31T22:59:31Z")
Hello,
I was trying to bootstrap while relying on an outbound http proxy, but the bootstrapping script didn’t honor the proxy settings. I created the following file to tell docker to use the a proxy:
```plaintext
$ cat /etc/systemd/system/docker.service.d/docker-http-proxy.conf
[Service]
Environment="HTTP_PROXY=http://proxy.example.com:8118" "NO_PROXY=localhost,127.0.0.1"
```
This allowed the first steps in the bootstrapping to succeed, but the bootstrapping failed when it tried to clone pups.git from [github.com](http://github.com). Due to the locally enforced firewall, the connection to [github.com](http://github.com) was refused.
I’m pretty sure that I had the HTTP\_PROXY environment variable and the system-wide git configuration set too.
I’ve since opened up http/s outbound ports, but was hoping that I could bootstrap in a somewhat more restricted environment. Any thoughts about how to encourage the bootstrapping process to use an http proxy?
Thanks,
Andrew
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 31, 2018, 11:45pm UTC](https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880/2 "2018-05-31T23:45:59Z")
Apparently this has happened before. [Install discourse with internet access only via proxy](https://meta.discourse.org/t/install-discourse-with-internet-access-only-via-proxy/66396)
---
### Author:  [@ssvenn](https://meta.discourse.org/u/ssvenn)
#### Post date: [June 1, 2018, 9:19pm UTC](https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880/3 "2018-06-01T21:19:18Z")
If you’re stuck on bootstrapping with the proxy method, I’ve had good success with the cached install method that requires no internet at all on the machine you’re installing on: [Install Discourse on an isolated CentOS 7 server](https://meta.discourse.org/t/how-to-install-discourse-on-an-isolated-centos-7-server/73538)
It works the same on any linux distribution that can run a recent version of docker.
I recommend creating a shell script for the git clone steps to save a lot of time when it’s time to update the caches, and to make sure you update everything at the same time.
It quickly becomes a mess if you forget to keep all your plugins in sync with the base discourse.