Troubleshooting

When a Mumara Campaigns installation misbehaves, start with the logs — storage/logs/laravel.log for application errors, plus the Apache/Nginx, PHP, MySQL, and Supervisor logs (standard locations for both RHEL-family and Ubuntu/Debian systems are listed in the guide).

The guide covers fixes for the most frequent issues:

• Permission errors — set ownership to the web-server user (apache or www-data), 755/644 on directories/files, 775 on storage and bootstrap/cache; on CentOS/RHEL also apply SELinux contexts with chcon.

• Database errors — "Connection refused" (check MySQL is running, try 127.0.0.1 instead of localhost), "Access denied" (recreate the user with proper grants), and "Unknown database".

• 500 errors and blank pages — missing .env, missing APP_KEY (run php artisan key:generate), stale caches, or PHP memory limits; temporarily set APP_DEBUG=true to see the real error, then turn it back off.

• License validation failures — the server must reach Mumara's license server over HTTPS; also check for expired keys or domain/IP mismatch in the client area.

• Cron and queue problems — verify the scheduler crontab entry, use full PHP paths, check Supervisor worker status, and restart workers after code changes.

The single most common queue mistake: Supervisor workers are running but the Queue Driver in Settings → Application Settings → General is still set to Cronjob or Realtime — jobs won't be dispatched to Supervisor until you change it.

📖 Read the full guide on docs.mumara.com →