Executing Workflow keeps loading forever

Questions
1

Hi guys,

I am new into n8n. I just installed it on my local server as a container. I can access the GUI and I added 1 manual trigger, but when I click Test Workflow, it keeps loading without getting to an end.

This is my .env file :

N8N_USER=hidden
N8N_PASSWORD=hidden
N8N_HOST=n8n.example.com

N8N_DB=hidden
N8N_DB_USER=hidden
N8N_DB_PASSWORD=hidden

N8N_RUNNERS_ENABLED=true
OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true
N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true

N8N_DISABLE_PRODUCTION_MAIN_MENU=true
N8N_DIAGNOSTICS_ENABLED=false
N8N_DISABLE_TELEMETRY=true

N8N_EXPRESS_TRUST_PROXY=true

This is my docker-compose.yml file :

services:
n8n:
container_name: n8n
image: n8nio/n8n:latest
restart: unless-stopped
ports:
- “5678:5678”
environment:
- N8N_BASIC_AUTH_ACTIVE=true
- N8N_BASIC_AUTH_USER=${N8N_USER}
- N8N_BASIC_AUTH_PASSWORD=${N8N_PASSWORD}
- N8N_HOST=${N8N_HOST}
- N8N_PORT=5678
- N8N_PROTOCOL=https
- N8N_RUNNERS_ENABLED=${N8N_RUNNERS_ENABLED}
- OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=${OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS}
- N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=${N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS}
- NODE_ENV=production
- TZ=Europe/London
- WEBHOOK_URL=https://${N8N_HOST}/
- EXECUTIONS_MODE=queue
- QUEUE_MODE=redis
- QUEUE_BULL_REDIS_HOST=common_redis
- QUEUE_BULL_REDIS_PORT=hidden
- QUEUE_BULL_REDIS_PASSWORD=hidden
- DB_TYPE=postgresdb
- DB_POSTGRESDB_HOST=postgres
- DB_POSTGRESDB_PORT=5432
- DB_POSTGRESDB_DATABASE=${N8N_DB}
- DB_POSTGRESDB_USER=${N8N_DB_USER}
- DB_POSTGRESDB_PASSWORD=${N8N_DB_PASSWORD}
volumes:
- n8n_data:/home/node/.n8n
networks:
- hidden

volumes:
n8n_data:

networks:
hidden:
external: true

This is the logs from the container :

Received SIGTERM. Shutting down…
[Task Runner]: Received SIGTERM signal, shutting down…
[Task Runner]: Task runner stopped

Stopping n8n…
Waiting for 1 active executions to finish…
Waiting for 1 active executions to finish…
Waiting for 1 active executions to finish…
Waiting for 1 active executions to finish…
Waiting for 1 active executions to finish…
User settings loaded from: /home/node/.n8n/config
Last session crashed
Initializing n8n process
n8n ready on 0.0.0.0, port 5678
n8n Task Broker ready on 127.0.0.1, port 5679
Found unfinished executions: 1, 2, 3, 4, 5, 6
This could be due to a crash of an active workflow or a restart of n8n.
Version: 1.88.0

Editor is now accessible via:
https://n8n.example.com
Registered runner “JS Task Runner” (hidden)
Enqueued execution 7 (job 7)
Enqueued execution 8 (job 8)
Enqueued execution 9 (job 9)

2

I see some issues:

you have set n8n to work with HTTPS, but there is no SSL configuration.

I don’t see such a setting in the docs. Where did you get it? I also don’t see any workers in you compose file.

3

Both of them were generated by gpt.

I dig into it and I found that if i set the QUEUE_MODE to “regular” instead of queue, it works perfect. I also noticed in my redis commander that the jobs are still there, which means, they have never got processed in first place.

I am not sure which setup is better. Right now the “regular” value works great. Are there any advantages with redis over regular to work on it and fix it?

4

Hi
Try commenting (hashing) following lines in docker compose file.

  • N8N_PROTOCOL=https
  • N8N_RUNNERS_ENABLED=${N8N_RUNNERS_ENABLED}
  • OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=${OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS}

I hope this will make your N8N setup working smoothly.

5

Hi Muhammad,

thank you for your reply. I haven’t tested it with redis, because without it, it works fine. I will test another docker container with redis and come back with results