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

Resolved After upgrade to Plesk Obsidian - error on login to Plesk admin panel

Jürgen_T

Regular Pleskian
Since I upgraded yesterday from Onyx to Obsidian I cannot login to my Plesk admin panel. Trying to get access in a browser through https://www.XXX.de:8443/admin/ a screen plesk web admin edition appears where I am ask for username and password. Giving this information an error screen with error 500 appears and shows the messages:

  • Type: PleskFatalException
  • Message: Original link and target URL should be on the same domain.
  • File: login_up.php
  • Line 94

Using "Plesk repaire" from the same screen let me go directly to my admin panel what works.
Any idea how to solve this?
 
Try to fix it in CLI with

# plesk repair installation
 
usually when you're open plesk CP URL it looks like
https://<PLESK_HOST>:8443/login_up.php?success_redirect_url=http%3A%2F%2F<PLESK_HOST>%3A8443%2F
are plesk server hostname and redirect URL equal before you submit login and password at authentication form ?

probably there are some wrong cached URL's in your browser history ?
 
After just checking 9496 rows of the plesk_18.0.19_installation report I have read your comment - and I guess, you are right! I am happy that this was the simple problem I did not realize before:-(
Thank you for your help! Now I will look for the TLS v.1.3 support what was announced for Obsidian:)
 
Back
Top