• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Will changing the Hostname of a server AFTER plesk was installed mess anything up?

Commander

Basic Pleskian
Server operating system version
Windows Server 2022
Plesk version and microupdate number
Version 18.0.48
I recently created a VPS account at a hosting company. Plex as pre-installed on this server.

But every time I create a new domain from within Plex on this server (that used a private nameserver), I had issues with domains not resolving properly and reliably.

After filing a trouble ticket, the hosting company said that they detected that the server's hostname was incorrect - the original hostname had dashes "-" instead of periods "." in it - the original hostname WAS set to 129-34-35-234.serv.company.net, and they changed it to 129.34.35.234.serv.company.net.

Since I don't see a setting inside Plesk that will allow me to *change* the hostname, I'm assuming the hostname was either manually entered when plesk was first installed on the server, or the installer automatically detected the name during installation.

And when the hosting company corrected the hostname, they did it OUTSIDE of plesk.

So, my question is this...

Is it harmful to change the hostname OUTDSIDE of plesk *AFTER* plesk has been installed? Meaning will every function of Plesk still work properly when the hostname has been changed from outside of plesk?
 
Back
Top