N8n on RPi getting - The session "xxxxx" is not registered

[consig1iere]

Going crazy (total noob here)! Running n8n on a Raspberry Pi 4 4GB which is running DietPi (Bookworm). I know I will get some flak for this, used ChatGPT for install instructions lol. N8n is running smoothly but when I try to set up a simple chat agent (groq + wikipedia), the chat window doesn’t show any response and keeps on “loading”. If I stop it, it automatically loads the chat response in the background and the screen even shows green checkmarks on all nodes. If I try another question in the chat, same thing happens.

Share the output returned by the last node
The output returns a response but not the way it is suppose to work.

Information on your n8n setup

• n8n version: 1.62.5
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main): No clue
• Running n8n via (Docker, npm, n8n cloud, desktop app): docker-compose
• Operating system: Linux Debian (DietPi running Bookworm)
• docker-compose.yml:

services:
  n8n:
    image: n8nio/n8n
    container_name: n8n
    restart: always
    ports:
      - "127.0.0.1:5678:5678"
    environment:
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=xyzxyz #(xyz is used instead of the actual pass)
      - N8N_HOST=xyz.duckdns.org
      - N8N_PORT=5678
      - WEBHOOK_URL=https://xyz.duckdns.org/ #(xyz is used instead of the actual URL)
      - VUE_APP_URL_BASE_API=https://xyz.duckdns.org/ #(xyz is used instead of the actual URL)
      - DB_SQLITE_VACUUM_ON_STARTUP=true
    volumes:
      - ~/.n8n:/home/node/.n8n

• docker-compose log:

NodeOperationError: Node does not have any credentials set
n8n  | ApplicationError: Node does not have any credentials set
n8n  | The session "xyz" is not registered. #(xyz is used instead of the actual id)

Nginx (xyz is used instead of real URL):

server {
    server_name xyz.duckdns.org;

    location / {
        proxy_pass http://localhost:5678;
        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;
        proxy_cache off;
    }

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/xyz.duckdns.org/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/xyz.duckdns.org/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = xyz.duckdns.org) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    server_name xyz.duckdns.org;

    listen [::]:80;
    return 404; # managed by Certbot

}

[Jon]

Hey @consig1iere

Welcome to the community

One of the problems with using ChatGPT is the data it is trained with is fairly old and can produce old configs that don’t work a lot like what you have.

We have install guides in our documentation that would have helped

First thing to do is update your env options the N8N_BASIC_x options have not been used since the launch of v1, you also don’t need VUE_APP_x set.

The next thing to do would be to add N8N_PROXY_HOPS=1 to the env list, once that is done you will need to update your nginx configuration to support websockets (there are a few examples on the forum).

That should then be it and you will be good to start Flowgrammin’