Many strange errors occurred when deploying n8n using docker. Does anyone know what the situation is?

[shouchi_migari]

Describe the problem/error/question

The logs show a large number of repeated errors.

What is the error message (if any)?

n8n  | Client version 1.14.1 is incompatible with server version 1.16.0. Major versions should match and minor version difference must not exceed 1. Set checkCompatibility=false to skip version check.
n8n  | Client version 1.14.1 is incompatible with server version 1.16.0. Major versions should match and minor version difference must not exceed 1. Set checkCompatibility=false to skip version check.
n8n  | Client version 1.14.1 is incompatible with server version 1.16.0. Major versions should match and minor version difference must not exceed 1. Set checkCompatibility=false to skip version check.
n8n  | Client version 1.14.1 is incompatible with server version 1.16.0. Major versions should match and minor version difference must not exceed 1. Set checkCompatibility=false to skip version check.
n8n  | Client version 1.14.1 is incompatible with server version 1.16.0. Major versions should match and minor version difference must not exceed 1. Set checkCompatibility=false to skip version check.
n8n  | Client version 1.14.1 is incompatible with server version 1.16.0. Major versions should match and minor version difference must not exceed 1. Set checkCompatibility=false to skip version check.

Please share your workflow

Share the output returned by the last node

no

Information on your n8n setup

• n8n version: 1.120.4
• Database (default: SQLite): sqlite
• n8n EXECUTIONS_PROCESS setting (default: own, main): main
• Running n8n via (Docker, npm, n8n cloud, desktop app): docker
• Operating system: debian13

[Parintele_Damaskin]

Hi @shouchi_migari !

Your workflow is OK, it has nothing to do with this “errors” warnings.

It s a gap between versions of n8n client/server.

In your docker-compose.yml file :

services:

n8n:

image: docker.n8n.io/n8nio/n8n:1.16.0

\# ... your other settings ...

There actually is the issue.

[shouchi_migari]

Thank you, my compose file is as follows. It only has one container, and I don’t know how this caused the version difference between the client and the server.

  n8n:
    image: n8nio/n8n:latest
    container_name: n8n
    restart: unless-stopped
    ports:
      - 10.0.0.2:30009:5678
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - .//home/node/.n8n
      - ./download:/home/node/download
      - ./rag-files:/data/files/rag
    depends_on:
      initContainer:
        condition: service_completed_successfully
    environment:
      - NODE_ENV=production
      - N8N_RUNNERS_ENABLED=true
      - N8N_PROXY_HOPS=1
      - N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true
      - NODE_FUNCTION_ALLOW_BUILTIN=*
      - NODE_FUNCTION_ALLOW_EXTERNAL=*
      - DB_SQLITE_POOL_SIZE=5
      - EXECUTIONS_DATA_PRUNE=true
      - EXECUTIONS_DATA_MAX_AGE=72
      - EXECUTIONS_DATA_PRUNE_MAX_COUNT=10000
      - NODE_OPTIONS=--max-old-space-size=4096
      - N8N_BLOCK_ENV_ACCESS_IN_NODE=false
      - N8N_GIT_NODE_DISABLE_BARE_REPOS=false
    healthcheck:
      test: ["CMD", "sh", "-c", "wget --quiet --spider --tries=1 --timeout=10 http://localhost:5678/healthz || exit 1"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 30s

[Parintele_Damaskin]

That .//home/node/.n8n line is almost certainly not what you intend.

It should map a host directory to /home/node/.n8n or where you have it.

Definitely is an old image and that’s why that errors.

You gave to do it properlywith Docker.

P .S i still use npm(will be deprecated later), but Docker only when I have to “move” out lol, and honestly can easily bring headaches.

[shouchi_migari]

I found that this issue only occurs when running this part.

[shouchi_migari]

I found the issue: my Qdrant service version is v1.16.0, but n8n’s Qdrant Vector Store is 1.14.1, which caused an error. Thank you for your help.

[Parintele_Damaskin]

Actually it was the node version and not n8n instance.

Glad that is solved!