• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue In version 18.0.57 #1, wildcard domains do not work correctly

HoracioS

Regular Pleskian
Server operating system version
Ubuntu 22.04.3 LTS aarch64
Plesk version and microupdate number
18.0.57 #1
Since v18.0.57 #1 wildcard domains do not work anymore.
The wildcard SSL certificate is correct and up to date.
Now wildcard domains are redirected to the server's IP and it directs to the default Plesk site, of course with an SSL certificate error as it does not correspond to that domain.

It worked for years, but now it has stopped working.

Best regards,
Horacio
 
Have you checked the content of /var/www/vhosts/system/<wildcard domain>/conf/* files for the wildcard domain in question? What document root or redirect is set in the conf files?
 
Yes, there are dozens of domains in that condition that magically stopped working after the update. The redirects are done through the .htaccess file

RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} =https
RewriteRule ^(.*)$ http://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^.*$ https://siteabcdfe.com [L,QSA]
 
When you remove the .htaccess file from one of the wildcard domain document roots and instead put an index.html file into it, is that file shown when you request an undefined subdomain so that the wildcard steps in?
 
Back
Top