Running Node Persists After Completion

[HoggyTheWizard]

Describe the problem/error/question

When executing my workflow, the HTTP node completes but doesn’t move onto the next node (image 1). Interestingly, the input/output viewer bugs during this for maybe 10-20 seconds before returning to normal (image 2).

What is the error message (if any)?

[WebSocketClient] Connection lost, code=1006 (browser console)

Please share your workflow

Share the output returned by the last node

The output was a binary data file, as expected. As explained above the issue is in regard to that not being passed to the next node.

Information on your n8n setup

• n8n version: 1.113.3
• Database (default: SQLite): SQLite
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker, Apache
• Operating system: Ubuntu

[darrell_tw]

Looks like your request return nothing.

Did you make sure the request return the binary as expected?

[Muhammad_Bin_Zohaib]

Sounds like the HTTP node is finishing but not handing off data properly. A couple of things you can try:

• Check the binary data handling → sometimes the next node expects JSON instead of binary. You may need to use a Move Binary Data node to convert before passing it along.

• Since you’re on Docker + Apache, also check reverse proxy/WebSocket settings (timeouts or buffering can cause the [WebSocketClient] Connection lost, code=1006 issue).

• Make sure you’re on the latest n8n version, sometimes these bugs are fixed in newer builds.

If you want, feel free to share a simplified workflow or reach out to me at [email protected] and I can help debug further.

[HoggyTheWizard]

Thanks for your reply. I can’t do the former as I need to upload the file in the HTTP request, which wouldn’t work with the JSON extract. In regard to the latter, here is my env file/Apache config if that helps:

Apache

<VirtualHost *:443>
  ServerName n8n.<mydomain>.com

  SSLEngine on
  SSLCertificateFile    /etc/letsencrypt/live/n8n.<mydomain>.com/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/n8n.<mydomain>.com/privkey.pem

  ProxyPreserveHost On
  ProxyRequests Off
  
  RequestHeader set X-Forwarded-Proto "https"

  RewriteEngine On
  RewriteCond %{HTTP:Upgrade} =websocket [NC]
  RewriteRule /(.*)           ws://127.0.0.1:5678/$1 [P,L]

  ProxyPass / http://127.0.0.1:5678/ keepalive=On retry=0
  ProxyPassReverse / http://127.0.0.1:5678/

  ProxyTimeout 3600
  TimeOut 3600
  LimitRequestBody 0
  
  ErrorLog  ${APACHE_LOG_DIR}/n8n_error.log
  CustomLog ${APACHE_LOG_DIR}/n8n_access.log combined
</VirtualHost>

.env

DOMAIN_NAME=<mydomain>.com
SUBDOMAIN=n8n
GENERIC_TIMEZONE=America/New_York
SSL_EMAIL=<name>@<mydomain>.com

NODE_FUNCTION_ALLOW_BUILTIN=*
NODE_FUNCTION_ALLOW_EXTERNAL=*
N8N_PUSH_BACKEND=websocket
N8N_HOST=n8n.<mydomain>.com
N8N_PROTOCOL=https
N8N_EDITOR_BASE_URL=https://n8n.<mydomain>.com
WEBHOOK_URL=https://n8n.<mydomain>.com/


N8N_PAYLOAD_SIZE_MAX=1073741824
N8N_DEFAULT_BINARY_DATA_MODE=filesystem

I attempted to add:
N8N_PAYLOAD_SIZE_MAX=1073741824
N8N_DEFAULT_BINARY_DATA_MODE=filesystem
Which would in theory increase the limit more than enough for my 12mb upload and 170mb output. Unfortunately, this did not work. To clarify your last point, I am on the latest version.