Firewall Issue allowing inbound TCP port 80 and 443

[djmcfar 0]

One of our machines that has been running ESET Smart Security premium 16.x for almost 3 months with no modifications to settings, failed to allow inbound web traffic this morning (inbound requests to ports 80 or 443). I am very experienced with iptables, but not familiar with the ESET firewall. I added a rule in an attempt to remedy the situation, and it had no effect, so I turned off the ESET firewall off to allow the web server internet access (Apache for windows running a non-profit website). Wireshark traces showed that with the ESET firewall turned on, all remote and local inbound web requests were blocked. 

With iptables you can place rules anywhere you want in a chain, as the order of rule evaluation is extremely important with firewalls, but I couldn't find a way to do that with ESET, so my rule got added to the bottom of the list. Any suggestions would be greatly appreciated. Note that there are no other firewalls running on the machine at the time this change in ESET firewall behavior occurred. Thanks in advance.

Edited July 28, 2023 by djmcfar

[LesRMed 23]

Don't these buttons allow you to move it?

 

[djmcfar 0]

@LesRMed Thanks LesRMed, I moved it to the top after you showed me the arrows, but it didn't fix the issue. Other than that rule, I am running installed settings, so the ESET firewall must be more complicated when it comes to adding a rule. If you see this post could you tell me if the rule in itself looks okay to you ? Thanks

[djmcfar 0]

I used learning mode to fix the issue. Interesting that learning mode added the same rule that I did (except for UDP, which is irrelevant). Note to self - don't bother entering rules, as they will have no effect, instead let ESET add them via learning mode, then switch back to automatic mode.