Add the ability to use HTTP/HTTPS proxies on Portainer #9316
Replies: 17 comments
-
Beta Was this translation helpful? Give feedback.
-
Same issue here, would love to see this implemented ! |
Beta Was this translation helpful? Give feedback.
-
Have you tried to add HTTP_PROXY and HTTPS_PROXY env var to portainer container ? |
Beta Was this translation helpful? Give feedback.
-
Tried it ... sometimes it works and I see the "app template homepage" ... sometimes I will get this error. Strange... without restarting the container! Passed ENV as HTTPS_PROXY=10.1.0.1:8080 http error: Get https://raw.githubusercontent.com/portainer/templates/master/templates.json: http: error connecting to proxy http://10.1.0.1:8080: dial tcp 10.1.0.1:8080: i/o timeout (code=500) |
Beta Was this translation helpful? Give feedback.
-
I can't really help more, I think you should have same problem from your browser with same proxy |
Beta Was this translation helpful? Give feedback.
-
I just tried it now with HTTP_PROXY variable and it works !! Thanks @WTFKr0 for the simple solution I should have thought of that before ! Full docker command : Replace $PROXY_HOST with the actual hostname of the proxy and $PROXY_PORT with the actual port of the proxy (if present).
|
Beta Was this translation helpful? Give feedback.
-
@WTFKr0 Nice one ;) @misery this problem might be related to your network. @DEKHTIARJonathan want to give this solution a try? I'm going to add this in the docs. |
Beta Was this translation helpful? Give feedback.
-
Added via portainer/portainer-docs@078c04a |
Beta Was this translation helpful? Give feedback.
-
@deviantony it works perfectly thanks ! |
Beta Was this translation helpful? Give feedback.
-
Hi Folks, It is important that this configuration is done using the Web UI. In many cases, the proxy login/password expire after X months, and then it stops working. In the corporate world, this is the default. |
Beta Was this translation helpful? Give feedback.
-
I'll re-open to consider an evolution to be able to configure any HTTP proxy inside Portainer. |
Beta Was this translation helpful? Give feedback.
-
I would add that, if you corporate proxy has https it is doing it with a internal signed certificate, hence you have to pass the CA to Portainer container so it will not comply about unknown certificate signer. I did it just by passing my |
Beta Was this translation helpful? Give feedback.
-
@jrbenito makes a good point; in fact it's also necessary in some corporate environments -- specifically those which perform SSL inspection -- to disable strict SSL (i.e. man-in-the-middle attack detection). |
Beta Was this translation helpful? Give feedback.
-
The corporate environment with authentication for proxy, here. |
Beta Was this translation helpful? Give feedback.
-
This is something we would like to bring into Portainer in the future, it has been added to our internal backlog but we don't have any ETA on this item at this stage. |
Beta Was this translation helpful? Give feedback.
-
So this issue was opened in 2017 and is still at large? I am evaluating portainer for our company and we use a corporate proxy with SSL inspection. I am having the hardest time finding the correct parameters to configure portainer and/or the agents to be able to pull images from our GitHUb organization. Here is the connection timeout when I try to browse my docker registry:
portainer is able to pull images from a public regsitry, e.g. nginx, just fine. But I am unable to deploy a stack using our own GitHub registry. |
Beta Was this translation helpful? Give feedback.
-
Are there any news on this? Today I had exactly this scenario:
I tried to update a stack and re-pull the images, after that the services stopped beacause the repository wasn't availabile. |
Beta Was this translation helpful? Give feedback.
-
Hello dear friends,
I use portainer behind a corporate proxy which is mandatory to access any outside resource.
Thus, portainer is unable to access necessary json file to use App Templates. I can of course host this file locally to fix the problem, but I tend to believe it might not be super hard to add proxy support in one or two requests.
I don't know if proxy could be useful for "endpoint" usage, it's not my usecase. I only use internal servers.
I drop you here a little screenshot of my container logs produced by the missing proxy configuration :
Thanks a lot for the help dear friends!
Beta Was this translation helpful? Give feedback.
All reactions