Laravel 502 Bad Gateway
betterbloq
HOBBYOP

7 months ago

I have a Laravel + Inertia.js app and I am getting a 502 bad gateway error on a single page. Everything works fine on local so this is only happening on the railway deployment in the staging environment. I have aggressively optimised this page and I'm at a loss now because there's absolutely nothing different about the page (except the data) and I have replicated that on my local environment without any error.

Solved

2 Replies

brody
EMPLOYEE

7 months ago

Hey!

This is an issue with your project / application. Unfortunately, we're unable to offer first-party support for issues unrelated to the Railway product or platform.

Other communities such as Stackoverflow might be able to help you out further.

Best,
Brody


Status changed to Awaiting User Response Railway 7 months ago


betterbloq
HOBBYOP

7 months ago

I resolved this by switching to Caddy as my server. Seems to have been either a body size or buffer limit with Nginx. Either way, closing this now.


Status changed to Awaiting Railway Response Railway 7 months ago


Status changed to Solved betterbloq 7 months ago


Loading...