• 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 access problem

M

mattvick

Guest
I'm currently unable to access Plesk from within my company network.

I can view the login page:

https://<domain name>:8443/login.php3

but when I hit 'login' I'm brought back to the login page, without any errors as there would be if my username/password were incorrect.

Will someone please tell me if Plesk needs any ports to be open, other than 8443?

Is there another reason that might be causing this issue?

Regards,

Matthew
 
Your account is probably locked due to too many incorrect login attempts (you can unlock this via the Plesk database, see the SW-Soft Knowledgebase, but you can also wait untill your account gets unlocked).
 
I can sign in from outside of my office network without any problem, so my account can't be locked.
 
Since it locks your login via your IP address, it can be locked. That explains why you can access it outside your network. Port 8443 is the only port that needs to be open to login to Plesk.
 
Back
Top