• 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 "Optimizer" / Performance Booster

LTUser

Regular Pleskian
Server operating system version
Ubuntu 20.04 (MariaDB 10.6)
Plesk version and microupdate number
Newest
Hello everyone,

I have a problem with the optimizer, which doesn't work if the domain can only use https / port 443, but returns a 410 (service gone) on port 80.

Can the optimizer be adjusted to use port 443 instead of port 80?
 
Ok...
Additional directives for HTTP
<Directory /var/www/vhosts/mydomain.org>
## CharsetDefault UTF8
Options -FollowSymlinks
Options -Indexes
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteBase /
RedirectMatch 410 ^/*.*$
</IfModule>
</Directory>
Any hints?
 
I have no clue how this could in any way interfere with Performance Booster settings. Could you please show an example why Performance Booster does not work with these settings? How can you see it?
 
Back
Top