Commit Graph
1 Commits
Author SHA1 Message Date
0db92c69d4 docs: upstream sent too big header while reading response header from upstream (#8466)
# Which Problems Are Solved


- If you operate Zitadel behind a Reverse Proxy or Ingress inside a
Kubernetes cluster,
you may encounter an Error like `upstream sent too big header while
reading response header from upstream`
- The Docs explain how to solve it

# How the Problems Are Solved

- Adding Troubleshooting Docs for too big upstream header, so people
that search for it find a solution.

---------

Co-authored-by: Elio Bischof <[email protected]>
2024-09-12 10:22:06 +00:00