• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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