dask-gateway: "HTTPClientError: HTTP 403: Use Proxy Server" due to local HTTP_PROXY?
Dask-gateway feels like a great fit for a project I’m involved in, and I’m excited to try it. Thank you!
I’ve followed the Kubernetes + Helm instructions to install the server out in the wild, and I’m getting a HTTPClientError: HTTP 403: Use Proxy Server when I try to connect to the public gateway from my local machine. I can instantiate the gateway just fine, but I can’t .list_clusters() or .new_cluster() without the error above.
I’m behind a corporate web proxy that I usually handle with an HTTP_PROXY environmental variable. Could this be related to my error? If so, is there a way for me to handle a local web proxy so that I can connect my local gateway client to the external public gateway?
Thanks again.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 20 (10 by maintainers)
That’s specific to the dask-kubernetes default images, and doesn’t work with dask-gateway. I recommend building your own docker images with whatever extra packages you may need, or create a new issue where we can discuss further options.
Works! I was actually using a config file, but a had
dummyinstead ofbasicas the auth type. Must’ve copied it incorrectly from the server config file. Thank you again.Yes.
os.environ['HTTP_PROXY']shows my proxy.That did it:
This is likely related to #103, the http client we use in the
Gatewayclient doesn’t respectHTTP_PROXY. You may be able to hack around this by configuring tornado to useCurlAsyncHTTPClientyourself (note that you’ll needpycurlinstalled).Let me know if this works.