Subject: Persistent Deployment Issue: "Failed to snapshot repository" on GoldEarn-Backend
domengo404
FREEOP

4 months ago

Dear Railway Support Team,

I am writing to report a persistent issue I'm encountering while trying to deploy my Flask application (GoldEarn-Backend) from GitHub.

**Service:** GoldEarn-Backend (Python/Flask)

**GitHub Repository:** AkramHossam/GoldEarn-Backend

**Problem Description:**

After successfully linking my GitHub repository, the deployment process consistently fails with the error message: "Deployment failed during initialization process" and "Failed to snapshot repository. Please try again in a few minutes."

This error occurs even after I have correctly configured the start command to `python main.py` (as `main.py` is at the root of the repository) and ensured no custom root directory is set.

**Troubleshooting Steps Taken:**

1. Cleared browser cache and cookies.

2. Attempted deployment from different browsers (Chrome, Firefox) on both mobile and desktop.

3. Verified the `main.py` file is directly in the repository root, and adjusted the start command accordingly.

4. Confirmed no custom root directory is set in Railway settings.

5. Waited for several minutes and retried deployment multiple times.

I have attached a video demonstrating the issue (if you have the video file) and screenshots of the deployment logs showing the "Failed to snapshot repository" error.

Could you please investigate this issue from your end? It seems to be preventing Railway from properly accessing or initializing my repository.

Thank you for your assistance.

Best regards,

[Your Name/Username]

Solved

13 Replies

Railway
BOT

4 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


Hello there,

It appears that for a brief period of time, builds were affected, you should see deployments resume. Let us know if you see the error again.


Status changed to Awaiting User Response Railway 4 months ago


dant2021
HOBBY

4 months ago

I am running into this issue as well. (seems to have resolved itself now)


Status changed to Awaiting Railway Response Railway 4 months ago


Going to track this anyways to see what might have went wrong.


Status changed to Awaiting User Response Railway 4 months ago


whatsupamii
PRO

3 months ago

its happening again! same error as the OP, and tried all the steps OP had tried.


Status changed to Awaiting Railway Response Railway 3 months ago


whatsupamii

its happening again! same error as the OP, and tried all the steps OP had tried.

christian
EMPLOYEE

3 months ago

Could you please link to a deployment where you're experiencing this issue?


Status changed to Awaiting User Response Railway 3 months ago


amitgawande03
FREE

3 months ago

this is still exist.


Status changed to Awaiting Railway Response Railway 3 months ago



Railway
BOT

3 months ago

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!


brody
EMPLOYEE

3 months ago

I'm now seeing a different error than before. I've attached a new ticket to this thread, which we will look into promptly.

In the meantime, it would be helpful if you could share your railway.json or railway.toml file.


Status changed to Awaiting User Response Railway 3 months ago


Railway
BOT

3 months ago

🛠️ The ticket "Deployment error" has been marked as todo.


Railway
BOT

3 months ago

🛠️ The ticket Deployment input error has been marked as in progress.


Railway
BOT

3 months ago

✅ The ticket Deployment input error has been marked as completed.


Railway
BOT

3 months 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 3 months ago


Loading...