• 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 redirecting for client users

G

Gorgon@

Guest
Hi folks,

Please let me know if this is the wrong forum. First, some background. I've been thrust into supporting several virtuozzo containers for linux servers. I'm still learning how the whole thing works but I've been given my first 'mystery'. Hopefully this is not a newbie connection.

We are running virtuozzo on redhat5 and most of the containers are fc4. Plesk is v8.6. Recently the following problem started. When a customer goes to https://theirdomain:8443 and tries to login as a client (ie not root), they keep getting redirected back to the login page. It's same behavior as if the URL entered was http:// instead of https://. Yet they can login as root just fine. If you replace 'theirdomain' with their IP address, the problem goes away and a regular client user can login just fine.

I am personally pretty familiar with Plesk but not with the Plesk/Virtuozzo combo. I've been looking at the logs but no errors show up there. Any pointers on where to look next are appreciated.

Thanks,
Mike S
 
Login redirecting

Same issue her. Could it be a network settings not liking the fact our CP is governed by an SSL?
 
To sort out this issue you can try to access Plesk natively bypassing Virtuozzo CP.

Try to use http:domain:8880 instead of usual Plesk login via https.

Also you can disable offline management and login via https:domain:8443 to check it:
http://kb.odin.com/en/659
 
I should have posted our 'fix' back then.

A change to /etc/vzcp/addon_httpd_conf/rewrite.conf in container 1 was the issue. A new rewrite rule was breaking things. So I just commented out a line in plesk.conf (in the same dir) that Included rewrite.conf and problem was solved. :)

M
 
Back
Top