# Service Catalog behind corp proxy

**URL:** <https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843>\
**Category:** Rancher 1.x\
**Created:** [February 23, 2016, 10:37pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843 "2016-02-23T22:37:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![flaccid](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/flaccid/32/46_2.png) [@flaccid](https://forums.suse.com/u/flaccid)\
**Post date:** [February 23, 2016, 10:37pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/1 "2016-02-23T22:37:35Z")

</div>

Even when the service catalog is disabled in the UI’s settings we still see:

`fatal: unable to access 'https://github.com/rancher/rancher-catalog.git/': Failed to connect to github.com port 443: Connection timed out`

This is similar to [Failed to clone the catalog from githubexit status 128](http://forums.suse.com/t/failed-to-clone-the-catalog-from-githubexit-status-128/884/3)

When adding a custom catalog the clone also times out, presumably because the host is not in `no_proxy`. The setting there also doesn’t appear to stick as a result.

Would someone be able to confirm if `http_proxy` and `no_proxy` for this operation are inherited from the docker service proxy configuration? Will a git clone work if the proxy is configured correctly? For [github.com](http://github.com) if this is supported we have HTTP\_PROXY set in `/etc/systemd/system/docker.service.d/http-proxy.conf` but does not appear to be used with this operation.

---

<div class="post-metadata">

**Author:** ![ebishop](https://avatars.discourse-cdn.com/v4/letter/e/9dc877/32.png) [@ebishop](https://forums.suse.com/u/ebishop)\
**Post date:** [February 23, 2016, 11:07pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/2 "2016-02-23T23:07:12Z")

</div>

try starting rancher/server with "-e http\_proxy=http://your.proxy "

---

<div class="post-metadata">

**Author:** ![flaccid](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/flaccid/32/46_2.png) [@flaccid](https://forums.suse.com/u/flaccid)\
**Post date:** [February 23, 2016, 11:20pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/3 "2016-02-23T23:20:34Z")

</div>

Hey @ebishop is that method still current? From a certain version I believe rancher will use the docker service’s proxy ([http://docs.rancher.com/rancher/installing-rancher/installing-server/](http://docs.rancher.com/rancher/installing-rancher/installing-server/)). @denise or is this perhaps an exception?

---

<div class="post-metadata">

**Author:** ![ebishop](https://avatars.discourse-cdn.com/v4/letter/e/9dc877/32.png) [@ebishop](https://forums.suse.com/u/ebishop)\
**Post date:** [February 23, 2016, 11:24pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/4 "2016-02-23T23:24:38Z")

</div>

I run one rancher server instance in a lab where a proxy is required most of the time. I couldn’t get the catalog to load and when I passed in the http\_proxy env variable it worked as I remember. Now I always start that instance and pass in http\_proxy. So apparently, it won’t hurt anything. 🙂

---

<div class="post-metadata">

**Author:** ![flaccid](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/flaccid/32/46_2.png) [@flaccid](https://forums.suse.com/u/flaccid)\
**Post date:** [February 23, 2016, 11:36pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/5 "2016-02-23T23:36:25Z")

</div>

Ah cool - which version was that with?

---

<div class="post-metadata">

**Author:** ![ebishop](https://avatars.discourse-cdn.com/v4/letter/e/9dc877/32.png) [@ebishop](https://forums.suse.com/u/ebishop)\
**Post date:** [February 23, 2016, 11:58pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/6 "2016-02-23T23:58:27Z")

</div>

version 59.0, and I set http\_proxy and https\_proxy

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [February 24, 2016, 4:27am UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/7 "2016-02-24T04:27:09Z")

</div>

This sounds like we need to investigate in regards to catalog.

I’ll be using this Github issue to track.

[https://github.com/rancher/rancher/issues/3664](https://github.com/rancher/rancher/issues/3664)

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [February 24, 2016, 3:54pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/8 "2016-02-24T15:54:39Z")

</div>

FYI, I’ve confirmed with @ibuildthecloud that we need to pass in the environment variables in order to get Rancher catalog working.

[http://docs.rancher.com/rancher/installing-rancher/installing-server/#http-proxy](http://docs.rancher.com/rancher/installing-rancher/installing-server/#http-proxy)

I’ve updated the docs to reflect this.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [February 25, 2016, 6:59pm UTC](https://forums.suse.com/t/service-catalog-behind-corp-proxy/1843/9 "2016-02-25T18:59:13Z")

</div>


