a month ago
Using an n8n deployment. I am getting an error "Error fetching feature flags Error [PostHogFetchNetworkError]: Network error while fetching PostHog"
I can see that PostHog status is spotty.
This is effectively a 100% outage for us. All of our executions make HTTP requests. We have a 100% failure rate since about 9am this morning Pacific.
I tried redeploy the container and the redeployment failed.
"This deployment failed at the container creation stage due to a transient infrastructure issue. The build completed successfully and the same code deployed without problems one week earlier. Try redeploying to resolve the issue."
3 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 28 days ago
a month ago
Could you elaborate on the details of the N8N deployment (e.g. is it using a template)? Posthog seems to have stabilized but it is interesting that their dependency would cause a total system failure 🤯
a month ago
It's using https://github.com/Shinyduo/n8n-railway. I tried re-deploying with N8N_DIAGNOSTICS_ENABLED=false as described by acuariumtech, but the redeployment failed repeatedly. I was able to get it to deploy successfully by switching datacenters from US west to US east.
I was able to successfully deploy a different, blank instance with the same template to US west, so it's not a broad US west outage.
The failures all failed at the create container step "This deployment failed at the container creation stage, not during the build. The build completed successfully and the exact same code deployed without issues on June 2nd with no changes since. Multiple retry attempts on June 9th all hit the same failure, so try redeploying and contact support if the problem continues."
I'm afraid that's all I could get from the logs.
Resolved, but root cause unknown.
a month ago
Awesome! I could not get the "Deploy on Railway" button from that repo working for me but I am really glad to hear it got resolved that simply. That is awesome!!
Status changed to Open 0x5b62656e5d • 28 days ago
Status changed to Solved 0x5b62656e5d • 28 days ago