-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: HerdHelper not starting #1189
Comments
How does the debug file look like? Any ideas or better errors after going through https://herd.laravel.com/docs/windows/1/troubleshooting/common-issues#the-herdhelper-windows-service-isnt-working ? |
I have reinstalled Herd because I realized that the service for the HerdHelper did not exist, now it is there and is also started at startup. I think this can be closed. Thank you! |
Strange, but the HerdHelper service can no longer be found in the Windows Service Manager, I restarted my PC and it just disappeared. |
Which anti virus program dislikes Herd? The helper changes the hosts file, so there is a chance that the program doesn't like that and thinks that it's malware. You can likely flag it as trusted somewhere in the settings of your anti virus. |
I use Windows Defender, have already deactivated it and also added Herd to the exception (trusted) list, but still the same problem. |
The only way why the helper can disappear is that either a anti-virus program removes it or there is a corporate policy installed on your machine that does it remotely. |
Platform
Windows
Operating system version
Windows 11 22631
System architecture
64-bit
Herd Version
1.13.0
PHP Version
No response
Bug description
Like many others here, I have the problem that HerdHelper does not start and therefore my projects are not accessible in the browser.
However, I can start HerdHelper manually by double-clicking (on the .exe), but that can't be the solution?
So far I have solved it by either editing the hosts file myself or starting the HerdHelper myself.
Steps to reproduce
No response
Relevant log output
The text was updated successfully, but these errors were encountered: