Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Login results in nginx 502 error #846

Closed
mcasperson opened this issue Nov 6, 2018 · 2 comments
Closed

Login results in nginx 502 error #846

mcasperson opened this issue Nov 6, 2018 · 2 comments
Labels

Comments

@mcasperson
Copy link

When performing a login, nginx returns a 502 error. In the logs you will see this:

2018/11/06 19:50:54 [error] 541#541: *80284 upstream sent too big header while reading response header from upstream

The solution is to add the following setting to the nginx config file:

proxy-buffer-size 128k;

This setting is documented at https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/configmap.md#proxy-buffer-size

@eiximenis
Copy link
Contributor

eiximenis commented Nov 30, 2018

Yep :)

Just for sake of completness...

  • If using AKS, then you can simply do a kubectl apply -f aks-httpaddon-cfg.yaml (file is in /k8s/helm). That will reapply the configmap used by nginx controller preinstalled with the http routing addon in AKS.
  • If using local k8s of Docker CE then this setting should be applied if you followed the instructions of wiki page. If not, the configmap is in the /k8s/nginx-ingress so you can apply. In fact this is a generic configmap that should work with any nginx controller that is installed on ingress-nginx namespace

I'll review the doc to make sure that these steps are clear :)

Thanks!

@mvelosop
Copy link
Collaborator

It looks like the conversation ended, so I'm closing this issue now. Feel free to comment, will reopen if needed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants