• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Primary hostname change messed up plesk

T

torqhost

Guest
Hi,

I had a server as 1 hostname like ns1.something.com, reverse DNS was pointing to that and in server preferences it was also like this.
Then I needed to change the primary hostname to something like test.something.com. So I changed RDNS and modified server preferences to match. Now when I go to something.com:8443 I get a redirect to ns1.something.com which doesn't exist. How do I fix this?

Thanks
 
how exact did you change hostname?

please try to check Plesk httpd.conf (usually at /etc/httpd/conf/) and zz010_psa_httpd.conf (usually at /etc/httpd/conf.d/) if there are any redirect options
 
Back
Top