[Bug]: Helper won't run on port 5000 or any port #727
Comments
|
Could you please go to C:\ProgramData\Herd and open the It should look like this: After that, please restart the service. Then go to |
|
Hi, I've made these updates and this is the log; I've just updated my actual username with MYUSERNAME in the below, all other data is the same. 2024-05-13 14:29:49.064 +01:00 [INF] Application is shutting down... Status is still red in Herd on port 5000. I was using and do have WAMP installed on this machine, but it's currently closed, and not running at the same time as Herd, I didn't want to remove WAMP until Herd is running ideally. |
|
I also have an issue, when I click the plus button in Herd to create a new project, the Laravel installer doesn't run, and just skips to the window which says the project is created. Does this function also require the helper, are they connected? 
|
|
I have had this problem, And I guess the problem caused by an anti-virus app because I wasn't have anti-virus and it was working fine once I install antivirus again it won't work again |
|
@EGYWEB-Mohamed - Which issue are you also getting, the helper one, or the create new site one? |
Does your terminal have the |
|
It should do, I was using WAMP so would normally create a new project via the terminal, Is there any way to check. |
|
What happens if you open Powershell and run |
|
I get Fatal error: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.2.0". You are running 8.1.14. in phar://C:/Users/MYUSERNAME/.config/herd/bin/laravel.phar/vendor/composer/platform_check.php on line 24 |
|
It looks like you're running php 8.1 globally but the installer requires php 8.2 because that's the dependency for Laravel 11. We definitely need to Either via the UI or by running After that, the installier does it's work 🙂 |
|
Herd claims I'm using 8.3 globally. I still have WAMP installed, but not enabled, will this cause a clash? |
|
It depends what's first in your $PATH variable. I assume that you get 8.1 when you run So my guess is that if you check your PATH variable in your environment variables, herd isn't the first one trying to link php and so it's the old one. That's a. It odd because the installer should place it first 🤔 Do your existing projects work if you clone them into a folder that's parked by herd? That's the one from the general settings. |
|
Yeah that command claims 8.1. 
My pre-herd projects do work when herd is running and I use the open link, they're all listed now in sites. |
|
Wamp was listed in the path, I've removed that and the new projects button works fine now, it's just the issue with herd helper remaining, but for now I can manually create the hosts file record. |
|
Regarding the HerdHelper: Could you please run Does your username contain a space or special chars? What happens if you change the port? There should be a popup requesting admin priviledges to restart it. Does the Dumps and Mail features work for those who face the issue but also have Herd Pro? |
|
Hi, This is the results running on port 5000 and 5002. SERVICE_NAME: HerdHelper When I change the port the pop-up shows but the same issue happens, as shown above I ran the same on port 5002. Dumps and mail are both green, services with mysql also works fine. Graeme |
|
Could you please mail me the content of your hosts file to our support email address? |
|
Hi, I've just send this over, Graeme |
|
@sschlein What was the fix for this? |
|
It's a duplicate not a permanent fix, sorry. |
|
@sschlein Is herd helpers only job to create the URLs in the hosts file? I've just been creating them manually for now, and it seems a workaround. |
|
Yeah exactly. That's the only thing (writing to your hosts file) that requires admin privileges and using the helper allows us to run all other parts of the app with your normal user account. The helper exposes a rest endpoint that accepts your sites and creates the hosts entries based on that. This is why I am wondering what intercepts these calls - for example the status call that displays the information if it's running. |
|
Might it work, when you install Herd it tries maybe 5 pre-defined and common free ports. |
|
The problem with that is that this is curing a symptom instead of working with the root cause. Most people here have tried changing ports, the helper is running but the Herd app can't connect to it. So there's a different problem that we need to solve. |
|
@graememullins and others with the HerdHelper status in red while it's clearly running in your windows services app: Can you please post the output of:
and then
I have no idea why it could start on port 6000 if there is 5000 in your app. Did you try 6000 and then set it back to 5000 but ignored the popup for the restart? Restarting it from the system services or via command line should to the trick. This needs an admin shell: |
|
Could you all also do a |
|
Output of sc.exe query HerdHelper SERVICE_NAME: HerdHelper curl (port 5000) {"message": "OK"} Ping localhost Pinging PCNAME [::1] with 32 bytes of data: Ping statistics for ::1: Ping 127.0.0.1 Pinging 127.0.0.1 with 32 bytes of data: Ping statistics for 127.0.0.1: Ping ::1 Pinging ::1 with 32 bytes of data: Ping statistics for ::1: |
|
Also; PS C:\WINDOWS\system32> sc.exe stop HerdHelper SERVICE_NAME: HerdHelper SERVICE_NAME: HerdHelper SERVICE_NAME: HerdHelper |
|
Unfortunately, that's all correct. Can you please install this debug build? Download Herd Debug This already has an updated HerdHelper and a new general setting with more logs. |
|
Ok, that's installed now, latest log below, I tested on port 5002 as well. 2024-05-24 20:12:23.066 +01:00 [INF] Application is shutting down... |
|
Hey folks, can you please try this debug version? It logs way more data than previous version.
You can either post the logs here or send them to support@beyondco.de (and please mention this issue #727 |
|
When I installed this, I did get a prompt which said, failed to load/start herd helper. Here it the output from the logs, 2024-05-31 16:03:23.890 +01:00 [DBG] Hosting stopping |
|
Hey folks, can you please try this NEW debug version? This one should heal itself it the port is already in use, fix not existing hosts files, write to read-only hosts files and only use IPv6 in cases that this is properly configured on the host machine.
You can either post the logs here or send them to support@beyondco.de Thanks for helping us with debugging. |
|
I still get this error; 
Logs for you: [2024-06-04 16:41:40.244] [error] HTTP Request Failed: { |
|
I wonder why Herd is in C:\Program Files and not C:\Users\USER\AppData\Roaming\Herd 🤔 Is this a Win10 and Win11 difference or why could that happen? Can you please download this version of the HerdHelper and install it manually? Download To install it manually:
If the HerdHelper service can't be started because it's not there yet, please do:
This should give us either better error messages during the setup or finally the logs that we need (or a working HerdHelper) at I appreciate your patience and your help to debug this so that we can fix this once and for all. |
|
I'm using Win11 I've tried all of the above and get; SERVICE_NAME: HerdHelper Logs for you; 2024-06-04 16:38:34.327 +01:00 [DBG] Hosting starting |
|
I am closing this issue here because we've moved that to the support inbox and there are other HerdHelper issues for follow up with other users. |
Platform
Windows
Operating system version
Windows 11
System architecture
Windows
Herd Version
1.1.0
PHP Version
8.3.7
Bug description
The helper won't run on port 5000, however the service is running in services.
Is there a fix for this, is there anything else I need to do to try another port?
I've tried port 5002, however this still doesn't work.
Also when I go to create a new project, it claims the project is created, however it doesn't get created.
I'm using my own /Projects folder on my D drive to hold any projects, not the herd folder in users.
Graeme
Steps to reproduce
Re installed Herd 3 times,
Started and stopped the service Herd Helper.
Windows updates
Herd updates
Relevant log output
No response
The text was updated successfully, but these errors were encountered: