Lbch 0 Posted April 20, 2021 Share Posted April 20, 2021 Hello, the Eset firewal seems to block virtual hosts on my localhost when using a port number. Setup: MAMP + MAMP hosts Websites that I open have a port number so I can target them using Browsersync Example: https://www.example.com:3000 (this is a local website on my laptop which has been created using Mamp) When I open the website with the port number it is blocked by the Firewall: https://www.example.com:3000 Files load really slow (minutes) or not at all and I get several messages in the firewall log. When I try to open the website without the port number it opens quickly, without a problem: https://www.example.com Any help on how to set this up is much appreciated. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,274 Posted April 20, 2021 Administrators Share Posted April 20, 2021 Does it work if you temporarily pause the firewall? If so, does it work if you switch to interactive firewall mode and create a rule when asked about the communication? Link to comment Share on other sites More sharing options...
Lbch 0 Posted April 20, 2021 Author Share Posted April 20, 2021 Quote Does it work if you temporarily pause the firewall? Yes it does. Quote If so, does it work if you switch to interactive firewall mode and create a rule when asked about the communication? I have tried to switch to interactive firewall, but I get literally an endless number of popups asking about the communication (see screenshot). I cannot even get back to Eset because of these. is there a way to manually add a rule? which rule should I implement? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,274 Posted April 20, 2021 Administrators Share Posted April 20, 2021 If you choose to create a rule you won't be asked about that communication again. If you create a rule for an application, I assume you won't be asked too many times since you probably don't have too many network-aware applications installed. At any rate, I'd recommend collecting logs as per https://support.eset.com/en/kb3404 and opening a support ticket with your local ESET distributor. Link to comment Share on other sites More sharing options...
Recommended Posts