goauthentik / goauthentik/authentik
Authentik behind Internet proxy. Correct NO_PROXY configuration
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 644
Description
When operating behind an Internet proxy, what is the correct configuration for NO_PROXY environment variable for Pods?
I have set HTTP_PROXY and HTTPS_PROXY to my Internet proxy, and I should configure NO_PROXY to enable all internal http communication in Authentik to operate without proxy. However, I cannot achieve a correct configuration because I always have no health available on the embedded outpost (I have it when I don't set the HTTP_PROXY, HTTPS_PROXY variables, so it must be about NO_PROXY configuration).
I have configured NO_PROXY to my cluster network range, service network range, pods network range, all service names for authentik namespace, ".svc", ".svc.cluster.local", my app domain, localhost, 127.0.0.1.
And still, I don't have health on the embedded outpost. In the logs of "authentik-server" pod I have a Forbidden: `{"error":"Forbidden","event":"failed to connect websocket","level":"warning","logger":"authentik.outpost.ak-api-controller","timestamp":"2025-07-30T00:51:05Z"}`.
Authentik version: `2025.6.4`
Thanks in advance.
**Update:** If I generate a new outpost (not the embedded one), I can achieve having health to that outpost
Contributor guide
Assessment
This issue has not been assessed yet.