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

Resolved Second Plesk Server - Hostname

markusoswald

New Pleskian
Hi there,

i have a question if i´m right.

Server #1 - Plesk Server with hostname "server1.mydomain.com"

Set up a new A & AAA record redirecting to the correct IP adresses. (server2.mydomain.com)

When i type "server2.mydomain.com", i´ll be redirected to the IP adress. When i try to access Plesk via https://server2.mydomain.com:8443" i´ll be redirected to the admin-panel from server 1.

What kind of set-up did i need in the DNS managment to correctly refer to the server2?

Can somebody help me?

Thank´s a lot!
 
Hi UFHH01,

now i was able to set the correct hostname. I can now connect via server2.mydomain:8443.

Now i want to secure the panel with a valid certificate. When i type server2.mydomain.com i will be redirected to https://www.server2.mydomain/

I´m not able to correct the CNAME record, because there´s a conflict with the glue records.
 
Hi markusoswald,

When i type server2.mydomain.com i will be redirected to https://www.server2.mydomain/

Pls. go to "Home > Subscriptions > YOUR-DOMAIN.COM > Websites & Domains > Hosting Settings" and change the setting to the desired value.

Possible values:
Code:
Preferred domain *    www.YOUR-DOMAIN.COM
                      YOUR-DOMAIN.COM
                      None
                 
                    Select the URL (either with or without the www. prefix) to which site visitors will be redirected via a SEO-safe HTTP 301 redirect.
 
Back
Top