Browse categories
Explore
Fiverr Pro
English
$
USD
I will fix your n8n on coolify task runner, worker and webhook errors
About this Gig
n8n on Coolify broken after updating?
Common problems I fix:
Worker or task-runner container keeps restarting or shows unhealthy
Task request timed out after 60 seconds in Code nodes
Workflows stuck in the queue
repository docker.n8n.io/n8nio/runners not found
Telegram or other webhooks failing (bad webhook)
Coolifys n8n templates can have outdated settings for n8n 2.x. I correct your Compose file, environment variables and healthchecks so your workers, task runners and webhooks run reliably.
Send me a screenshot of your Coolify logs and your n8n version.
Server:
Apache HTTP
•
Virtual private server
Operating system:
Windows
•
Linux
•
IOS
Other Support & IT Services I Offer
FAQ
Why do workers or task runners crash on Coolify after updating n8n?
Coolify templates often use older n8n 1.x configurations. Version 2.x requires updated task-runner sidecars, correct broker listen addresses, and specific container healthchecks to prevent continuous restarts.
Why do my webhooks (Telegram, Stripe, WhatsApp) fail on Coolify?
Webhooks break when N8N_HOST, N8N_PROTOCOL, or WEBHOOK_URL variables are missing or misconfigured behind Coolify’s reverse proxy (Traefik/Caddy). I adjust these variables so incoming triggers execute smoothly.
What fixes Task request timed out after 60 seconds on Coolify?
This happens when n8n's main process cannot communicate with the task-runner broker due to internal container network isolation or mismatched port bindings. I reconfigure your Docker Compose network settings to fix it.
Is direct server access safe?
Yes. I always export your n8n database, container state, and N8N_ENCRYPTION_KEY before making updates. Access can be revoked immediately after the job is completed.
