Intermittent Disconnections: n8n (Worker) and Self-Hosted Chatwoot

nocodedummy
PRO

7 days ago

1. Overview

I used Railway’s “one-click” template to spin up:

  • n8n with an external worker (latest template version, no custom build)

  • Chatwoot self-hosted (latest template version)

Both services run in the Outbound Chatbot project, production environment. The stack powers a simple chatbot that is still in testing.

2. Problem Statement

During testing, n8n and Chatwoot lose their connections every few minutes:

  1. In n8n, running any workflow manually causes the UI to display “Connection lost, reconnecting…” and the page reloads; the workflow often hangs or fails.

  2. In Chatwoot, the dashboard shows a “Disconnected” banner at roughly the same cadence; it automatically reconnects, but open chat sessions are dropped.

I have not touched any environment variables or deployment parameters from the template defaults, and health checks remain green.

4 Replies

nocodedummy
PRO

7 days ago

Btw this is the error I keep on getting:

Attachments

image.png

echohack
EMPLOYEE

6 days ago

I looked at our side for your postgres databases for both instances and did not see unusual activity on the hosts. It looks like your network is configured correctly as well. I think the only thing remaining to check here is connection pools. Do you know if you might be facing connection pool saturation on your postgres databases?

Status changed to Awaiting User Response railway[bot] • 6 days ago

nocodedummy
PRO

6 days ago

Thanks for checking! I haven’t customized any connection pool settings from the Railway templates, so they’re currently using the default values. Could connection pool saturation still occur under light testing loads? If so, what limits should I look at or tweak in Railway for n8n and Chatwoot respectively? Happy to run any diagnostics you recommend to confirm this. (I’m a beginner under this topic)

Status changed to Awaiting Railway Response railway[bot] • 6 days ago

jake
EMPLOYEE

6 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 jake • 6 days ago

jake
EMPLOYEE

6 days ago

Apologies but this looks like an issue with the application level code. Due to volume, we can only answer platform level issues.

I've made this thread public so that the community might be able to help with you query.