Edit on GitHub

Troubleshooting - GrantID

Here you can find information that may help you to diagnose problems on your on-premises instance of GrantID.

Nginx returns 502 Bad Gatewway when accessing /connect/authorize/callback during authentication flow

On scenarios on which an nginx reverse proxy is used, a 502 Bad Gatewway error may occur during the authentication flow, more specifically when /connect/authorize/callback is called:

Note

This issue can affect instances on AWS and also on Kubernetes when using an nginx-based ingress

Error 502 on auth callback

To fix this, set the following settings on your nginx configuration file:

proxy-buffer-size: 256k
proxy-buffering: 'on'
proxy-buffers: 4 "512k"

For instance:

server {

    ...

    location / {
        proxy_pass         ...
        ...
        proxy-buffer-size: 256k
        proxy-buffering: 'on'
        proxy-buffers: 4 "512k"
    }
}

On Kubernetes, these are usually set on the ingress controller's config map:

Proxy buffer configuration on Kubernetes

See also