Execution Logs

Questions
1

Hej guyz and girlz,

I will answer my first question here now, so don`t blaim me if this one is already answered :wink:
Currently I am struggling with the visulisation of my execution logs. I just get a circle of death bot nothing is shown.
Using n8n on my own Hetzner cloud. Did have the same setup before on locker docker environment and even at n8n cloud before and never sth like this happened, so this happens after moving to Hetzner. Does anyone knows a thing I can fix?
Thanks in advance.

image
image1449×728 44.7 KB

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Welcome to the community!

The “circle of death” in execution logs on self-hosted setups is almost always a WebSocket connectivity issue. When n8n can’t establish a real-time WebSocket connection back to the frontend, the logs just spin indefinitely.

A few things to check on Hetzner:

1. Reverse proxy WebSocket headers
If you’re running nginx or Caddy in front of n8n, make sure you’re passing WebSocket upgrade headers. For nginx:

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

2. N8N_PUSH_BACKEND env variable
Some setups work better with SSE instead of WebSocket. Try adding:

N8N_PUSH_BACKEND=sse

This switches from WebSocket to Server-Sent Events, which tends to be more reliable behind proxies.

3. Firewall/Hetzner network rules
Check if your Hetzner firewall is blocking WebSocket connections. Long-lived connections sometimes get cut off by default firewall rules.

Start with the N8N_PUSH_BACKEND=sse change - it’s the quickest fix and solves this 90% of the time on cloud/VPS deployments.

4

Hej thanks, this was quite fast! Coming back in case :wink: Thanks in advance!

5

Got it - Caddy was blocking x-frame-options
X-Frame-Options “DENY”
Now: X-Frame-Options: SAMEORIGIN
Check :white_check_mark: