Recent content by VNick

We've released a new version of the MCP extension. It resolves some installation issues, includes an OAuth authorization by default (which is standard for remote MCP servers), and sports an up-to-date knowledge base.

You have a real opportunity to influence the early development of this extension by providing your feedback — especially today, while it is in a very rapid development phase. You can install it today using the Extension Catalog directly from the Plesk UI, or by running plesk bin extension -i...

Introducing the Plesk and WP Toolkit MCP Server Extension (Early Beta) I'm excited to announce the first public beta of the Plesk and WP Toolkit MCP Server extension! This version is still quite early in development and currently supports only Plesk Obsidian for Linux. What is MCP? Model...

This configuration is required only if you observe HTTP 421 errors in logs for paths related to PPE and/or webmail.* domains.

In case you are using Plesk Premium Email extension and experience related issues with it after the hotfix, you may replace the /etc/nginx/conf.d/fixssl.conf content with: proxy_ssl_server_name on; proxy_ssl_session_reuse off; map $host $webmail_host { ~^webmail\..+ $host...

https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18071-mu1 - just to be clear that the fix is available in Plesk 18.0.70.3 and 18.0.71.1.

That's a different issue, and it would not have been broken today. If you had this issue before, you probably had it for a longer time. Possibly you have customized reverse proxy configuration (likely nginx in your case) that supplies incorrect SNI host name to Apache.

What's the corresponding error message in the logs (error_log)?

This is an issue caused by additional security checks introduced by your OS vendor in the Apache 2 binaries, which makes it reject requests from behind nginx reverse proxy with its default settings in case a site is using SSL settings different from the default vhost (which would typically be...

Sorry, I cannot. Again, there's no "conversion" per se. Mostly just removal of incompatible settings.

The logic is part of the MariaDB upgrade feature. We use the upstream MariaDB packages as is (we do not rebuild them). So this is not something that is intended to be customizable by end users. They can just perform the necessary adjustments manually in any way they see fit, since the feature...

We may modify default config files (such as /etc/my.cnf or /etc/mysql/my.cnf), but we don't overwrite them entirely. Yes, in case these changes would prevent the new version of DB server from startup and normal operation. In case we remove some directives, we backup the corresponding...

@igorosabel , we've just released an update to address this issue. Thanks for reporting it. https://docs.plesk.com/release-notes/obsidian/change-log/#php-250123

Please provide your Plesk and Docker extension versions.

Sure. We actually use the upstream MariaDB packages for this feature. They are not modified in any way by Plesk (and Plesk doesn't interfere with mariadb-check on the service startup), so you should follow MariaDB Community Bug Reports and Feature Requests to report such bugs into the upstream.