Troubleshooting
Use this page when something is not working and you need a symptom-based recovery path.
The guides already include short troubleshooting sections. This page goes a bit deeper and groups the most important issues by symptoms.
Installation and launcher problems
Section titled “Installation and launcher problems”./install.sh does not run
Section titled “./install.sh does not run”Check whether:
- you already ran
chmod +x ./install.sh ./uninstall.sh - you are inside the extracted ZIP folder
- your shell can execute local scripts normally
Try again with:
chmod +x ./install.sh ./uninstall.sh./install.shPhant installs, but no launcher appears
Section titled “Phant installs, but no launcher appears”Check whether:
- the install script completed successfully
- your desktop session has refreshed application entries
Try:
- logging out and back in
- restarting your desktop session
- running
update-desktop-databaseif your system provides it
Onboarding and hook problems
Section titled “Onboarding and hook problems”CLI dump capture is not working
Section titled “CLI dump capture is not working”Check whether:
- onboarding was completed
- the PHP CLI hook is enabled
- PHP is detected correctly in
Settings > Diagnostics - the
DumpsRuntime panel shows the collector as running
HTTP dump capture is not working
Section titled “HTTP dump capture is not working”Check whether:
- the PHP-FPM hook was installed
- Valet Linux is installed and working
- the
Valetpage shows recommendations or mismatches - the related PHP-FPM service is active
Valet and HTTP dump problems
Section titled “Valet and HTTP dump problems”My site appears, but HTTP dumps do not show up
Section titled “My site appears, but HTTP dumps do not show up”Check whether:
- the site is actually served through the expected Valet setup
- the PHP-FPM service used by that site matches the expected prepend configuration
Apply Remediationis still needed in theValetpage
Valet verification shows warnings
Section titled “Valet verification shows warnings”Read the recommendations carefully first.
Common causes include:
- Valet not found in
PATH - missing PHP-FPM hook configuration
- inactive PHP-FPM service
- custom environment layout that needs manual verification
PHP switching and settings problems
Section titled “PHP switching and settings problems”I switched PHP, but my project still behaves the same
Section titled “I switched PHP, but my project still behaves the same”Check whether:
- the CLI runtime changed but the site still uses another PHP-FPM service
- Valet Linux still needs verification after the switch
PHP settings were saved, but nothing changed
Section titled “PHP settings were saved, but nothing changed”Check whether:
- the project is using the PHP runtime you edited
- the related PHP-FPM service restarted successfully
- a manual follow-up command was suggested by Phant
Updates and license problems
Section titled “Updates and license problems”My license key is saved, but updates still do not work
Section titled “My license key is saved, but updates still do not work”Check whether:
- the key was actually saved in
Settings - the update section reports an error
- the current version and latest version values look correct
The update downloads but does not install
Section titled “The update downloads but does not install”Check whether:
- the downloaded file path is shown in
Settings - the install step returned an error
- the environment prevented the restart/install handoff
Services status problems
Section titled “Services status problems”A service shows as stopped
Section titled “A service shows as stopped”Check whether:
- the service is actually running outside Phant
- your service manager reports it as active
- the project depends on that exact service and not another one
A service shows as unavailable
Section titled “A service shows as unavailable”Check whether:
- the service is installed
- the machine exposes it through the expected discovery path
- the service is managed in a way Phant can inspect
When to check another page
Section titled “When to check another page”If the issue is very feature-specific, also check: