[Bug]: keep getting "502 Bad Gateway" for every Herd *.test URL

[cinemapub]

Platform

macOS

Operating system version

macOS Sequoia 15.5

System architecture

ARM64 (M1, M2, etc)

Herd Version

1.20.0 (Build 45)

PHP Version

both 8.4 and 8.3

Bug description

I installed Laravel Herd on a brand new MBP. It seemed to not work well (On Windows, when I click the program icon, I always get the Herd app window with Settings screen. On MacOS, I get nothing, just the Herd icon in the menu bar remains, but I didn't pay attention to that first, I expected an app window). I then installed Laravel Valet. There were conflicts (probably 2 dnsmasq at the same time).

I then uninstalled Valet, and reinstalled Herd, once I understood that when you start it, you only see the icon in the menu bar and you still need to start Settings, Sites,... from there
Herd says everything is OK, I can stop and restart all services, they all become green, but every *.test URL gives me a 502 Bad Gateway error. I get it with the Adminer, with existing Laravel projects I add, with new Laravel projects I've created within Herd.

Steps to reproduce

• Uninstall Laravel Herd (https://herd.laravel.com/docs/macos/troubleshooting/uninstalling)
• Reinstall Laravel Herd, add Pro License
• Add Service: mySQL
• Click on Adminer button
• I get this page: http://database.herd.test/?$%7Bservice.type%7D&server=127.0.0.1:3306&username=root&password=

Which is a "502 Bad Gateway - nginx/1.27.5" page

Relevant log output

Logging setup complete.
Helper tool is installed and running. Version: 1.0.40 (1.0.40)
Starting initialize method
Copying Nginx config
Copying base Nginx config
Copying DnsMasq config
Copying Fpm config
Copying debug Fpm config
Copying Valet config
Copying PHP config for version 8.4
Ensuring helper tool is installed
Helper tool is installed and running. Version: 1.0.40 (1.0.40)
laravel in app is older or identical than laravel on disk, skipping copy
expose in app is older or identical than expose on disk, skipping copy
composer in app is older or identical than composer on disk, skipping copy
Found existing PID file /Users/pforret/Library/Application Support/Herd/.pid/nginx.pid
Found existing PID file /Users/pforret/Library/Application Support/Herd/.pid/dnsmasq.pid
Wrote PID (36333 to /Users/pforret/Library/Application Support/Herd/.pid/mails.pid
Wrote PID (36334 to /Users/pforret/Library/Application Support/Herd/.pid/fpm-8_3.pid
Wrote PID (36335 to /Users/pforret/Library/Application Support/Herd/.pid/fpm-8_3 (debug).pid
Wrote PID (36336 to /Users/pforret/Library/Application Support/Herd/.pid/C8D32BF7-255F-48C9-AADE-1E2562A4861B.pid
Successfully killed process with pid 35024: AllowedCommandReply(terminationStatus: 0, standardOutput: Optional(""), standardError: Optional(""))
Successfully killed process with pid 35025: AllowedCommandReply(terminationStatus: 0, standardOutput: Optional(""), standardError: Optional(""))

Reply: success(Herd.SetPortCommandMessageReply(log: Optional("Port set to 2304")))
Process Mails started
Process FPM-8.3 started
Process FPM-8.3 (Debug) started
Process MySQL started
Process FPM-8.3 error: [21-May-2025 10:09:20] NOTICE: [pool herd] 'user' directive is ignored when FPM is not running as root
[21-May-2025 10:09:20] NOTICE: [pool herd] 'group' directive is ignored when FPM is not running as root

Process FPM-8.3 error: [21-May-2025 10:09:20] NOTICE: fpm is running, pid 36334

Process FPM-8.3 error: [21-May-2025 10:09:20] NOTICE: ready to handle connections

Process FPM-8.3 (Debug) error: [21-May-2025 10:09:20] NOTICE: [pool herd] 'user' directive is ignored when FPM is not running as root
[21-May-2025 10:09:20] NOTICE: [pool herd] 'group' directive is ignored when FPM is not running as root

Process FPM-8.3 (Debug) error: [21-May-2025 10:09:20] NOTICE: fpm is running, pid 36335

Process FPM-8.3 (Debug) error: [21-May-2025 10:09:20] NOTICE: ready to handle connections

Process Mails output: Port 2525 is free. Starting mailserver.

Process FPM-8.3 (Debug) failed with exit code: 9
Process FPM-8.3 (Debug) stopped
Delete PID file /Users/pforret/Library/Application Support/Herd/.pid/fpm-8_3 (debug).pid
Process Mails output: Mailserver listening on port 2525

Process FPM-8.3 failed with exit code: 9
Process FPM-8.3 stopped
Delete PID file /Users/pforret/Library/Application Support/Herd/.pid/fpm-8_3.pid
Delete PID file /Users/pforret/Library/Application Support/Herd/.pid/nginx.pid
Delete PID file /Users/pforret/Library/Application Support/Herd/.pid/dnsmasq.pid
Wrote PID (36385 to /Users/pforret/Library/Application Support/Herd/.pid/fpm-8_3.pid
Wrote PID (36387 to /Users/pforret/Library/Application Support/Herd/.pid/fpm-8_3 (debug).pid
Wrote PID (36386 to /Users/pforret/Library/Application Support/Herd/.pid/nginx.pid
Process FPM-8.3 started

[jobbrown]

I'm getting the same behaviour but only on certain PHP versions (7.4 affected, 8.X not). My install isn't new but I recently updated to 1.20.0 (Build 45). Restarting & rebooting had no effect.

Edit: sorry. My issue is slightly different. I'm getting 504 Gateway Time-out.

504 Gateway Time-out
nginx/1.25.4

[pixelmultiplo]

Same problem on all php versions.

[asivaneswaran]

After trying to update to 8.4 and Larvel 12, I get this now when I try to runnpm run dev:

error when starting dev server:
Error: getaddrinfo ENOTFOUND riftsurge.test
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

[mpociot]

Does the problem persist when you switch PHP versions (either by using herd use from the terminal or by clicking on a specific PHP version in the menubar).

If this happens on a new installation of Herd, it could also be caused by some unusual user settings - please see: #10 (comment)

[kato-st]

I encountered the nginx gateway timeout just earlier after updating Herd to 1.20.2 (Build: 47), and managed to resolve it (somehow) by simply switching the existing target PHP version for my project from 8.3 to 8.4 from Herd menubar and also from Herd > Sites window (for good measure), and then refreshed the relevant locally running web apps to which the locally running project UI then loads successfully.

Then i reverted the new target PHP version from 8.4 to 8.3, and the UI still loaded successfully, which was strange, but glad my project UI was still served in the browser nonetheless.

Note

Also, when Herd was updated to 1.20.2 (Build: 47), and i tried to restart my services, only the Herd FPM-8.3 service failed to start. Even after a Herd quit and re-open / restart.

So when i switched the target PHP version from 8.3 to 8.4, the service then appeared to startup. And still maintained its startup status (i.e. green circle) when reverting the PHP version back down to the project compatible version of 8.3.

I suppose the PHP version switching / toggling may have written / changed / restored some config files to restore my local project server to startup successfully again(?)