• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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