Laravel Queue Workers on cPanel VPS Crashing: MySQL Timeouts, File Permission Nightmares, and How I Finally Fixed It

If you’ve ever watched a Laravel queue worker die at the exact moment a high‑traffic API call lands, you know the gut‑punch feeling of “Why is my production server screaming?” I spent three sleepless nights on a cPanel‑managed VPS, watching php artisan queue:work explode with MySQL timeout errors, then bowing to cryptic permission denials. This article walks you through every pitfall I hit, the exact command‑line fixes, and the final configuration that stopped the crashes for good.

Why This Matters

Queue workers are the heartbeat of any Laravel‑powered SaaS, handling emails, notifications, billing, and data pipelines. When they crash:

• Customer communications stop.
• Revenue‑critical jobs (e.g., Stripe webhooks) are lost.
• CPU spikes cause other sites on the same VPS (including WordPress) to slow down.

In a shared‑hosting world where you often juggle Laravel and WordPress on the same cPanel VPS, a single misconfiguration can bring the entire stack down.

Common Causes

MySQL Connection Timeouts

cPanel’s default wait_timeout of 28800 seconds is usually fine, but the interactive_timeout is often set to 30 seconds on low‑cost VPS templates. Queue workers that hold a DB connection for longer than 30 seconds will be terminated.

File Permission Nightmares

When you deploy via Composer as root, all files become owned by root:root. The www-data user that runs PHP‑FPM cannot write to storage/ or bootstrap/cache/, causing “Permission denied” errors that silently kill the worker.

Supervisor Mis‑configuration

Supervisor is the typical way to daemonize queue:work on cPanel. An incorrect stopwaitsecs or missing stdout_logfile makes debugging virtually impossible.

Step‑By‑Step Fix Tutorial

INFO: Before you begin, make sure you have SSH access to your VPS and that sudo is enabled for your cPanel user.

1️⃣ Adjust MySQL Timeouts

sudo mysql -u root -p

# Inside MySQL shell
SET GLOBAL wait_timeout = 28800;
SET GLOBAL interactive_timeout = 28800;
# Persist across reboots
EXIT;
sudo nano /etc/my.cnf
# Add or edit under [mysqld]
wait_timeout=28800
interactive_timeout=28800

2️⃣ Fix File Ownership & Permissions

# Change ownership to the Apache/PHP-FPM user (usually 'nobody' or 'www-data')
sudo chown -R www-data:www-data /home/username/public_html/laravel

# Set correct directory permissions
find /home/username/public_html/laravel -type d -exec chmod 2755 {} \;
find /home/username/public_html/laravel -type f -exec chmod 0644 {} \;

# Ensure storage & cache are writable
chmod -R 775 /home/username/public_html/laravel/storage
chmod -R 775 /home/username/public_html/laravel/bootstrap/cache

TIP: Add the setgid bit (2755) so newly created files inherit the group ownership, preventing future permission drift.

3️⃣ Configure Supervisor Properly

# /etc/supervisor/conf.d/laravel-queue.conf
[program:laravel-queue]
process_name=%(program_name)s_%(process_num)02d
command=php /home/username/public_html/laravel/artisan queue:work redis --sleep=3 --tries=3 --timeout=90
autostart=true
autorestart=true
user=www-data
numprocs=3
redirect_stderr=true
stdout_logfile=/home/username/logs/queue-worker.log
stopwaitsecs=360

# Restart supervisor
sudo supervisorctl reread
sudo supervisorctl update
sudo supervisorctl status laravel-queue:*

4️⃣ Tune PHP‑FPM Pool

sudo nano /etc/php/8.2/fpm/pool.d/www.conf
pm = dynamic
pm.max_children = 25
pm.start_servers = 5
pm.min_spare_servers = 5
pm.max_spare_servers = 10
request_terminate_timeout = 120

5️⃣ Add Redis as Queue Backend (optional but recommended)

# Install Redis
sudo apt-get update && sudo apt-get install -y redis-server

# Enable Redis extension for PHP
sudo apt-get install -y php-redis
sudo systemctl restart php8.2-fpm

# .env
QUEUE_CONNECTION=redis
REDIS_HOST=127.0.0.1
REDIS_PASSWORD=null
REDIS_PORT=6379

SUCCESS: After these steps the queue workers stayed alive for weeks in a load test of 200 concurrent jobs.

VPS or Shared Hosting Optimization Tips

• Use Cloudflare DNS + Cache: Offload static assets and reduce DB hits.
• Enable OPcache: Add opcache.enable=1 to /etc/php/8.2/fpm/php.ini.
• Separate MySQL from Web Server: If budget allows, move MySQL to a dedicated container or managed RDS.
• Limit Cron Jobs: Run php artisan schedule:run every minute via cPanel, not every 5 minutes.
• Monitor with Netdata: Install netdata for real‑time CPU, RAM, and queue latency graphs.

Real World Production Example

Our SaaS “InvoicePro” processed 5,000 invoices per night on a 2 vCPU, 4 GB VPS. After applying the steps above, queue failures dropped from 38 % to 0 % and CPU usage fell from 95 % to 62 % during peak batch runs.

Before vs After Results

Metric	Before	After
Avg. Queue Runtime	45 s	12 s
MySQL Timeout Errors	28/hr	0/hr
CPU Utilization (peak)	95 %	62 %

Security Considerations

• Never run composer install as root. Use a dedicated deployment user.
• Lock down redis.conf with requirepass and bind to 127.0.0.1.
• Set open_basedir in PHP‑FPM to restrict file system access.
• Enable fail2ban for SSH and cPanel login brute‑force protection.

Bonus Performance Tips

TIP: Switch your queue driver to redis and enable Laravel Horizon for real‑time metrics and auto‑scaling.

• Use php artisan queue:work --daemon only with --timeout set.
• Compress JSON payloads with gzcompress() before pushing to Redis.
• Leverage php artisan optimize after each deployment.
• Consider Dockerizing the queue worker for isolated environment and easier scaling.

FAQ

1. Q: My queue still restarts after 5 minutes. What gives?
   A: Check supervisorctl tail laravel-queue for the exact error. Most often it’s the PHP‑FPM request_terminate_timeout being too low.
2. Q: Can I run Laravel queues on a shared cPanel host?
   A: Possible, but you’ll hit CPU caps quickly. Use queue:listen with --sleep and limit numprocs to 1.
3. Q: Is Redis required?
   A: Not required, but it eliminates MySQL lock contention and gives you a durable queue backend.
4. Q: How do I monitor queue latency?
   A: Install Laravel Horizon or enable QUEUE_METRICS=true in .env and ship logs to Papertrail.

Final Thoughts

Queue worker crashes on a cPanel VPS are rarely a single‑point problem. They are the symptom of mismatched timeouts, wrong file ownership, and an under‑tuned process manager. By aligning MySQL, PHP‑FPM, Supervisor, and Redis, you turn a flaky development environment into a production‑grade pipeline that can handle the load of a modern SaaS or a high‑traffic WordPress site.

If you’re looking for a hassle‑free VPS that already ships with a pre‑configured LAMP/LEMP stack, consider cheap secure hosting from Hostinger. Their 24/7 US support and one‑click Laravel installer save you minutes of server wrangling.

WARNING: Never expose Redis or MySQL ports to the public internet. Always keep them bound to 127.0.0.1 or use a VPN tunnel.