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

Forget password doesnt work!!

Roberto Nunez

Basic Pleskian
Hello,
I can detect that domaindotcom:8443/get_password.php?plesk_user_exception=true

ERROR: PleskPermissionDeniedException

Access denied
0: auth.php3:603

I never received the password...

Thanks for solved this error.
 
I can't reproduce it on my test Plesk server.
Do you have any related errors in /var/log/sw-cp-server/error_log and /usr/local/psa/var/log/maillog ?
 
Hi Igor,
I try https://domain.com:8443/get_password.php but it doesnt work with this message:

ERROR: PleskPermissionDeniedException
Access denied.

0: auth.php3:603

I looking for errors in /var/log/sw-cp-server/error_log
2010-11-10 11:46:08: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2010-11-10 11:46:24: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2010-11-10 12:25:10: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2010-11-10 12:25:10: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2010-11-10 12:25:10: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2010-11-10 12:25:10: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2010-11-10 12:25:26: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2010-11-10 12:37:52: (connections.c.299) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
2010-11-10T12:39:48-02:00 ERR (3): Forgery protection token check failed.
2010-11-10T12:40:31-02:00 ERR (3): Forgery protection token check failed.
2010-11-10T12:41:18-02:00 ERR (3): Forgery protection token check failed.
2010-11-10T12:44:16-02:00 ERR (3): Forgery protection token check failed.
2010-11-10T12:44:39-02:00 ERR (3): Forgery protection token check failed.
2010-11-10T12:45:03-02:00 ERR (3): Forgery protection token check failed.
2010-11-10T12:45:05-02:00 ERR (3): Forgery protection token check failed.
2010-11-10T12:46:10-02:00 ERR (3): Forgery protection token check failed.


and /usr/local/psa/var/log/maillog (none).

Thanks.
 
It looks like that there is broken correct Plesk permissions. Make sure, at least, that Plesk user 'psaadm' belongs to group 'psaadm':

# grep ^psaadm /etc/group

If you can't fix broken Plesk permissions by yourself - contact Support Team.
 
We have the same problem here.
The sending of the password worked only one time.
The next customer who wanted to have the pw sent, first was redirected to the same pw-send formular, then he got the exception page as described above.
The error is repeatable from now on.
We have the same errors in the logs - and psaadm is member of psaadm.
 
Thanks! The patch fixed it.
Btw.: we also had the problem on FF 3.5 - not only on IE8
 
Do you mean that now you have the same problem with FF 3.5?
 
oh no. It's working now with both browsers!
Before we had the problem in FF and IE.
 
Back
Top