• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Plesk Firewall Configuration Resets Nightly

S

Shadi

Guest
Am having this rather bizzar problem. I set a rule in Plesk for the firewall [Plesk Built in Firewall Module], i.e. Port 12345 for a custome application to enable access to it.

This works fine once the settings are enabled.

Then at some point through the night it seems the firewall resets its configuration, even through the rule is actually still in the list. Going to the firewall module section clicking "edit settings" and then just "activate settings" without changing anything fixes it.

But this has to be done everytime we wish to use a custome application by an administrator. So clearly it's not correct :)

[Just to note there is nothing wrong with the applications we wish to run, that is a 100% certinty, this is strictly a firewall issue]

Anyone have any idea as to the cause or even better a means to fix this problem?

All responses are appreciated :)

Thanks in advance.

Shadi
 
Same here

Hi,

I am having this same problem using a FC5 with Plesk 8.1.1 system.

The firewall rules are listed in Plesk firewall module, but overnight (or after a reboot), iptables shows the original rules.

I think there might be some conflict in the firewall management - may be some other service is taking over firewall control.

I find this "fail2ban" Python script a candidate, but I am not sure.

Can someone help, please?

Thank you!
 
Hi

I had a similar problem, where the firewall policy would be changed, this was caused by apf being loaded, both at start and also a cron once per day, my provider had installed this, which then didnt work with the plesk firewall or with fail2ban

So check what services are started when you boot up and what are in your crons, hope this helps
 
great thanks. I had already removed the apf from boot time but in /etc/cron.daily is a script "fw" this restarted apf, so removing this script resolved the issue.
 
Back
Top