Symptoms
-
The plesk login command shows the rDNS instead of domain name
# plesk login
https://ec2-203.0.113.2.us-east-2.compute.amazonaws.com:8443/login?secret=<removed>
https://203.0.113.2:8443/login?secret=<removed> -
Server hostname is correct
# hostname
example.com -
The
psa.misctable has the correct entry# plesk db “select * from misc where param=’FullHostName'”
+————–+——————-+
| param    | val        |
+————–+——————-+
| FullHostName | example.com    |
+————–+——————-+
Cause
It is caused by a bug in the product with ID #PPPM-10470 which will be resolved in future Plesk updates.
Note: Consider subscribing to this article to be notified when the bug is resolved
Resolution
As a workaround, the following can be configured:
For Plesk Onyx
- Connect to the server via SSH;
- Add the following entry to
/etc/hostsfile, like:# echo “203.0.113.2 example.com” >> /etc/hosts
Where the IP 203.0.113.2 and the domain name example.com are the server public IP and domain name.
For Plesk Obsidian
- Connect to the server via SSH;
- Create Plesk database backup;
- Access Plesk database;
- Update the
pleskHttpHostparameter to the actual hostname, followed by the port 8443, for example:MYSQL_LIN: UPDATE misc SET val=’example.com:8443‘ WHERE param=’pleskHttpHost’;
