Unable to deploy private GitHub repository - persistent "failed to clone" error
desiklic
FREEOP

8 months ago

I'm unable to deploy any service from my private GitHub repository despite proper GitHub App integration. All deployment attempts fail at the initialization stage with:

We failed to clone your repository, likely due to a network issue. Please try again in a few minutes.

What I've confirmed:

  • Railway GitHub App is installed with "All repositories" access
  • Repository permissions show full read/write access to code, deployments, etc.
  • Environment variables are configured (MONGODB_URI, OPENAI_API_KEY, etc.)
  • Build/start commands are correct (yarn workspace backend build / yarn workspace backend start)
  • Tried both EU West and US East regions - same error in both

Timeline:

  • Issue started ~24 hours ago
  • All 3 services in my project fail identically
  • Noticed there was an EU network incident 3 days ago - possibly related?

Current status:

  • Project: supportive-smile
  • Project ID: 0b8883e7-8a17-4007-9148-4981bb382d71
  • Environment: preview
  • Service: feisty-abundance
  • Latest deployment: Failed at "Initialization › Snapshot code" stage
  • No builds ever succeed - fails before reaching build stage

Question: Is this a known issue with private repository access, or is my account stuck in a bad state after the EU network incident? Happy to provide deployment IDs or additional logs if helpful.

0 Replies

Welcome!

Sign in to your Railway account to join the conversation.

Loading...