• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Plesk login redirects to Plesk login :-(

amba1980

New Pleskian
Hi,

since today, my plesk login at https://server.com:8443 redirects to the login page

https://xxx:8443/login_up.php?success_redirect_url=/

The websites still work and do not redirect. (All issues about redirect talk about domains. I'm talking about the login page.)

Command line login to my server works and user / passwords have been double checked.

I rebooted the (virtual) machine.

On a different VM with the same hoster, login still works (so it is not my browser).

All my machines are from the same hoster and use the most recent Plesk Obsidian on Ubuntu LTS 20.04

Any thoughts on what that is? How to fix it?

Thanks!
 
FWIW I figured it out. I had increased the max file upload size in a php.ini file to 16M but it didn't like the syntax and failed while parsing it (weird in itself). So this failure to run the code led to the login being thrown back to itself. Silly.
 
Not sure "how to close" this issue. Not possible because despite the tag it is not an issue in an issue mgmt sense?
 
Back
Top