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

Can't login via hostname (303 See Other response) Plesk 10.4.4

Alexander Mills

New Pleskian
For legacy reasons, we are forced to stay with Plesk 10.4.4, however when we try to login via the server hostname, we receive a 303 See Other response from the server, with another header set to the IP address of the server.

Essentially Plesk is telling us that it wants us to login from the IP address and not from the hostname we have set. However, if I login from an alternative hostname, for example, one of the domains hosted on the server, (using HTTPS and port 8443), I can login successfully. Can anyone shed some light as to why this is happening?
 
For legacy reasons, we are forced to stay with Plesk 10.4.4, however when we try to login via the server hostname, we receive a 303 See Other response from the server, with another header set to the IP address of the server.

Essentially Plesk is telling us that it wants us to login from the IP address and not from the hostname we have set. However, if I login from an alternative hostname, for example, one of the domains hosted on the server, (using HTTPS and port 8443), I can login successfully. Can anyone shed some light as to why this is happening?
 
Hi Alexander Mills,

did you notice, that there is a => Plesk 10.x for Linux Issues, Fixes, How-To <= Sub-Forum? :D

It could be, that you use "sso" and didn't configure/modify/adjust the sso - preferences.

MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -u admin psa -e"select * from misc where param='FullHostName'"

/usr/local/psa/bin/server_pref
--show

/usr/local/psa/bin/server_pref --update -hostname <new hostname>

/usr/local/psa/bin/sso -s -server https://<new hostname>:11443 -url https://< new hostname >:11444



 
I didn't, but thank you!

Unfortunately for the second command "--show", returns 'show' is not a command for me I can't see an equivalent either, by using the --help flag - any ideas?
 
Regarding SSO, we don't use it, I believe we leverage the API to retrieve the user credentials and then populate a simple HTML form, which is submitted to Plesk
 
Hi Alexander Mills,

... as answered in your other thread:

It could be, that you use "sso" and didn't configure/modify/adjust the sso - preferences.

MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -u admin psa -e"select * from misc where param='FullHostName'"

/usr/local/psa/bin/server_pref --show

/usr/local/psa/bin/server_pref --update -hostname <new hostname>

/usr/local/psa/bin/sso -s -server https://<new hostname>:11443 -url https://< new hostname >:11444

 
Hi Alexander Mills,

I can't see an equivalent either, by using the --help flag - any ideas?
I just reviewed the Plesk 10.4 documentation and must admit, that there is no equivalent in your used Plesk version:

What is your output of:
MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -u admin psa -e"select * from misc where param='FullHostName'"

Can you confirm, that you have an existing DNS - entry ( A-record ) for the used hostname? ( setup over your nameserver, maybe the initial one from your domain registrar? ) ?
 
Back
Top