Upgrade to 1.119.0 , Chrome report the construct Websocket: The URL '/rest/push?pushRef=xxxxx' is invalid

Describe the problem/error/question

I upgrade to the verison: 1.119.0 , any workflow show the ‘Connection Lost‘, and can not Execute workflow; but the Eage no this problem

The error actually showing up on the browser console , which it can’t connect to the WebSocket Client as follows:

image

N8N VERSION: 1.119.0

Deploy on K8S 1.18.10

Database: PostgreSQL 16

N8N ENV on K8S deployment:

  • command:
    • /bin/sh
      args:
    • -c
    • sleep 5; n8n start
      env:
    • name: DB_TYPE
      value: postgresdb
    • name: DB_POSTGRESDB_HOST
      value: postgres-service.n8n.svc.cluster.local
    • name: DB_POSTGRESDB_PORT
      value: “5432”
    • name: DB_POSTGRESDB_DATABASE
      value: n8n
    • name: DB_POSTGRESDB_USER
      valueFrom:
      secretKeyRef:
      name: postgres-secret
      key: POSTGRES_NON_ROOT_USER
    • name: DB_POSTGRESDB_PASSWORD
      valueFrom:
      secretKeyRef:
      name: postgres-secret
      key: POSTGRES_NON_ROOT_PASSWORD
    • name: N8N_PROTOCOL
      value: http
    • name: N8N_PORT
      value: “5678”
    • name: EXECUTIONS_MODE
      value: queue
    • name: QUEUE_BULL_REDIS_HOST
      value: redis-service
    • name: QUEUE_BULL_REDIS_PORT
      value: “6379”
    • name: QUEUE_HEALTH_CHECK_ACTIVE
      value: “true”
    • name: N8N_SECURE_COOKIE
      value: “false”
    • name: N8N_HOST
      value: n8n.internal.xxxxxxx.com
    • name: N8N_DEFAULT_LOCALE
      value: zh
    • name: N8N_DIAGNOSTICS_ENABLED
      value: “false”
    • name: N8N_VERSION_NOTIFICATIONS_ENABLED
      value: “false”
    • name: N8N_TEMPLATES_ENABLED
      value: “false”
    • name: N8N_RUNNERS_ENABLED
      value: “true”
    • name: OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS
      value: “true”
    • name: N8N_ENCRYPTION_KEY
      value: changeEncryptionKey
    • name: N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE
      value: “true”
    • name: WEBHOOK_URL
      value: https://n8n.internal.xxxxxxx.com
    • name: N8N_COMMUNITY_PACKAGES_ENABLED
      value: “False”
    • name: NODE_FUNCTION_ALLOW_EXTERNAL
      value: “*”
    • name: NODE_FUNCTION_ALLOW_BUILTIN
      value: “*”
    • name: N8N_REINSTALL_MISSING_PACKAGES
      value: “true”
    • name: N8N_COMMUNITY_NODES_ENABLED
      value: “true”
    • name: N8N_PROXY_HOPS
      value: “1”
    • name: N8N_RUNNERS_MODE
      value: internal
    • name: N8N_PUSH_BACKEND
      value: websocket

Nginx proxy config:

server {
server_name n8n.internal.xxxxxx.com;
listen 443 ssl;
ssl_certificate /etc/nginx/ssl_internal/internal.crt;
ssl_certificate_key /etc/nginx/ssl_internal/internal.key;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers AES128-SHA:AES256-SHA:RC4-SHA:DES-CBC3-SHA:RC4-MD5;
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;

location / {
    proxy_set_header Host $http_host;
    proxy_pass   http://k8s-hawaii;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Real-Port $remote_port;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header REMOTE-HOST $remote_addr;
    proxy_connect_timeout 60s;
    proxy_send_timeout 600s;
    proxy_read_timeout 600s;
    proxy_set_header Origin https://n8n.internal.xxxxxx.com/;
}

}

I try to change “N8N_PUSH_BACKEND“ to ‘‘SSE‘,the ‘Websocket‘ Promble is gone. But fresh the chrmme ,report the error: /workflow/DXJFEXICVpoPtcFp not foud .

I try to modiy the k8s ingress , add the ingress annotations:

nginx.org/proxy-read-timeout: “3600”
nginx.org/proxy-send-timeout: “3600”
nginx.org/websocket-services: “n8n-service”

but this is nothing.

I guess: this problem is casued by chrome version.

chrome version: 117.0.5938.92 64bit

Eage version: 142.0.3595.90 64bit

If anyone happens to know how to resolve this, I’d really appreciate your input—thank you!

hello @ping2025

Does the error persist in Chrome if you open it in incognito mode?

The issue also exists.

I have tested it, and the latest version of Chrome does not have this issue.

Due to specific reasons, my vendor needs to use an older version of Chrome. Other users on the latest version might not encounter this problem