Search results

You'll for sure need to remove "FollowSymlinks" and only leave "SymLinksIfOwnerMatch", because by default symbolic links are only allowed for the same owner. If you have the normal "FollowSymlinks" in the statement, it will fail. About the other entries: I do not know more. 403 is a permission...

Yes, if you cannot use a hostname, IPv4 is your option.

This is a known issue PPPM-10421. As there are at least two ways to circumvent it it is not a priority for fixes. You could for example use the generic FTP host name instead.

Sitejet Builder cannot be migrated to another server. As far as I know only Sitejet Support can update your key and links to the new location so that you can access the same website again from another server.

The error messages point to an unstable network connection or an issue with the remote FTP storage server.

Wrong approach, because then the .htaccess file in the layer above also works on the subdirectory. It won't work if you nest domains. Instead: Create additional domain names as "alias". Your multisite installation will react on the correct domain. That's what it is for. It is NOT advised to...

You are right. I should have just ignored the post or removed it and went on. Or I should have translated it as a courtesy translation as done before in some other posts. With my post I meant to bring to your attention that it is also a form of politeness to enable all users on a forum to...

No, it just occupies some disk space and consumes some cpu time, but nothing major.

When a domain is configured to use a specific PHP version, you'll find a configuration in /opt/plesk/php/<version>/etc/php-fpm.d. With such a configuration file a pool is considered "defined" and PHP will work as expected.

/opt/plesk/php/<version>/etc

Yes, you can modify the rule accordingly. But be aware that any other file with "wp-" in its name will also trigger it. You do not (and should not) add a new "failregex" per line. Just start the first line with it, but then add more filter lines underneath omitting an extra "failregex="...

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?

https://www.plesk.com/blog/product-technology/sitejet-commerce-add-a-store-directly-in-plesk/

You're only showing part of the log string. Normally you'll at least also need to know the response code of the web server. For example if it is 404 you could formulate a rule like ^<HOST> .*"(GET) /.*wp-includes/wlwmanifest.xml.*" 404.*

Postings in another language but English are normally quite useless in an international forum.

Please open a support ticket with Plesk support so that an engineer can check it on your server.

What exactly is the custom configuration that you have that you are blocking port 80?

Thank you for the feedback. I checked PPM-12015 and it is an open case that still needs to be resolved. It's been accepted as a product issue and will be fixed in a future version of Plesk.

As the demand is very low, I do not expect CL 9 to be supported soon. It is realistic that the earliest estimate for consideration of CL 9 support is 2025, and from there it might still take a while until it is actually supported.

Ceasing support only means that you won't be able to update Plesk to newer versions on the existing platform. Currently I have not heard of plans to extend support for EOLed operating systems just because the vendor offers security fixes for "high" level issues. Rather migrate now than later.