Roland

Hey, I'm experiencing the very same issue as the OP. When can we expect this to be fixed? For troubleshooting and workaround for the time being see below: I'm not able to access any web service (node, nginx, docker etc...) that I fire up locally on any port. The browser just hangs and having the spinner rotating forever. None of the following works: hxxp://localhost:3000 hxxp://127.0.0.1:3000 hxxp://[::1]:3000 Most of these servers bind to the unspecified ipv6 address (::) - if it's enabled, this is the expected and default behaviour. By default, I should be able to access my local web service using the ipv4 address (localhost and 127.0.0.1) and especially with ipv6 address ([::1]). It is platform specific and seems like most of the OS-s are the same. macOS definitely has dual stack mode enabled by default AND ipv4 is auto-listened if anything binds to the unspecified ipv6 address (::). (see attached and link to an issue) If I define ipv4 explicitly for the service (localhost, 127.0.0.1 or 0.0.0.0) then it works fine and it is accessible via the browser. This is what my ESET firewall log looks like. It is clearly blocking my access. 22/02/2020, 11:36:49 No usable rule found [::]:62323 [::1c1e:f373:0:0]:3000 TCP root 22/02/2020, 11:36:44 No usable rule found [::]:62322 [::1c1e:f372:0:0]:3000 TCP root I was able to get around it by adding the following rule to the firewall (also see attached). Please note: in order to add the :: address you'll have to type ::0 in the IP Address field in ESET for the button to become active. All Application - Inbound - TCP - All Remote Ports - All Local Ports - ::0 (the unspecified ipv6 address) and this is in my logs after adding the rule: 22/02/2020, 18:06:57 Communication allowed by rule [::]:64541 [::1c1e:fc1d:0:0]:3000 TCP Allow communication for System root 22/02/2020, 18:06:57 Communication allowed by rule [::]:64541 [::1c1e:fc1d:0:0]:3000 TCP Allow communication for System root I used freshly installed ESET Cyber Security Pro (6.8.300.0) - default settings - on macOS Mojave (10.14.6) to test and troubleshoot this issue. However, this came to my attention when I was trying to use my work laptop that has ESET Endpoint Security (6.8.400.0) installed on macOS Catalina (10.15.3).