• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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