2 months ago
Hi,
a few days ago the GitHub account connected to this Railway Account got suspended. This means that my repositories can't be updated or accessed at all.
While I'm waiting for GitHub's answer, I clearly need to have maintenance on my repositories. GitHub is taking too long to answer, and I fear they might just ignore the Review Appeal.
To avoid any service outage for my users, is there any way I could upload all my repos to another GitHub account / another service, re-upload them inside another Railway account (or this one, if I can unlink my current GitHub account), and have all the configs automatically transferred to the new account? (e.g. env tables, databases, etc...)
6 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
You shouldn't need to have another Railway account. You can unlink your current Github account and link a new one at https://railway.com/account. Make sure you've got an alternate login method (eg, Google or email).
2 months ago
Also, there isn't a way to export the repository from Railway. The only way to reupload it into a new repository is if you have a local copy of the code.
0x5b62656e5d
You shouldn't need to have another Railway account. You can unlink your current Github account and link a new one at https://railway.com/account. Make sure you've got an alternate login method (eg, Google or email).
2 months ago
Once I do that, would I have to create new projects or can I use a new repo named the same way as the old one without changing anything?
2 months ago
Yes, you can recover from this without rebuilding your Railway infrastructure from scratch, but the safest approach is NOT to create a new Railway project unless necessary.
If the existing Railway project is still accessible, keep the existing project/services/databases and change the GitHub source rather than recreating the infrastructure.
Railway supports changing the source of an existing service. The service stores its source reference and its configuration separately, so changing the GitHub repository does not inherently mean recreating the service or its variables. Railway's CLI also supports connecting an existing service to a GitHub repository:
railway service source connect --repo <owner/repo> --branch <branch>The new GitHub account/repository would first need to be accessible to Railway's GitHub integration.
For example, if you have a local clone of the affected repository, you can push that code to a repository under a new GitHub account, connect that GitHub account to Railway, and then reconnect the existing Railway service to the new repository.
This is preferable to creating a new Railway project because the existing Railway service already contains its deployment configuration, variables, networking, domains, etc.
For the database, do NOT recreate it just because the GitHub repository changed. If the existing Railway database is still healthy, leave it in place and keep the application pointing to it. Railway treats the database as a separate service from the application source.
If you genuinely need to create a completely new Railway project/workspace, then there is no single "move everything automatically" operation that I would rely on for a disaster recovery migration. You should separately migrate:
- source code/repository
- service configuration
- environment variables/secrets
- database data using a proper database backup/export and restore
- volumes, if used
- domains/DNS
- external integrations
- deployment/CI configuration
Railway does provide project transfer between workspaces. If your objective is simply to move the Railway project to another Railway workspace, transferring the existing project is much safer than recreating it. The project transfer mechanism is available from Project Settings and transfers the project rather than requiring you to rebuild all services.
One important distinction: a GitHub account suspension and a Railway project/infrastructure failure are two different problems. If the Railway services are still running, don't delete or recreate them while GitHub is unavailable. Preserve the running infrastructure first, then restore your source-control path.
Also, before doing anything destructive, make sure you have a local copy of every repository and verify your database backups.
Railway's current documentation confirms that services can use GitHub, local directories, or Docker images as their source, and that an existing service's source can be changed from its service settings. It also documents CLI support for connecting an existing service to a GitHub repository.
References:
- Railway Services: https://docs.railway.com/services
- Railway CLI service source: https://docs.railway.com/cli/service
- Railway Project transfer: https://docs.railway.com/projects
- Railway Variables: https://docs.railway.com/variables
onetap007
Once I do that, would I have to create new projects or can I use a new repo named the same way as the old one without changing anything?
2 months ago
No. If you unlink and relink your Github to the same Railway account, you'll be able to continue using your current projects. However, you may encounter access issues for repositories, as you're on a different Railway account. If that's the case, then you'll need to create a new repository in your new Github account, and just relink the source for the service to that new repository in the service settings.
a month ago
my GitHub account got suspended for “setting up multiple free accounts” but I didn’t have a clue I had more than one. Anyways, I’ve tried moving everything to AWS but I’m a super Novice. Idk what I’m really doing so I need some advice. Anyone with experience on how to handle this, please help! I can’t even get my account authenticated bc it says I used all my limits of getting verification emails/text sent but it never actually authenticated my account. It never worked. Idk. I’m stuck and not sure how to get everything pulled off my desktop and cloud services and get it to AWS or if anyone has any suggestions for how to manage a build after losing GitHub access that would help. Many Thanks!
Alec