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

administrator login

L

loopy

Guest
Hello all ;)

I shortly began using Plesk and having a question regarding the login screen of Plesk:

When I'm connectin to Plesk with domain.tld:8443, I automatically get forwarded to hostname:8443.
Is it possible to turn this off?
I just want to see the domain-name like domain.tld:8443.

The customer shouldn't really know which hoster I'm using for my servers.

Any help would be appreciated....
 
Same prob with the ip adress.
Redirection to the hostname...

Anyway I tried to change the hostname of my first server, but this seems to be heavier than it sounds...

This is what i did already:

/etc/hosts
changed the hostname

/var/qmail/control/me
changed the hostname

hostname <newhostname>

mysql -u admin -p`cat /etc/psa/.psa.shadow`
use psa;
update misc set val='NEWHOSTNAME' where param='FullHostName';

Plesk restart:
/etc/init.d/psa stopall
/etc/init.d/psa stop
/etc/init.d/psa start

Still the same prob. Omg :confused:
Plesk still redirects to the old hostname:mad:
 
The problem isn't that you're clients are accessing something by an invalid address, it's that they're accessing it on an insecure protocol. Your clients are accessing http://domain.tld:8443, they NEED to access https://domain.tld:8443. This makes a big difference, and this WILL stop the redirection to https://hostname:8443/
 
ye, you're right.
Figured it out today.


Anyway thx your your help :)
 
Back
Top