We are trying to setup Self-Hosted Akto on Docker in a private network. The host can only access Internet via proxy. We’ve successfully cloned and built the images, but once we login in the browser, there’s a message that something went wrong. I see that Akto is trying to reach some external IP.
How can we configure Akto to use a proxy when it tries to access HTTP and HTTPS?
Hi @zeljko.vukovic - Akto needs internet access to download a lot of bootstrap data (security test configurations, PII data configurations etc.). Currently, there is no proxy-support in Akto. We can add it though.
What kind of proxy are you using and what is the authentication mechanism?
Till then, is it possible to whitelist github.com and *.akto.io?
Hello, sorry for not comming back to you till now.
I’ve seen this page in docs: Setting up proxy | Akto - API Security platform
Does it mean that a proxy can now be configured? In that case, it is not clear on that page where can these variables be configured?
To answer your earlier question, our proxy does not need auth. Without a proxy, we cannot whitelist Internet traffic based on URLs, only based on IPs. Even if you provide us with IPs for *.akto.io, the IPs for github.com change frequently due to CDN, redundancy and other reasons.
You are correct, we recently added support for proxy in all Akto deployments. You can configure the variables mentioned in the documentation as environment variables ( PROXY_URI and NO_PROXY ) for Akto deployment in which you want the proxy to be available. This can be at different places for different types of deployments, e.g. for a k8s deployment via a helm chart you can update the helm chart and add the environment variable or add it directly to the Akto container. In case you have a specific deployment we can help with that as well.