Recent content by Azurel

https://mariadb.com/docs/release-notes/community-server/12.3/mariadb-12.3-changes-and-improvements Since 28 May 2026 It looks like the question is valid now? ;)

This is great! For everyone who has already tried the AlmaLinux 8 to 9 conversion: could you share your experience here? I'm particularly interested in how smoothly it went and how long the process actually took on your systems.

Thank you! As feedback: running `plesk repair web -php-handlers` worked as a validation check, and selecting a new PHP version did not modify any existing settings. However, there is still something that seems odd. I have three default Service Plans. Two of them have never been used, and I had...

5 hours ago my system updated to Plesk Obsidian 18.0.78 Update #3 but there is still no changelog https://docs.plesk.com/release-notes/obsidian/change-log/ I'm just mentioning it in case it was forgotten to be included in the changelog. ;)

with "Add or Remove Components" => /installer/select_components.html In my case, Roundcube is not installed, and no domain has been using PHP 8.2 or PHP 8.3 for a long time, as both PHP versions were disabled previously with 0 domains left. Only Service Plan with "Unlimited" use PHP 8.3. The...

Username: TITLE Not used PHP versions removed, but Plesk reports missing versions PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.78 Update #3 AlmaLinux 8.10 PROBLEM DESCRIPTION I uninstalled PHP 8.2 and PHP 8.3 because no domains on this server were using...

I've submitted a feature request: One side note: the features.plesk.com platform is rather frustrating to use. You can log in and submit requests, but there is no overview of your own submitted requests, no status updates, and no email notifications whatsoever – not even when a request gets...

Thank you for the clarification. That's unfortunate – I assumed DNS-01 support would include external DNS providers via their APIs, since that's essentially the main use case for it (so I think). Without that, the extension isn't really usable for anyone whose DNS isn't managed by Plesk itself...

Hi, I installed the new ACME SSL extension (ACME SSL extension - Plesk) because I need wildcard certificates. However, I'm confused about how the extension actually works. The configuration UI only shows three fields: - ACME Directory URL (required) - EAB Key ID (optional) - EAB HMAC Key...

I understand that increasing SecResponseBodyLimit fixes the issue technically, but why is setting it globally to 256 MB considered the recommended approach? Since this value applies globally (for each page request) to ModSecurity response inspection, couldn't this become a memory/performance...

Is this issue fixed? Its look like you must first upgrade to minimum 10.11.15 (there is MDEV-37138 fixed) and than upgrade to 11.8? Have anybody successful upgraded to 11.8 from 10.11.16?

I don’t think this is best practice. I simple disabled the SecRuleEngine for /plesk-stat/. So this works for me:

I would strongly recommend listing all theoretically available tools in the “Web statistics” selection box. Tools that are not yet installed should be shown in a disabled state and labeled with “(needs installation)”. Additionally, it might be helpful to include a link to a knowledge base...

ACME already supports around 200 built-in integrations for registrar APIs, which typically remain very stable over time. It would be great if Plesk could incorporate these integrations directly into its certificate management. That way, users could simply select their provider, enter their API...

Thanks, that solves my problem. It was the wrong URL. :eek: