#client-side TypeError when fronting with nginx

2 messages · Page 1 of 1 (latest)

red pelican
#

I'm fronting overseer with nginx and continue to get browser client javascript errors (safari, chrome, mobile & desktop). Specifically the error is, TypeError: Cannot read properties of undefined (reading 'limit'). The overseer landing page & login flow refuses to load as a result which follows with the following error rendered in the browser window, Application error: a client-side exception has occurred (see the browser console for more information).

When I access overseer directly there are no issues which leads me to beleive the issue is with nginx configuration somehow.

I don't have any problems with ~30 services fronted by nginx though. My nginx configuration is defined here: https://github.com/billimek/k8s-gitops/blob/master/kube-system/nginx/nginx.yaml#L21-L47

I also attempted to set Enable Proxy Support in Overseer which didn't make a difference. The Application URL setting matches my nginx hostname for Overseer.

Looking for anyone who may have experienced this issue before and knows what to change to resolve it.

red pelican
#

... Answering my own question in case this comes up in a search:

Can't use the nginx default backend for 401 (and probably also 403) errors as it seems to interfere with overseer's /api/v1/auth/me check which returns a 401 and nginx redirects the client to a diff backend.