google chrome 138.0.7204.50

Chrome 32 bit

https://superuser.com/questions/689898/why-does-windows-firewall-want-to...

That is blocking public
private is only needed for home

https://developer.chrome.com/blog/local-network-access

Our initial version of Local Network Access is ready for opt-in testing in Chrome 138.

Chrome 139 and beyond

Our intent is to ship Local Network Access as soon as possible. Recognizing that some sites may need additional time to be updated with Local Network Access annotations, we will add an Origin Trial to let sites temporarily opt-out of the secure contexts requirement before we ship Local Network Access by default. This should provide a clearer migration path for developers, especially if you rely on accessing local network resources over HTTP (as these requests would be blocked as mixed content if requested from an HTTPS page in browsers that don't yet support the Local Network Access mixed content exemption).

Access annotations or windows firewall pop ups are very similar
there is a a problem with 138 and 139

https://chromestatus.com/feature/5152728072060928

Chrome 141 restricts the ability to make requests to the user's local network, gated behind a permission prompt.

Currently public websites can probe a user's local network, perform CSRF attacks against vulnerable local devices, and generally abuse the user's browser as a "confused deputy" that has access inside the user's local network or software on their local machine. Gating the ability for sites to make local network requests behind a permission prompt helps stop the exploitation of vulnerable devices and servers from the drive-by-web, and gives users control over which sites can probe their local network.