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

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