Bad Gateway 502
Hey : ) does anyone know why my app would be getting 502 errors after an update? It was up and working fine, was updated & now it looks like routing has broken - looking at the app logs it doesn't look like requests are making it to my nginx container.
I didn't change any nginx / zerops conf - just a few lines of app code. Anyone who knows what might be going on would be appreciated 🙏
A quick search didn't turn up anyone having this issue recently
7 Replies
Hi @P110 , can you please send the project ID?
Can indeed:
3k5zoZOLTF23tmP2KSh7ZA
Reverted to an old version - it's back up
Trying to re-activate new version now & see if it's unstuck
Aaand she's down again - weird... makes me feel like it might be a me problem somewhere thoughI see the problem give me a minute.
🫡 Thank you
@P110 I have already found the problem. Unfortunately, there is an error in the configuration of the L7 balancer when using rate limiting. I have currently disabled it on the domain. As soon as we fix the problem, we will let you know that it can be turned on again.
No stress, thanks Jan - so keep rate limiting off and I'm all good for now?
Yes, this should be okay for now.