Troubleshooting
Where to look
Section titled “Where to look”- Nginx errors:
~/.config/valet/Log/nginx-error.log, and~/.config/valet/Log/<site>-error.logfor secured, isolated and proxied sites. - Service state:
valet status, orsystemctl status nginxand the PHP-FPM unit for your version. - Which driver serves a site:
valet whichin the site’s directory.
A site doesn’t resolve
Section titled “A site doesn’t resolve”Check what the name resolves to:
getent hosts blog.test- Nothing, on a system using
/etc/hosts: the site was created after the last refresh. Runvalet restart hosts. See DNS. - Nothing, with delegation: check
systemctl status valet-cubed-dnsandresolvectl status, then runvalet restart hoststo set the delegation up again. - Works in the terminal but not in the browser: the browser is using its own DNS over HTTPS. See Browsers with their own DNS.
- LAN names or VPN DNS stopped working after an older Valet release: run the DNS migration.
“Valet requires the which command”
Section titled ““Valet requires the which command””Install which with your package manager. Minimal installs of Arch Linux and openSUSE don’t include it.
403 or 502 errors under SELinux
Section titled “403 or 502 errors under SELinux”valet install makes Nginx and PHP-FPM permissive so they can read sites in your home directory. If you installed with --ignore-selinux, or SELinux was enabled later, run valet install again, or label your site directories for httpd_t yourself.
Arch Linux: “target not found” for a PHP package
Section titled “Arch Linux: “target not found” for a PHP package”The PHP version you asked for isn’t in Arch’s official repositories. Install it from the AUR with your AUR helper (for example php83 and php83-fpm), then run the Valet command again.
openSUSE: “Redis unavailable” during install
Section titled “openSUSE: “Redis unavailable” during install”openSUSE ships Redis only as a per-instance service (redis@), which Valet doesn’t set up. Everything else works. To use Redis, create an instance as described in openSUSE’s Redis package documentation.
The database user can’t log in
Section titled “The database user can’t log in”Run valet db:configure --force and enter a user and password that work. Valet stores them in ~/.config/valet/config.json.
Reporting a bug
Section titled “Reporting a bug”Open an issue on GitHub with your distribution and version, the command you ran, and its full output.