Error after upgrade docker latest version

[tridi]

After update latest version i got this error every time i want test webhook output, it wont stop execute but the output is done… its really annoying coz now everytime i want test output must start over again

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: 1.22.6
• Database (default: SQLite):Default
• n8n EXECUTIONS_PROCESS setting (default: own, main):Default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system:Linux

[Jon]

Hey @tridi,

Welcome to the community

Which version of n8n did you upgrade from? If you are using a reverse proxy is it also set to enable websockets as I have seen similar issues to this in the past.

[tridi]

i just using docker compose pull so i guess it will pull latest version right so i never know how to check the version before.
hosted on ubuntu 22.04 and this my logs

This my docker-compose.yml

version: "3.7"

services:
  traefik:
    image: "traefik"
    restart: always
    command:
      - "--api=true"
      - "--api.insecure=true"
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.web.http.redirections.entryPoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--entrypoints.websecure.address=:443"
      - "--certificatesresolvers.mytlschallenge.acme.tlschallenge=true"
      - "--certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}"
      - "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json"
    ports:
      - "80"
      - "443"
    volumes:
      - traefik_data:/letsencrypt
      - /var/run/docker.sock:/var/run/docker.sock:ro

  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - "xxx.xxx.219.204:5678:5678"
    labels:
      - traefik.enable=true
      - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.entrypoints=web,websecure
      - traefik.http.routers.n8n.tls.certresolver=mytlschallenge
      - traefik.http.middlewares.n8n.headers.SSLRedirect=true
      - traefik.http.middlewares.n8n.headers.STSSeconds=315360000
      - traefik.http.middlewares.n8n.headers.browserXSSFilter=true
      - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
      - traefik.http.middlewares.n8n.headers.forceSTSHeader=true
      - traefik.http.middlewares.n8n.headers.SSLHost=${DOMAIN_NAME}
      - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
      - traefik.http.middlewares.n8n.headers.STSPreload=true
      - traefik.http.routers.n8n.middlewares=n8n@docker
    environment:
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER
      - N8N_BASIC_AUTH_PASSWORD
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - VUE_APP_URL_BASE_API=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - N8N_PUSH_BACKEND=sse
      - NODE_ENV=production
      - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - DB_SQLITE_VACUUM_ON_STARTUP=true
      - N8N_EMAIL_MODE=smtp
      - N8N_SMTP_HOST=hidden
      - N8N_SMTP_PORT=465
      - N8N_SMTP_USER=hidden
      - N8N_SMTP_PASS=hidden
      - N8N_SMTP_SENDER=hidden
      - N8N_SMTP_SSL=true
    volumes:
      - n8n_data:/home/node/.n8n

  gotenberg:
    image: gotenberg/gotenberg:7

volumes:
  traefik_data:
    external: true
  n8n_data:
    external: true

any clue to fix this?

[Jon]

Hey @tridi,

That looks ok but I would try the below which removes the options that are no longer supported or not needed in your configuration.

You can find the version of n8n in the UI under the Help menu but it would be handy to know what version you upgraded from.

version: "3.7"

services:
  traefik:
    image: "traefik"
    restart: always
    command:
      - "--api=true"
      - "--api.insecure=true"
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.web.http.redirections.entryPoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--entrypoints.websecure.address=:443"
      - "--certificatesresolvers.mytlschallenge.acme.tlschallenge=true"
      - "--certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}"
      - "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json"
    ports:
      - "80"
      - "443"
    volumes:
      - traefik_data:/letsencrypt
      - /var/run/docker.sock:/var/run/docker.sock:ro

  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - "xxx.xxx.219.204:5678:5678"
    labels:
      - traefik.enable=true
      - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.entrypoints=web,websecure
      - traefik.http.routers.n8n.tls.certresolver=mytlschallenge
      - traefik.http.middlewares.n8n.headers.SSLRedirect=true
      - traefik.http.middlewares.n8n.headers.STSSeconds=315360000
      - traefik.http.middlewares.n8n.headers.browserXSSFilter=true
      - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
      - traefik.http.middlewares.n8n.headers.forceSTSHeader=true
      - traefik.http.middlewares.n8n.headers.SSLHost=${DOMAIN_NAME}
      - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
      - traefik.http.middlewares.n8n.headers.STSPreload=true
      - traefik.http.routers.n8n.middlewares=n8n@docker
    environment:
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - DB_SQLITE_VACUUM_ON_STARTUP=true
      - N8N_EMAIL_MODE=smtp
      - N8N_SMTP_HOST=hidden
      - N8N_SMTP_PORT=465
      - N8N_SMTP_USER=hidden
      - N8N_SMTP_PASS=hidden
      - N8N_SMTP_SENDER=hidden
      - N8N_SMTP_SSL=true
    volumes:
      - n8n_data:/home/node/.n8n

  gotenberg:
    image: gotenberg/gotenberg:7

