Troubleshooting
Solutions to common issues with Laradebug.
Installation Issues
"App is damaged" on macOS
macOS may block unsigned apps. To fix:
- Right-click the app in Finder
- Select Open from the menu
- Click Open in the dialog
- The app is now trusted
Or via Terminal:
bash
xattr -cr /Applications/Laradebug.appApp Won't Launch
- Check macOS version (requires 11.0+)
- Try downloading again (corrupted download)
- Move app to Applications folder
- Restart your Mac
Permission Denied
If Laradebug can't access your project:
- Go to System Preferences → Security & Privacy → Privacy
- Select Files and Folders
- Ensure Laradebug has access to your projects folder
Project Issues
"PHP Not Found"
Error: PHP executable not foundSolutions:
- Install PHP 8.0 or higher
- Verify PHP is in your PATH:bash
which php php -v - If using Herd/Valet, ensure it's running
- Set custom PHP path in Settings → General → PHP Path
"Artisan Command Failed"
Error: Failed to execute artisan commandSolutions:
- Test artisan works manually:bash
cd /path/to/project php artisan tinker - Check
.envfile exists and is valid - Verify database credentials
- Run
composer installif dependencies are missing
Database Issues
Connection Refused
SQLSTATE[HY000] [2002] Connection refusedSolutions:
- Start your database server (MySQL, PostgreSQL, etc.)
- Check
.envdatabase credentials:DB_HOST=127.0.0.1 DB_PORT=3306 DB_DATABASE=your_database DB_USERNAME=your_user DB_PASSWORD=your_password - Verify database exists
- Test connection with database client
HTTP Monitoring Issues
Requests Not Captured
Check:
- HTTP toggle is enabled (amber)
- Using Laravel's
Httpfacade (not raw Guzzle) - Code actually executed
Correct usage:
php
// This is captured
Http::get('https://api.example.com');
// This is NOT captured
(new \GuzzleHttp\Client())->get('https://api.example.com');AI Assistant Issues
"API Key Invalid"
Solutions:
- Verify key is copied correctly (no extra spaces)
- Check key hasn't expired
- Ensure you have API credits
- Try generating a new key
Ollama Not Connecting
Solutions:
- Verify Ollama is running:bash
ollama list - Check URL in settings (default:
http://localhost:11434) - Ensure a model is downloaded:bash
ollama pull llama3.2 - Restart Ollama
Slow AI Responses
Solutions:
- Claude: Check internet connection
- Ollama: Try a smaller model (phi, mistral)
- Clear chat history (long conversations slow down)
Autocompletion Issues
Suggestions Not Appearing
Solutions:
- Check autocompletion is enabled in Settings
- Try
Ctrl + Spaceto manually trigger - Refresh autocomplete index: Settings → Editor → Refresh Autocomplete Index
- Verify project loaded correctly
Missing Classes
Solutions:
- Refresh autocomplete index
- Run
composer dump-autoloadin your project - Check class file exists and has correct namespace
- Restart Laradebug
Getting Help
Check Logs
Laradebug logs are at:
~/Library/Logs/Laradebug/Report Issues
If problems persist:
- Note the exact error message
- Note steps to reproduce
- Check if it happens with other projects
- Report at GitHub Issues
Reset Settings
To reset all settings:
- Quit Laradebug
- Delete preferences:bash
rm -rf ~/Library/Application\ Support/Laradebug/ - Restart Laradebug
WARNING
This removes all settings, snippets, and history.
Common Error Messages
| Error | Meaning | Solution |
|---|---|---|
EACCES | Permission denied | Check file/folder permissions |
ENOENT | File not found | Verify path exists |
ECONNREFUSED | Connection refused | Start the required service |
ETIMEDOUT | Connection timed out | Check network/service status |
ENOMEM | Out of memory | Reduce data size, restart app |
Still Stuck?
- Restart Laradebug
- Restart your Laravel development server
- Check Laravel logs:
storage/logs/laravel.log - Try with a fresh Laravel project to isolate the issue