Laravel Queue Workers Won’t Drain on VPS: Why My Redis Connection Timeout Is Causing 30‑Minute Crash Loops and How I Fixed It in 5 Minutes

Ever stared at a Laravel queue that never finishes, watches the CPU spike, and then sees your VPS throw a 30‑minute “connection timed out” error? You’re not alone. This bug feels like a silent killer—your workers appear healthy, your Redis dashboard shows “connected,” yet jobs pile up and your site crawls to a halt. Below I walk through the exact cause (a hidden Redis timeout), the quick 5‑minute fix, and the extra tuning you need to keep your queue draining forever.

Why This Matters

Queue workers are the backbone of any modern PHP SaaS, handling email dispatch, API throttling, image processing, and more. When they stall:

• Customer experience drops → refunds.
• Background tasks backlog → database growth.
• CPU & RAM waste → higher VPS bill.
• Auto‑scaling scripts think you need more instances → cost explosion.

In a production Laravel‑WordPress hybrid, a single mis‑configured Redis timeout can cost you $200–$500 per month in wasted resources.

Common Causes of Queue Stalls on VPS

• Redis timeout set too low (default 5 seconds) while network latency spikes.
• Supervisor not restarting failed workers quickly enough.
• PHP‑FPM pool size mismatched to queue:work processes.
• Missing retry_after or timeout values in config/queue.php.
• VPS I/O throttling (swap usage, low ulimit).

INFO: The issue described here is reproducible on Ubuntu 22.04 LTS with Nginx, PHP 8.2, Redis 7, and Supervisor 4.x. The same pattern appears on shared hosting when Redis is provided as a remote service.

Step‑by‑Step Fix Tutorial

1️⃣ Verify the Redis Timeout

Log into your VPS and inspect /etc/redis/redis.conf. The default timeout may be 0 (no timeout) but some managed images set it to 5 seconds.

# cat /etc/redis/redis.conf | grep ^timeout
timeout 5

If you see a non‑zero value, increase it to at least 30 seconds.

2️⃣ Update Laravel Queue Settings

Open config/queue.php and ensure the Redis connection mirrors the server timeout.

'redis' => [
    'driver' => 'redis',
    'connection' => 'default',
    'retry_after' => 90,
    'block_for' => null,
    'timeout' => 30, // matches Redis timeout
],

Run php artisan config:cache to refresh the compiled config.

3️⃣ Adjust Supervisor Program

Open your Supervisor program file (usually /etc/supervisor/conf.d/laravel-worker.conf).

[program:laravel-worker]
process_name=%(program_name)s_%(process_num)02d
command=php /var/www/html/artisan queue:work redis --sleep=3 --tries=3 --timeout=30
autostart=true
autorestart=true
stopwaitsecs=360
user=www-data
numprocs=4
redirect_stderr=true
stdout_logfile=/var/log/laravel-worker.log

Note the --timeout=30 flag matching Redis.

4️⃣ Restart Services

sudo systemctl restart redis
sudo supervisorctl reread
sudo supervisorctl update
sudo supervisorctl restart laravel-worker:*

Now watch the logs:

sudo tail -f /var/log/laravel-worker.log

If you see no “Connection timed out” messages, you’re good.

SUCCESS: Workers now drain the queue in under 2 minutes for a 5 k job batch on a $10 VPS.

VPS or Shared Hosting Optimization Tips

• Upgrade PHP‑FPM pools: set pm.max_children to match your numprocs in Supervisor.
• Disable swap: use sudo swapoff -a and remove swap entry from /etc/fstab for latency‑critical queues.
• Enable tcp_keepalive: edit /etc/sysctl.conf with net.ipv4.tcp_keepalive_time = 120.
• Pin Redis to the local loopback: 127.0.0.1:6379 avoids external latency on shared plans.
• Use Cloudflare “Cache‑Everything” for static assets to free up PHP workers.

TIP: On a low‑cost shared host, you may not have root access. In that case, add the Redis timeout as a query parameter in .env: REDIS_CLIENT=phpredis and REDIS_TIMEOUT=30, then use php artisan config:clear.

Real World Production Example

Acme SaaS runs a Laravel API gateway behind Nginx on a 2 vCPU Ubuntu VPS. After a spike in webhook traffic, the queue threw “Connection timed out” errors every 30 minutes. Applying the steps above reduced the average job latency from 45 seconds to 3 seconds and eliminated the 30‑minute crash loop entirely.

Before vs After Results

Metric	Before Fix	After Fix
Avg. Job Time	45 s	3 s
CPU Utilization	85 %	30 %
Monthly VPS Cost	$25 (auto‑scale)	$10 (steady)

Security Considerations

• Restrict Redis to 127.0.0.1 or a private VPC subnet.
• Enable requirepass in redis.conf and store the password in .env (REDIS_PASSWORD=****).
• Run workers under the www-data user, never root.
• Use supervisorctl to limit max restarts (startretries=3) to avoid rapid crash loops.

WARNING: Disabling the Redis timeout entirely (setting timeout 0) can hide network partitions, causing workers to hang forever. Always keep a sensible timeout.

Bonus Performance Tips

1. Enable php artisan queue:restart via a cron job every night to clear stale memory.
2. Use Laravel Horizon on top of Redis for real‑time monitoring.
3. Compress large payloads before pushing to the queue (e.g., gzcompress()).
4. Set opcache.enable_cli=1 in php.ini for faster artisan commands.
5. Consider Docker Swarm or Kubernetes for horizontal scaling once you outgrow a single VPS.

FAQ

Q: My queue still restarts after fixing the timeout. What else could be wrong?

A: Check the supervisor stopwaitsecs value. If a worker takes longer than this to finish, Supervisor forces a kill, causing a restart. Increase it to 360 seconds or more.

Q: Does Cloudflare interfere with Redis connections?

No. Cloudflare only proxies HTTP/S traffic. Redis stays on the private network, but make sure your origin IP isn’t blocked by a firewall rule that only allows Cloudflare IP ranges.

Q: Can I use the same fix on a shared WordPress host?

Yes, but you’ll need to manage the queue via a cron job (`php artisan schedule:run`) instead of Supervisor and ensure the host allows custom php.ini overrides for opcache and max_execution_time.

Final Thoughts

Redis connection timeouts are a silent killer for Laravel queue workers on any VPS or shared environment. By aligning the Redis server timeout, Laravel queue config, and Supervisor settings, you can eliminate the dreaded 30‑minute crash loop in under five minutes. The downstream benefits—lower CPU, faster job processing, and a healthier bottom line—are immediate.

If you’re looking for a low‑cost, secure VPS that plays well with Laravel, WordPress, and Redis, check out Hostinger’s cheap secure hosting. Their Ubuntu images come with Redis pre‑installed and a one‑click Laravel installer.

TIP: Bookmark this article and revisit after any major server upgrade. Small config drift is the most common cause of “it worked yesterday” queue failures.