• 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.

Resolved Login interface cannot be accessed from Plesk

dicker

Basic Pleskian
Server operating system version
Ubuntu 22.04.3LTS
Plesk version and microupdate number
Plesk Obisdian 18.055 Update 2
Hello,
As of today, I can no longer access the Plesk login interface with my laptop.
With a cell phone it only works without wifi. As soon as I turn on wifi, the Plesk login interface is no longer accessible.
I was able to enter the IP of the laptop as a trusted IP. But it still doesn't work.
Turning off fail2ban didn't work either.
Error message
The website is unavailable Hostname's response took too long.
 
It's been dealt with. For whatever reason I needed a new INternet IP. Restarting the router solved the problem.
 
Fail2Ban on your server has probably banned your IP address. This happens when frequent wrong login attempts are done.
 
How do you know it wasn't blocked? When you restarted your router it got a new ip, and that new ip is not banned. Do you know the previous ip and have you searched /var/log/fail2ban.log for that old ip?
 
I figured it out with my cell phone without wifi. Then I checked whether the IP was blocked. But it wasn't and there was nothing in the log file. Even when I turned off fail2ban it didn't work.
 
Back
Top