Resolving Common Issues
If you are on this site, we’re sorry. We are working to create the most robust and easiest to use local development environment for Laravel – but Herd is still a tool early in its lifecycle, and we aren’t there yet. On this page, you’ll find common issues and a solution to resolve them. If the documentation and the following tips don’t resolve your issue, please head over to the support section.Restarting Herd
In some rare scenarios, Herd doesn’t start after it has been quit previously. Please check your Task Manager if there are still running instances of Herd and stop them manually before opening Herd again.Herd Debug Logs
The Herd app writes all output to amain.log
log file but keeps this file to a maximum of 1MB, so if you want to get the debug information for Herd, you can check this file. If you encounter a problem that you can reproduce, please check the logs and share them with us via the support if you can’t fix the problem with this information.
404 Errors
If Herd can not properly detect a driver for your site or can’t find the site at all, Herd displays a custom 404 error page. This error page mostly has a useful hint how to fix the problem but it case it does not, the most common problem is that the directory of the project includeswww
in the name.
Herd strips www
from directory names so that all sites are accessible via their domain with and without www
prefix.
The solution to this is renaming the directory from www.your-site.com
to your-site.com
. This allows yout to access the site at http://your-site.com.test
. If the site had specific configurations, you need to apply them again after this change because Herd treats this site as a new one.