volumes:
  traefik_data:
    external: true
  n8n_data:
    external: true

[tridi]

thanks for update the config and i already fix with it but the problem isnt solved, its still loading when i try execute each node workflow.

i remember my last version is [email protected] and everything just fine. should i rollback the version? and how to do it? thanks

[Jon]

Hey @tridi,

Yeah if you set the version using the below and run a compose pull then a stop and start it should put you back on the older version, It will be interesting to see if it resolves the problem.

docker.n8n.io/n8nio/n8n:1.22.4

[tridi]

yeah still not solve the problem, so now everytime i run test workflow it wont be stop but the result is complete.

and this my error logs from docker container

really appreciate if there is a clue how i can solve this problem, and i already clear cookies and prune docker image everytime trying switch version

[Jon]

Hey @tridi,

I guess the good news is if you are seeing the same issue after going back to the older version then this issue wouldn’t be related to the upgrade.

Can you try connecting to your n8n instance without going through Traefik (just use the ip and port) and see if you have the same issue when doing that

[tridi]

i try like you said on fresh install and its work on ssl with proxy on my cyberpanel then i clear my chrome cookies but i still get same problem

This my screenshot when i try testing workflow with webhook and it wont stop

But on the execution its success

And this my container logs

For more information this is fresh install on ubuntu 22.04 with 8GB RAM and 4vcpu
Any more advice on this error?

[Jon]

Hey @tridi,

Did you try connecting directly to the IP of n8n as suggested? Looking at the error I don’t think you have websockets enabled, does Cyberpanel have a reverse proxy built in?

[tridi]

hi jon yes i already try to access with ip address but still have the issue so i try use proxy on cyberpanel.

i try to find that websocket issue and found solution to add listener and still not solving the problem

and this how i setup websocket on openlitespeed

[Jon]

Hey @tridi,

Sadly I don’t know how to configure the sustem you are using to support websockets so that may be a question for them but before we go too far down that route…

Did you try the direct IP connection using the 5678 port for n8n to bypass any reverse proxies? That will let us know if the issue is with the proxy or something else.

[tridi]

hey jon sorry for late reply, this my screesnhot if access with ip address

and this my docker-compose.yml

version: "3.7"

services:

  n8n:
    image: docker.n8n.io/n8nio/n8n:latest
    restart: always
    ports:
      - "46.xxx.xxx.xx:5678:5678"
    environment:
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - DB_SQLITE_VACUUM_ON_STARTUP=true
    volumes:
      - n8n_data:/home/node/.n8n

  gotenberg:
    image: gotenberg/gotenberg:7

volumes:
  n8n_data:
    external: true

and for information i not get any problem for execution if access on ip address so this issue because my proxy config?

but why this problem comes when i update new n8n version? I have never experienced this problem before and several applications that I installed with Docker using the same proxy method also have no problems.

[Jon]

Hey @tridi,

If it doesn’t appear when going direct then you guessed correct it will be an issue with your reverse proxy and you will need to check how to enable websockets correctly.

I am not sure why this would happen only when upgrading but if it is was an internal issue to n8n you would always see this issue.

[tridi]

appreciate your time for helped me jon, ill find out about it and i saw there is new n8n version release and talk about fixing issue like this i hope it can solve my case too.

Overall i love n8n cause im just a self taught on programming and i learn better with it since i use n8n, great tools! Hope someday i can afford startup plan to monetize it on my country. thanks again jon

UPDATE
Solve this problem by update latest version of n8n, thanks