Bizarre Self-Hosting Error (Only running or waiting executions can be stopped and 2 is currently error (?))

Questions
1

Describe the problem/error/question

We have completely wiped our .n8n data folder and deleted all docker containers related to n8n. We build a simple 1-2 node execution, and the executions never complete and are presented with this error:

Our self-hosted n8n worked fine for a couple months, then this randomly occurred. Updating did nothing as well.

What is the error message (if any)?

Screenshot 2024-09-05 at 3.36.29 PM

This seems to happen with any kind of run.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: latest
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: ubuntu 20.04
2

It has come to my attention it is somehow a websocket failing to ever connect issue. Investigating.

3

This seemed to be fixed with adding to my nginx reverse proxy config:

proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

I am now encountering a DNS down issue, investigating.

2 Likes
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.