7 days ago
Hello Railway Support,
I’m hosting an n8n instance on Railway, and I’ve been running into recurring errors in the logs. Please see the attached screenshots for reference.
The main issues I’m seeing are:
Webhook errors
Received request for unknown webhook: 404 The requested webhook "POST <UUID>/webhook" is not registered.
These keep repeating, even though I haven’t configured those webhooks explicitly.
Postgres checkpoint messages
LOG: checkpoint complete: write XX buffers (...)
These are very frequent and I’m not sure if they’re expected or a sign of a misconfiguration with the Railway Postgres add-on.
Because of these issues, some workflows in n8n are not triggering as expected.
Could you please help me understand:
Why these webhook errors are happening and how I can resolve them?
Whether the Postgres checkpoint logs are normal on Railway or if something needs to be adjusted in my setup?
Thank you very much for your support!
4 Replies
7 days 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!
7 days ago
Can you please help me improve the architecture?
7 days ago
This is N8N specific, and not related to Railway, so the amount of support we can offer is limited. With that in mind, it looks like your N8N service has been redeployed more recently than the other services. That could cause the webhook to be deleted, and thus it's not available from your other services.
You can try to set the following Variable on the service in Railway:
N8N_SKIP_WEBHOOK_DEREGISTRATION_SHUTDOWN
= true
Once you've set it, Redeploy your services and reconnect the webhook.
Status changed to Awaiting User Response Railway • 7 days ago
5 days ago
Thank you christian, i'll do that and let you know how it goes.
what about the 2nd error, the one related to Postgres checkpoint messages?
Status changed to Awaiting Railway Response Railway • 5 days ago
5 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 5 days ago