Nov '25 • Support Needed 💻
Help!! Selfhosting trigger not triggering
My Schedule Trigger nodes are not firing automatically.
I already tested:
VPN removed
moved workflows to new laptop
timezone set to Australia/Sydney
updated n8n with docker compose pull / down / up -d
created brand new workflow with only Schedule Trigger
Still no automatic execution.
I added this worker block into my docker-compose.yml (under services):
n8n-worker:
image: docker.n8n.io/n8nio/n8n
restart: always
environment:
- GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
command: worker --concurrency=5
depends_on:
- n8n
Containers started normally with no errors.
Question: Is this the correct worker configuration and correct placement under “services” for n8n latest version?
Is there anything else required for Schedule Trigger to actually run in Docker on Hostinger?
8
16 comments
Help!! Selfhosting trigger not triggering
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
1
🔥
+6899
2
🔥
+3877
3
+2671
4
+2348
5
🔥
+1679
Powered by