Project: unicornio

Service: Primary (n8nio/n8n Docker image)

Environment: Production

Hi Railway team,

I am experiencing instability issues with my production n8n service hosted on Railway.

Context:

- The service was working correctly yesterday.

- Today, without any configuration changes, Railway started sending build failure and deployment failure emails.

- I received multiple “Build failed” and “Deployment failed during network process – Healthcheck failure” notifications.

Current situation:

- The Primary service now shows as “Active”.

- However, my n8n workflows are failing or getting stuck in queue.

- The GPT client interacting with my n8n webhooks returns: “Client response error” and internal server error.

- Executions sometimes stay in “Starting soon” or error out.

Logs show repeated errors including:

- ERR_ERL_UNEXPECTED_X_FORWARDED_FOR

- Healthcheck failures

- Containers restarting unexpectedly

- Previously: “Invalid number value for N8N_PORT: $PORT” (fixed manually)

Infrastructure:

- Using Railway template with:

- Primary (n8n)

- Worker

- Postgres

- Redis

- Gotenberg

- Resources are already set to maximum allowed for my plan.

- No recent variable changes were made before the issue started.

What I need:

1. Confirmation whether there was an infrastructure incident affecting deployments today.

2. Confirmation whether my service is being restarted automatically.

3. Help identifying why healthchecks and networking are intermittently failing.

4. Confirmation that no internal Railway routing/proxy issue is affecting X-Forwarded-For handling.

This is a production workflow and currently non-functional.

Please let me know what diagnostics you need from my side.

Thank you.