• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Can the Plesk Firewall extension potentially 'Lock me out' of a server?

Craig1986

Basic Pleskian
I am contemplating the installation of the Plesk Firewall extension, where I can see that Policies and Rules can be set as to restrict access to a server based on IP.

Firstly, what is the difference between restricting access by IP within 'Plesk's Firewall Extension' and within 'Tools & Settings > Restrict Administrative Access'? Would I be right in thinking that the latter simply restricts access to Plesk only while the former restricts multiple methods of access (Therefore, via Plesk and SSH etc)?

Secondly, I am worried I may be 'locked out' of the server. Ideally, I would like to restrict all access to a specific IP address. In the event that my IP changes (The need to restart Router for example), what would be the situation then? Am I right in thinking I would be locked out of the server completely or have I misunderstood Plesk's Firewall extension here?
 
Hi

If you have dinamyc IP of course you not need setup any access by IP restriction

Instead plese use two factor autentification

Plesk firewall will not block you if you configure it in correct way
 
Hi, @Craig1986.
Firstly, what is the difference between restricting access by IP within 'Plesk's Firewall Extension' and within 'Tools & Settings > Restrict Administrative Access'? Would I be right in thinking that the latter simply restricts access to Plesk only while the former restricts multiple methods of access (Therefore, via Plesk and SSH etc)?
Yes, "Restrict Administrative Access" just allow or deny login to Control Panel for Plesk Administrator or Additional Plesk Administrator from some specified IPs. Firewall can deny access for any IP to any port, so using firewall you can deny login to Control Panel for all users.

Secondly, I am worried I may be 'locked out' of the server. Ideally, I would like to restrict all access to a specific IP address. In the event that my IP changes (The need to restart Router for example), what would be the situation then? Am I right in thinking I would be locked out of the server completely or have I misunderstood Plesk's Firewall extension here?
By default Plesk Firewall have no rules, which deny access to Control Panel or SSH. But if you add specific rules, that deny access for all IPs instead yours, than you really will be locked out. So better be carefully with deny rules, especially for SSH access (SSH can be used to repair everything, except broken SSH access =))
 
Back
Top