• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs wildcard subdomain

Martin_Sauer

Regular Pleskian
User name: Martin_Sauer

TITLE

wildcard subdomain

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 7.5, Obsidian 18.0.26, web host edition, apache + nginx (in default config without custom folder according last update)

PROBLEM DESCRIPTION

The behaviour as outlined in
does no longer work.

When creating the wildcard subdomain, the resulting wildcard domains are not added to the server directive in nginx.conf and also not in httpd.conf resp. the related vhost files. By adding the wildcard subdomains by hand it works again.

STEPS TO REPRODUCE

As outlined in the article

By following those steps, the wildcard subdomain is not properly used as expected.

ACTUAL RESULT

nothing happens, nada, zero, null, muerto

EXPECTED RESULT

All subdomains without explicit subdomain settings should be redirected to the original domain, where the original domain website handles the domain names.

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
From developer:

Linked article Adding Wildcard Subdomains (Linux)
work as planned for:
CentOS Linux release 7.7.1908 (Core) and Ubuntu 18.04.4 LTS
for dev and prod environments.

You may check apache config after add wildcard subdomain:

Code:
# cat /etc/httpd/conf.d/zz010_psa_httpd.conf | grep wildcards
IncludeOptional '/etc/httpd/conf/plesk.conf.d/wildcards/*.conf'
# ls -la /etc/httpd/conf/plesk.conf.d/wildcards/
total 4
drwxr-xr-x. 2 root root   51 Apr 27 09:08 .
drwxr-xr-x. 7 root root 4096 Apr 24 18:45 ..
lrwxrwxrwx. 1 root root   74 Apr 27 09:08 <YOUR_DOMAIN>.conf -> /var/www/vhosts/system/_.<YOUR_DOMAIN>/conf/httpd.conf
 
cat /var/www/vhosts/system/_.<YOUR_DOMAIN>/conf/httpd.conf | egrep \\*.<YOU_DOMAIN> -A2
                ServerAlias "*.<YOU_DOMAIN>"
                UseCanonicalName Off
 
--
        ServerAlias "*.<YOU_DOMAIN>"
        UseCanonicalName Off

if the problem will remain after that I recommend contact Plesk support.
 
Same report here Forwarded to devs - Wildcard Subdomain not working
For me that file is empty. Its have only comments.

cat /var/www/vhosts/system/_.<YOUR_DOMAIN>/conf/httpd.conf | egrep \\*.<YOU_DOMAIN> -A2
result: no output

/var/www/vhosts/system/_.<YOUR_DOMAIN>/conf/httpd.conf
#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
#IF YOU REQUIRE TO APPLY CUSTOM MODIFICATIONS, PERFORM THEM IN THE FOLLOWING FILES:
#/var/www/vhosts/system/_.DOMAIN.com/conf/vhost.conf
#/var/www/vhosts/system/_.DOMAIN.com/conf/vhost_ssl.conf

CentOS Linux 7.7.1908 (Core) with Plesk Obsidian Version 18.0.26
 
Back
Top