The session “{id}” is not registered

[aiaiai]

Hello,

Describe the problem/error/question

I made a new n8n on my raspi. when i start the testmode (telegram trigger) i cant stop the testmode anymore. and the trigger also doesnt work.
in my n8n logs shows:
“The session “{id}” is not registered” when i send a telegram message.

What is the error message (if any)?

“The session “{id}” is not registered”
in the logs

Please share your workflow

just a telegram trigger, nothing more.

Information on your n8n setup

• *n8n version: 1.77.3
• *Database (default: SQLite): ??
• *n8n EXECUTIONS_PROCESS setting (default: own, main): ??
• **Running n8n via raspi pi with docker, nginx, letsencrypt and my own domain
• *Operating system: raspi pi OS

what can i do? i cant find anything…

[n8n]

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:

[mcnaveen]

Can you try refreshing your browser and see if it solves your issue.

[aiaiai]

Refreshing the browser is the only way to get out of that. Without refreshing, i am stucked in the not funktion test mode. but after refreshing i am back to the not working trigger…

i tried different thing. stop, start docker. stop start nginx. tried to change the conf of nginx and the conf of n8n but i never got a working solution. so i am little frustrated…

the only clue i have is the “the session (id) ist not registered” in the logs of n8n on my raspi. the id ist everytime a new random mix of letters.

maybe one of you can help me…
thanks!!!

[aiaiai]

I found it:
from the telegram site:

Stuck waiting for trigger event#

When testing the Telegram Trigger node with the Test step or or Test workflow buttons, the execution may appear stuck and unable to stop listening for events. If this occurs, you may need to exit the workflow and open it again to reset the canvas.

Stuck listening events often occur due to issues with your network configuration outside of n8n. Specifically, this behavior often occurs when you run n8n behind a reverse proxy without configuring websocket proxying.

To resolve this issue, check your reverse proxy configuration (Nginx, Caddy, Apache HTTP Server, Traefik, etc.) to enable websocket support.

---

so i asked chatGPT for help and after different suggestions i got a configuration for n8n that worked.
fill that in after location in the n8n conf

location / {
    proxy_pass http://localhost:5678;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_buffering off;
}

location ~* ^/ws/ {
    proxy_pass http://localhost:5678;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
}