Chrome & Firefox get ERR_ADDRESS_UNREACHABLE to my homelab on one computer (but curl, Safari, and a fresh Chrome profile all work)

Hello everyone,

For about a month now, I can't reach my homelab from my wife's Macbook (macOS). Both Chrome and Firefox fail with ERR_ADDRESS_UNREACHABLE, whether I use the direct IP or the domain name.

What makes this strange is everything else works fine from the same machine, at the same time:

• curl -v direct IP / domain name returns a normal 200
• dig / ping resolve and reach the server fine
• NFS shares mount and work normally
• Safari works (never used on this machine before, so effectively a fresh browser)
• Chrome launched with a throwaway profile dir works (lauching chrome from the terminal with argument--user-data-dir=/tmp/chrome-clean --no-first-run)

So the network, DNS, routing, and the server are all probably fine. The failure is specific to Chrome and Firefox using their normal profiles.

I've already tried a few things, none fixed it:

• Cleared history, cache, cookies/site data (all time)
• Flushed socket pools + cleared host cache (chrome://net-internals)
• chrome://settings/resetProfileSettings and reset all flags
• chrome://policy is empty, no URLBlocklist or anything
• New Chrome profile / Guest profile, still fails
• Renamed the whole Chrome user-data dir so it rebuilds fresh, still fails
• Rebooted the Mac
• No proxy or VPN active (scutil --proxy is clean). I do occasionally use FortiClient for work but it's disconnected.

Setup: macOS Ventura 13.6 (Intel i7), homelab behind Caddy reverse proxy, Pi-hole + dnsmasq for local DNS (*.mydomain.com).

Does anybody have any idea what could cause both browser to return this error ?

Thanks!