Front-end Freezing Issue During Workflow Test Execution on Self-Hosted N8n

Questions
1

Hi n8n Community,

I am currently facing an issue with our self-hosted N8n instance. This problem has persisted across multiple versions. When we try to run a test on the front-end, the workflow execution appears to be stuck. Specifically, after triggering the test execution of a node, the front-end interface freezes, preventing further testing or implementation. However, upon checking the “executions” section, I can confirm that the execution is indeed happening in the back-end.

I am seeking assistance to understand how to properly configure N8n to avoid this issue. Any insights or guidance on how to resolve this front-end freezing problem while ensuring that the back-end execution functions smoothly would be greatly appreciated.

Thank you in advance for your support.

1 Like
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Hey @_LT, thanks for reaching out. Could you share a video of this happening? Additionally, since you are self-hosting, you could increase the verbosity of n8n’s logging. Feel free to share logging from the period your recording covers and we can take a deeper look.

5

image
image957×563 39.7 KB

in fact it is not configured =/

6


Freezing Editor | n8n - Watch Video

The loom video i ve recorded.

7

I have the same issue, it only started happening after I setup nginx for https

8

Hi @_LT and @Francisco_Saavedra

if you are using nginx you will have to configure the websockets.

server {
  listen 443 ssl;
  server_name n8n.my_domain.tld;
  location / {
    proxy_pass http://127.0.0.1:5678;
    proxy_set_header Connection 'Upgrade';
    proxy_set_header Upgrade $http_upgrade;
    proxy_http_version 1.1;
  }
  ssl_certificate # removed
  ssl_certificate_key # removed
}

:bulb: More Info: NGINX as a WebSocket Proxy

9

Hi @ria

Thank you for the solution! We are using Traefik instead of Nginx. Could you please provide an example configuration for Traefik to handle WebSockets?

Thanks in advance!

10

Hi @vianavnx

You shouldn’t need any specific config for Traefik to handle WebSockets. Are you seeing any issues with it?

11

Yes, its the same issue of the OP. And i was thinking its probably the same solution

12

@ria Do you know what might be causing this behavior even when using Traefik? thanks

13

Hi @vianavnx

Are you only using Traefik or nginx as well?

What kind of errors do you see in the Browser Dev Tools?

14

If i havd this for nginx, what i should change into?

server {
    listen 80;
    server_name your-domain.com;

    location / {
        proxy_pass http://localhost:5678;
        proxy_http_version 1.1;
        chunked_transfer_encoding off;
        proxy_buffering off;
        proxy_cache off;
    }
}
15

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