• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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