• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk Firewall Question

D

darkmuncan

Guest
In order to add a network to a rule in Plesk Firewall is it not simply designated as such XXX.XXX.XXX.0 ? This would allow any device in network XXX.XXX.XXX.1 - XXX.XXX.XXX.254 access correct? This is how it's worked in other firewall devices/software that I've configured before. I edited the rule for ssh access to allow from a network of devices and deny from others but nobody in that network can access, doesn't seem to work.
 
XXX.XXX.XXX.1-254 is XXX.XXX.XXX/24 in plesk firewall.

Originally posted by darkmuncan
In order to add a network to a rule in Plesk Firewall is it not simply designated as such XXX.XXX.XXX.0 ? This would allow any device in network XXX.XXX.XXX.1 - XXX.XXX.XXX.254 access correct? This is how it's worked in other firewall devices/software that I've configured before. I edited the rule for ssh access to allow from a network of devices and deny from others but nobody in that network can access, doesn't seem to work.
 
Back
Top