21 days ago
Hi everyone,
I have a Laravel service running on Railway that was working perfectly. I recently pushed some changes that didn't involve any infrastructure or configuration updates. However, after the new build, Nginx is returning a 404 error.
My public URL port is correctly configured, and I haven't changed anything since the initial setup.
Any ideas on what might be causing this? Thanks!
Pinned Solution
21 days ago
I had to use Railpacks instead of Nixpacks, which is just the bullshit this platform does to force you into using their services. I hate them, and I'm looking forward to never using Railway ever again.
Ever since this forced change, my Laravel service (which was working perfectly) is now returning a 404 error through Nginx, even though there were no infrastructure changes. My public port is correctly mapped and nothing else has changed.
The problem was solved
2 Replies
21 days ago
Try rolling back to the previous working commit. If it works, then the changes you made are the cause. Sharing what changes you made would be helpful.
darseen
Try rolling back to the previous working commit. If it works, then the changes you made are the cause. Sharing what changes you made would be helpful.
21 days ago
I had to use Railpacks instead of Nixpacks, which is just the bullshit this platform does to force you into using their services. I hate them, and I'm looking forward to never using Railway ever again.
Ever since this forced change, my Laravel service (which was working perfectly) is now returning a 404 error through Nginx, even though there were no infrastructure changes. My public port is correctly mapped and nothing else has changed.
The problem was solved
Status changed to Solved brody • 21 days ago