Skip to content
n8n-docker: build fails ~150 ms after start, no logs, no incident on status page
elio77-bot
OP

8 days ago

Service n8n-docker (repo Elio77-bot/n8n-docker, branch main) fails every new deployment at "Build image" about 150 ms after starting, with no build or deploy logs.

Failed deployments: d2727c03 and 9d76e604 (2026-11-11).

The first failure's diagnosis said "No GitHub installation found" and the Settings > Source page showed "Could not load branches" for the repo; later failures show "Infrastructure Error".

status.railway.com shows no incidents.

The previous deployment of the same commit is still running and unaffected.

Redeploying the new commit fails immediately every time.

Solved

1 Reply

Railway
BOT

8 days ago

Your first attempt today at 19:27 UTC was refused because the project no longer had access to the GitHub repository, which matches the "No GitHub installation found" and "Could not load branches" messages. Reconnecting GitHub in your account settings, confirming the Railway GitHub App still has access to that repo, then disconnecting and reconnecting the repository in the service's Settings > Source restores that access.

The three attempts after that (19:30, 19:38 and 20:29 UTC) failed before the build itself began, which is why no build logs were produced, and your running deployment is unaffected.


Status changed to Awaiting User Response Railway • 8 days ago


Railway
BOT

20 hours 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 20 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...