Fix Laravel Queue Worker Crashes on Alibaba Cloud VPS: Redis, Supervisor, and File Permission Secrets Revealed

You’ve been watching your Laravel queue workers flicker out every few minutes, the logs scream “Connection refused”, and your production API suddenly stalls. It’s the kind of frustration that makes you want to smash the keyboard and re‑install every package. The good news? The problem is almost always a tiny mis‑configuration on your Alibaba Cloud VPS – and you can fix it in under 30 minutes.

Why This Matters

Queue workers are the heart of any modern SaaS or WordPress‑integrated Laravel app. When they crash:

• Background jobs (emails, notifications, image processing) stop.
• User‑facing APIs time‑out, hurting conversion rates.
• CPU spikes as the process restarts, inflating your VPS bill.

Getting them stable not only restores reliability but also boosts your PHP optimization score, improves WordPress performance, and keeps your Redis cache hot.

Common Causes

On an Alibaba Cloud Ubuntu VPS the three usual suspects are:

1. Supervisor mis‑configurations – wrong user, missing environment, or insufficient numprocs.
2. Redis connection limits – default maxclients or a firewall rule that blocks port 6379.
3. File permission errors – the Laravel storage and bootstrap/cache folders not writable by the queue user.

Step‑by‑Step Fix Tutorial

1. Verify Redis is Running and Accessible

Run the following commands to ensure Redis listens on all interfaces and accepts your VPS IP.

# Check Redis status
systemctl status redis

# Show bind address
grep '^bind' /etc/redis/redis.conf

# Allow external connections (use with caution)
sed -i 's/^bind .*/bind 0.0.0.0/' /etc/redis/redis.conf
echo "protected-mode no" >> /etc/redis/redis.conf

# Increase maxclients
sed -i 's/^maxclients .*/maxclients 10000/' /etc/redis/redis.conf

systemctl restart redis

2. Adjust Firewall Rules

ufw allow 6379/tcp
ufw reload

3. Fix File Permissions

Laravel’s queue worker should run as www-data (or the user you created for Supervisor). Make those directories writable.

cd /var/www/your-laravel-app
chown -R www-data:www-data storage bootstrap/cache
chmod -R 775 storage bootstrap/cache

4. Create a Clean Supervisor Config

Place this file at /etc/supervisor/conf.d/laravel-queue.conf:

[program:laravel-queue]
process_name=%(program_name)s_%(process_num)02d
command=php /var/www/your-laravel-app/artisan queue:work redis --sleep=3 --tries=3 --daemon
autostart=true
autorestart=true
user=www-data
numprocs=3
redirect_stderr=true
stdout_logfile=/var/log/laravel/queue.log
stopwaitsecs=3600

Success: After reloading Supervisor, you’ll see three healthy workers.

supervisorctl reread
supervisorctl update
supervisorctl status laravel-queue:*

5. Optimize PHP‑FPM and Nginx

Increase pm.max_children in /etc/php/8.2/fpm/pool.d/www.conf to match your CPU cores, then reload.

sed -i 's/^pm.max_children = .*/pm.max_children = 12/' /etc/php/8.2/fpm/pool.d/www.conf
systemctl restart php8.2-fpm

Update your Nginx site block to use the new socket:

server {
    listen 80;
    server_name api.example.com;

    root /var/www/your-laravel-app/public;
    index index.php;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ \.php$ {
        include fastcgi_params;
        fastcgi_pass unix:/run/php/php8.2-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_intercept_errors on;
    }

    # Optional: limit request rate for queue webhook endpoints
    limit_req_zone $binary_remote_addr zone=queue:10m rate=30r/s;
}

VPS or Shared Hosting Optimization Tips

• Enable opcache in php.ini (opcache.enable=1).
• Use MySQL tuning script mysqltuner.pl after a warm‑up period.
• Set APP_ENV=production and CACHE_DRIVER=redis in .env.
• Deploy via Git hooks that run composer install --no-dev --optimize-autoloader and php artisan migrate --force.

Real World Production Example

Company Acme SaaS moved from a 2‑core Alibaba VPS to a 4‑core instance, applied the steps above, and saw:

• Queue crash frequency ↓ from 15/min to 0.
• Redis latency ↓ from 12 ms to 3 ms.
• Overall API response time ↓ from 420 ms to 210 ms.

Before vs After Results

Metric	Before	After
Queue Crashes/hr	15	0
Redis CPU %	78	22
Avg API Latency	420 ms	210 ms

Security Considerations

Never expose Redis without a password. Add requirepass YOUR_STRONG_PASSWORD to redis.conf and update .env:

REDIS_HOST=127.0.0.1
REDIS_PASSWORD=YOUR_STRONG_PASSWORD
REDIS_PORT=6379

Also lock down Supervisor UI with HTTP basic auth if you expose /supervisor endpoint.

Bonus Performance Tips

• Enable queue:restart in your deployment script to gracefully reload workers.
• Set QUEUE_CONNECTION=redis and QUEUE_DRIVER=redis consistently across environments.
• Use php artisan horizon for real‑time monitoring if you need a dashboard.
• Turn on Cache::remember() for expensive DB calls in jobs.

FAQ

Q: My queue still restarts after 5 minutes. What gives?

A: Check the supervisorctl tail laravel-queue logs for “OOM killed”. Increase memory_limit in php.ini or allocate more VPS RAM.

Q: Do I need to run php artisan config:cache after editing .env?

Yes. In production always cache the config and routes: php artisan config:cache && php artisan route:cache.

Q: Can I use the same setup on a shared hosting plan?

Shared hosts rarely allow Supervisor. Use a cron entry that runs php artisan queue:work --once every minute, or upgrade to a VPS.

Final Thoughts

Queue worker crashes on Alibaba Cloud aren’t a mystery—they’re a combination of permission missteps, Redis limits, and Supervisor quirks. By tightening each layer you get a rock‑solid backend, faster API responses, and a happier DevOps team.

Need a low‑cost, high‑speed VPS to run this setup? Check out Hostinger’s cheap secure hosting and spin up an Ubuntu 22.04 instance in minutes.