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

Unable to change default site for shared IP

J

JaredF

Guest
I am unable to change the default site for a shared IP. I am running 10.3.0 but also had this issue with 10.1.1 on Ubuntu 10.04.

Steps to reproduce:

1) Create original.example.com on IP
2) Create new.example.com on IP
3) Tools & Utilities > IP Addresses > Select IP > Select new.example.com for Default site drop down

Open IP in browser and it will display original.example.com for IP, which is wrong

4) Domains > original.example.com subscription > Suspend

Open IP in browser and it will display new.example.com for IP, which is correct

5) Domains > original.example.com subscription > Activate

Open IP in browser and it will still display new.example.com for IP, which is correct

6) Tools & Utilities > IP Addresses > Select IP > Select original.example.com for Default site drop down

Open IP in browser and it will display original.example.com for IP, which is correct

7) Tools & Utilities > IP Addresses > Select IP > Select new.example.com for Default site drop down

Open IP in browser and it will display original.example.com for IP, which is wrong (see step 4 and 5 to fix)

I'm pretty sure this is a bug. I've tried tracing the Apache config files but it gets real tricky real fast. Although the hacky deactivation trick works above I'd be great to figure out what is going on here. I'm thinking it might have something to do with the load order for the various configuration files.

Cheers.
 
Back
Top