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

Resolved Host error after update to 18.0.72

MaasRick

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.72
Hi all,

After the upgrade to 18.0.72 I'm encountering the following problem:
My laravel application expects a certain domain to verify if it's routes need to pass to the first or second website. This worked like a charm after the update.

After the update, I get a "default-xxxxx" host instead of the actual domain from Plesk:
HTTP_HOST: default-82-165-51-122 - Host ($request->getHost()): default-82-165-51-122

Expected:
HTTP_HOST: hp.example.com - Host ($request->getHost()): hp.example.com

Now I have unmatched routes, so my application isn't working anymore.

Does anybody know a fix for this matter?
 
This also happened on my Ubuntu 24 Server. I also changed my Default Site to None to fix the issue
 
Hi @Sebahat.hadzhi Some more information for you, I just tested my site (that was set as default for the IP) at SSL Labs and it still shows as the default, so there's no notice that the site is SNI which is what I was expecting.
 
The behavior was identified as a bug with ID PPPM-15085. The fix will be introduced at one of the upcoming releases. In the meantime, the only workaround is setting Default Site to none in Tools & Settings > IP Addresses.
 
The behavior was identified as a bug with ID PPPM-15085. The fix will be introduced at one of the upcoming releases. In the meantime, the only workaround is setting Default Site to none in Tools & Settings > IP Addresses.
Affirmative, this fixes the issue. If you keep the website as default website, and turn nginx proxy mode off, it also works. This was my previous workaround. Now I have turned nginx's proxy mode back on, and set the default domain to none and it works.
 
Back
Top