Getting 502 Bad Gateway errors for one page on v3 rack. App responds with 200, and the page works fine on v2 rack

Nice, yeah I will need to do this as well. Which value did you end up using? And can this be done using kubectl?

I found this guide, but it’s a bit involved: Fixing Nginx "upstream sent too big header" error when running an ingress controller in Kubernetes

I was wondering if there’s an easy kubectl command I can run?

EDIT: I figured something out for now: Nginx 502 Bad Gateway auth0 nextjs - #5 by nathan.f77

@mark Do you know if these changes are persistent, or do you need to set this every time you deploy, or after you update Convox?

I noticed that it’s an app-specific setting configured within the Convox app and database, so it’s actually not even part of my Terraform config or .tfstate file. So I’m not too sure how temporary this is, and if I can expect downtime with 502 errors at some point when it gets reset.