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

• 📚 Build from a Dockerfile

• 🧵 Dockerfile Issue

• 🧵 How to deploy api (nestjs) and web (nextjs) from monorepo

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

Have you ensured that the RAILWAY_DOCKERFILE_PATH is correctly set in the environment where the error occurs?

Should verify that the path is correct and that the Dockerfile is accessible at that path. Additionally, check if there are any differences in the environment settings between the working and non-working environments.

Yes, the variable is the same as our working environments. The only difference seems to be the Dockerfile not being detected

Could you please link the failed deployment?

Actually I do not have a failed deployment. When I try to deploy from source for the first time on the env, I get "There was an error deploying from source" error.

You might want to double check your config in Service -> Settings, disconnect and reconnect the repo

Thank you. It appears that somehow something changed in the github config and I was not able to link back the repo. It is working after reconnecting the repo with our github admins

However, I do need one of our github admin to be able to switch the connected branch which is kind of annoying. We never had this issue before

I believe changing config has always been an admin action?

Before they add to validate access to the repo once and afterwards we could just switch back and forth repos on Railway projects. I can be also a new config change on our side but I am not sure how as the repos are accessible to Railway.

In my case, I do have the ability to list all branches of the repo on Railway UI but when I select another one and I deploy, no deploy is triggered

For example on Vercel we do not have this issue and the repo access process is pretty much the same

Changing branches doesn't trigger a deploy, so that's expected

Actually there is a button prompting for a deploy when switching branch. But after further tests, it appears I cannot trigger any deploy somehow on any project and any env. For example when I update an env variable. This is critical for us as I won't get github admin right

Basically, clicking on the "deploy" button doesn't do anything anymore

Unfortunately that's the behavior we have ATM. You can use the CLI to workaround this by setting up GitHub actions based on more complex workflows

Was able to fix it. Actually, I logged out and logged in and it kind of resynced the github settings and I can work as usual now.

Thank you so much on your help on that