• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Firewall.. Rules not coming into force until a reboot?

blackcapsteve

New Pleskian
Hi
I am using the firewall in Plesk, to keep my system safe(r). I download the mailog on a regular basis and highlight those IP addresses which are hitting my system. Whilst not able to contain all intruders I have managed to reduce the strike rate substantially.
I also have only one IP address for both SSH and FTP, which is mine.
However.. I am on a variable IP and if I reboot my router, or if my supplier suddenly decides to issue me with another address, then I have to change the firewall to let me in.
No problem. I like it that I am the only one who can FTP to my server.
But..
I have noticed that the new rules dont immediately come into force..

Even though I get the 'Information: The current configuration has been successfully activated. ' message, I still cant get in. I have tried waiting for an hour or so, but nothing seems to change.
The changes only seem to be enforced AFTER a reboot of the server.
Is there some other way to get the rules up and working straight away without a reboot?

Regards
Steve
 
Back
Top