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

Another subdomain/wildcard issue

M

midtempo

Guest
Hi,

I've another issue with wildcard subdomains, in that I've some 'real' subdomains (forum.domain.com, shop.domain.com, etc.) and also need to set ServerAlias *.domain.com for the main VirtualHost container.

The issue is that as the main VirtualHost container is the first in the httpd.include file, the server isn't getting down to the actual subdomain instructions, rather it's picking up the wildcard and racing off to the main site structure.

Is there anything I can do to resolve this (I've seen a couple of other threads here with the same problem, but no solution has been posted that I can see)

Running Plesk 8.3.0
Have set up *.domain.com in the dns zone
Have also set up forum.domain.com and shop.domain.com as dedicated entries in the DNS
Am aware that I have to only add instructions to the vhost.conf file and that I need to then run websrvmng

Help!!!
 
Back
Top