• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk Login issue

D

Dennis Beverloo

Guest
Since this morning I can't login to Plesk anymore. Yesterday it worked fine and nothing changed since then.

I enter my username and password (which is the correct password as I've checked it in the /etc/psa/.psa.shadow file), then when I click Login, the page goes white and instantly goes back to the login page, without showing any kind of error message. What could be the problem here?
 
Did you tried to find a reason in /var/log/sw-cp-server/error_log file?
 
A few hours after I openend this topic I could suddenly log in without any problems. It seemed that all my login attempts were actually successful because there were multiple sessions open from my IP, the panel just kicked me back to the login screen. However, later that day I got the same problem again, and still now I can't login.

I'm getting these messages in the error log:

2010-08-25 16:19:15: (connections.c.299) SSL: 1 error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
2010-08-25 16:19:15: (connections.c.299) SSL: 1 error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure

Any suggestions?
 
2010-08-25 16:19:15: (connections.c.299) SSL: 1 error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure

The possible cause such reports is brute-force attack on sw-cp-server port(8880) which may to block a normal sw-cp-server working. In addition can to recommend to check security log and search strings like:
Jan 13 02:54:48 plesk9 sshd[9890]: Failed password for root from ::ffff:125.208.21.3 port 8880 ssh2
Jan 13 07:32:43 plesk9 sshd[11756]: Failed password for root from ::ffff:125.208.21.3 port 8880 ssh2

or similar.
You can to block the hosts which run brute force attack for resolve such type of problems. There are couple possible ways to do this:

1. Blocking hosts by firewall rules.
2. Blocking hosts by tcp wrappers.
3. Thirdparty solutions.
 
I found the solution to my problem.
If I remove the cookie that stores the PHPSESSID, I have no problem logging in to Plesk.

I almost never click the logout link in Plesk, could that cause the problem? (session cookie remains when not logging out?)
 
Yes, it can be reason of problem but most probably it can be related to browser settings too. Did you tested it with different browsers?
 
Back
Top