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

Login Page shows "Continue" button

i got a different problem but it has too to do with the Login Page.... mine still shows the old one but there is a temporary alternative which works on me and on you:

Load the Plesk with https://controlbooth.com:8443/login_up.php3 instead of just https://controlbooth.com:8443....


That's the alternative that works i found by me actually and it displays the new plesk screen on you too so enjoy it until someone can help us ^^


MfG sinnLoser
 
You can easily fix it though...

Just temporarily stop your firewall (service iptables stop) or open up port 11444 (TCP). That way, the redirect to that funny URL will work. After you have been redirected once, and accepted the license agreement, you can start the firewall again (service iptables start) or close the TCP port again.

That's it. It's a one time only event. After that, the 'normal' login on port 8880 will work.

Tino
 
You can easily fix it though...

Just temporarily stop your firewall (service iptables stop) or open up port 11444 (TCP). That way, the redirect to that funny URL will work. After you have been redirected once, and accepted the license agreement, you can start the firewall again (service iptables start) or close the TCP port again.

That's it. It's a one time only event. After that, the 'normal' login on port 8880 will work.

Tino

Tino -

Works perfectly! Thanks!
 
Better idea if you don't want Single Sign On enabled ( only good if your using Plesk Billing ) is to just turn it off and that continue will go away.

/usr/local/psa/bin/sso -d = Disable
/usr/local/psa/bin/sso -e = Enable
 
Billing, SSO fix, firewall rule

Hello,

I tested the fix described above but find the firewall rule must stay in place for it to work ongoing. just being able to see Billing work was great. Thanks Tino!

Since the relay through SSO seems to happen every time, not once, and will need to support customers looking at their billings - so restriction to an IP address won't work - won't the firewall rule need to be in place to allow all access to 11444? is there an issue with doing that?

as an aside, the test also showed the SSO cert was a Parallels cert not my current panels' cert, however I was able to login (and add an exception to the browser) whilst I try to make more sense out of post http://kb.odin.com/en/6138
 
I can't login to my Plesk at all. I go to the URL on por 8443 (tried 8880 as well) and it quickly shows a 'Continue' button after which it redirects to a URL that says 'Server Not Found' (login.php3?window_id=&requested_url=). Any ideas? Please if anyone has advice!
 
Like stated before, this is most probably a firewall issue.
To make sure that that is the case, stop the firewall and try again.

If that works, open up the required ports in the firewall.

Tino
 
Back
Top