• 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 Plesk bans my own IP address

Techtoox

New Pleskian
Plesk bans my own IP address.

Currently, my public IP address is always banned by Plesk. I have numerous Wordpress installations and when I want to call up a Wordpress installation, my public ip address is immediately added to the banned list. But I don't quite understand why that is. I can log into my Plesk server normally, but I can no longer call up the Wordpress installations because my IP is banned every time I try.

I already googled, but unfortunately couldn't find anything to explain why my own public IP address was banned. Could someone help me here?

OS: Ubuntu 20.04.2 LTS
Product: Plesk Obsidian 18.0.34 Update #2, last updated on April 6, 2021 12:18 AM


System Security
IP Address Banning: On
ModSecurity: On
 
This can be avoided by adding your IP address to the Fail2Ban white list. It's the default on Obsidian, but needs to be done manually once on Onyx.
 
To add, check your logs. First check f2b to see which jail banned you. Then check the logs of that jail. (modsec if its modsec, access logs if its wp, postfix if postfix, etc)
 
Back
Top