• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue 18.0.72 broke IP Default Webites Ubuntu 24

LRLD

Basic Pleskian
Server operating system version
Ubuntu 24.04.3
Plesk version and microupdate number
Plesk Obsidian 18.0.72 Web Pro Edition
Hi,

Just installed 18.0.72 and two things, please remove the "custom template warning" unless you have actually changed the templates!!
Secondly, now the site assigned to be the default for the IP shows the Plesk default page!
Now what has changed?? All my SNI sites are fine!

I've tried removing the previous fixssl.conf to test but no, still the Plesk default on the default site for the IP!

This is affecting both of my servers! even with new custom templates.

TIA
 
Same situation, thanks for the update on the fix. Another Plesk update fail! That is two in a row now that caused serious issues. Testing needs to be much better before these updates are released.
 
Just installed 18.0.72 and two things, please remove the "custom template warning" unless you have actually changed the templates!!
Secondly, now the site assigned to be the default for the IP shows the Plesk default page!
Now what has changed?? All my SNI sites are fine!
I've tried removing the previous fixssl.conf to test but no, still the Plesk default on the default site for the IP!
This is affecting both of my servers! even with new custom templates.
FWIW In our case(s), we have had none of the above, post the upgrades to 18.0.72. No issues at all in fact.
Caveat: We don't use any Custom Templates (in the same way you may be doing...) and we don't (currently) have any laravel driven applications
I've added a link to this, in the other similar thread that's been posted.
 
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 as already suggested by @LRLD .
 
Back
Top