GitHub deployment stopped for an inaccessible existing project
guirampinelli
FREEOP

2 months ago

The site drrampinelli.com.br is still served by Railway, but the Railway account connected to GitHub user guirampinelli shows zero projects. The existing project is in workspace LUMMEN. A merge to main (commit f22c4a7) did not trigger a deployment, so the new page still returns HTTP 404. The Railway GitHub App is installed and Terms were accepted today. Please restore access to the existing project or trigger the deployment from main. I can provide project IDs privately.

Solved

1 Replies

Railway
BOT

2 months ago

The domain is confirmed to be served by Railway, but the project it belongs to sits under a different account than the one this thread is tied to. Your current account ("guirampinelli's Projects", Trial plan) has no projects and no connection to the workspace you mentioned. To trigger the deployment or manage that project, you would need to work from the account that owns that workspace, as plans, projects, and deployments do not carry across accounts.


Status changed to Awaiting User Response Railway • about 2 months ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...