12 days ago
Our MANUS apps (hosted on Railway) are started crashing multiple times per day with a 502 Bad Gateway error, and we lack access to the error logs needed to troubleshoot the issue.
We are seeing Cloudflare errors indicating the host is failing with the following details:
- Host: ahzmzuk4gqkay45pfr75-production.up.railway.app (Note: Please also check sndmwc3ivkrev5wjf33g)
- Error: 502 Bad Gateway
How can we access recent crash logs for these services or get permissions to view them directly? Manus is not being very helpful we tried reaching out to them twice.
Thanks,
6 Replies
12 days ago
This thread has been marked as private.
Status changed to Awaiting Railway Response Railway • 12 days ago
12 days ago
The account this thread is tied to has no services in any of its workspaces, so the services you mentioned belong to a different Railway account and we can't view or share their logs from here. Deployment and crash logs can only be seen by members of the workspace that owns those services, so access has to come from the account that owns them, which in this case appears to be the workspace your apps were deployed into rather than this one.
Status changed to Awaiting User Response Railway • 12 days ago
Railway
The account this thread is tied to has no services in any of its workspaces, so the services you mentioned belong to a different Railway account and we can't view or share their logs from here. Deployment and crash logs can only be seen by members of the workspace that owns those services, so access has to come from the account that owns them, which in this case appears to be the workspace your apps were deployed into rather than this one.
12 days ago
Is it easy to migrate fully from Manus to Railway? Everything is hosted on Railway anyway but we can't troubleshoot because we cant see the error logs or have sufficient observability
Status changed to Awaiting Railway Response Railway • 12 days ago
12 days ago
What a move like this involves, and what carries over versus what has to be set up again, depends on how your projects are wired together. The people best placed to answer that are the ones who have already made the same move.
So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public and the thread closes.
Status changed to Awaiting User Response Railway • 12 days ago
12 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 12 days ago
aeojx
Is it easy to migrate fully from Manus to Railway? Everything is hosted on Railway anyway but we can't troubleshoot because we cant see the error logs or have sufficient observability
12 days ago
I'd try logging into another Railway account and see if you have access to the services.
You should be able to view the logs for the services by clicking into the active deployment.
0x5b62656e5d
I'd try logging into another Railway account and see if you have access to the services. You should be able to view the logs for the services by clicking into the active deployment.
12 days ago
Which railway account should I log in? We never direcly created account with Railway. We did everything through Manus...
12 days ago
Well, you can't create services on Railway without having to create an account. You'll need to figure out what you used to log in with in order to access the logs.
Other than that, there's nothing Railway (or the community) can do to help you.