N8N self hosted Queue Mode - Chat & Webhook not working

Questions
1

I’m facing issues with my N8N self-hosted setup in Queue Mode. When I check the execution history, both the webhook and chat sessions are queued but never executed, eventually timing out. Additionally, when I test and run a workflow, it continues executing even after the process is complete.

Here are my YAML files for the N8N main and N8N-worker configurations. Am I missing something? I’m sure there’s some hack or configuration I’ve overlooked. Any help would be greatly appreciated!

Chat and Webhook in queue
image

image

Screenshot 2024-11-30 224615

Chat box is missing
image

n8n:

  • image: n8nio/n8n:latest*
  • restart: always*
  • ports:*
  •  - 5678:5678*
  • environment:*
  •  - DB_TYPE=postgresdb*

  •  - DB_POSTGRESDB_HOST=postgres*

  •  - DB_POSTGRESDB_PORT=5432*

  •  - DB_POSTGRESDB_DATABASE=${POSTGRES_DB}*

  •  - DB_POSTGRESDB_USER=${POSTGRES_NON_ROOT_USER}*

  •  - DB_POSTGRESDB_PASSWORD=${POSTGRES_NON_ROOT_PASSWORD}*

  •  - EXECUTIONS_MODE=queue*

  •  - QUEUE_BULL_REDIS_HOST=redis*

  •  - QUEUE_BULL_REDIS_PORT=6379*

  •  - QUEUE_HEALTH_CHECK_ACTIVE=true*

  •  - N8N_ENCRYPTION_KEY=${N8N_ENCRYPTION_KEY}*

  •  - N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true*

  •  - QUEUE_RETRY_ATTEMPTS=3*

  •  - QUEUE_DLQ_NAME=dead_letter_queue*

  •  - NODE_ENV=production*

  •  - TZ=America/New_York*

  •  - N8N_DEFAULT_TIMEZONE=America/New_York*

  •  - EXECUTIONS_PROCESS=main*

  •  - EXECUTIONS_PROCESS_COUNT=10*

  •  - EXECUTIONS_TIMEOUT=1800*

  •  - N8N_METRICS=true*

  •  - N8N_METRICS_PORT=5678*

  •  - N8N_SESSION_STORE_OPTIONS='{"type":"redis","host":"redis","port":6379}'*

n8n-worker:

  • image: n8nio/n8n:latest*
  • restart: always*
  • environment:*
  •  - DB_TYPE=postgresdb*

  •  - DB_POSTGRESDB_HOST=postgres*

  •  - DB_POSTGRESDB_PORT=5432*

  •  - DB_POSTGRESDB_DATABASE=${POSTGRES_DB}*

  •  - DB_POSTGRESDB_USER=${POSTGRES_NON_ROOT_USER}*

  •  - DB_POSTGRESDB_PASSWORD=${POSTGRES_NON_ROOT_PASSWORD}*

  •  - EXECUTIONS_MODE=queue*

  •  - EXECUTIONS_PROCESS=queue-worker*

  •  - QUEUE_BULL_REDIS_HOST=redis*

  •  - QUEUE_BULL_REDIS_PORT=6379*

  •  - QUEUE_HEALTH_CHECK_ACTIVE=true*

  •  - N8N_ENCRYPTION_KEY=${N8N_ENCRYPTION_KEY}*

  •  - QUEUE_RETRY_ATTEMPTS=3*

  •  - QUEUE_DLQ_NAME=dead_letter_queue*

  •  - TZ=America/New_York*

  •  - N8N_DEFAULT_TIMEZONE=America/New_York*

  •  - N8N_METRICS_PORT=5678*

  •  - N8N_SESSION_STORE_OPTIONS='{"type":"redis","host":"redis","port":6379}'*

Please let me know if you have any questions

Information on your n8n setup

  • **n8n version: 1.69.2 **
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Durian 12 Linux
2

Are other trigger nodes, or the Schedule node also showing the same issue?

3

This has long been deprecated, please feel free to remove this.

None of these are used by n8n. Can you please share a link to the docs that suggested these, so that we can get the docs updated :pray:

4

Hello @netroy , I’m not sure where these variables came from. I was using ChatGPT to troubleshoot, and it most likely suggested by GPT

5

No, Only chat and webhook on the queue mode

6

Could someone please share a docker-compose.yml file for configuring queue mode in a self-hosted environment? I have n8n-main , n8n-worker , and n8n-webhook . I’m looking for a setup where chat and webhook triggers work immediately without long queue times or timeout.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.