Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
The behavior was recognized as a bug identified with ID PPPM-15192. At this point, the only workaround I can suggest is to manually enable the module from Tools & Settings > Apache & Nginx Settings > Apache modules if the repair utility is ran. Our team will introduce a fix in one of the...
Hello, @mediengestalter . I am unable to replicate the reported issue by renaming a domain name, the Laravel application operates without issues. Could you please try running the repair utility for the domain name you are experiencing issues with:
plesk repair fs domain.tld
@superfun2k23 , is DNSSEC configured for the domain names you are experiencing issues with? If not, please refer to the following docs:
Configuring DNSSEC for a Domain
Hello, @superfun2k23 . Could you please try the resolution from the following article:
https://support.plesk.com/hc/en-us/articles/12376969003415-Email-delivery-fails-5-7-1-Command-rejected
Thank you for sharing your feedback. The complaint about the notifications has been brought to Cloudlinux's end. I will follow-up with more details as soon as possible. Thank you for your patience in the meantime.
Hello, @Rabah . If the issue still persists, I would recommend getting in touch with our Customer Support team so they can take a further look. If necessary, they can involve CloudLinux:
Contact Us - Plesk Support Will Help
mod_status was disabled on clean installations due to security reasons (it allows to view request details on neighbor sites). However, once it has been manually enabled, it should not be consequently disabled upon running the repair utility. I will double-check that further with our team and get...
Hello, @macadia . Thank you for the report. I was able to replicate the described behaviors after the subscription suspension and forwarded them to our team for further review.
Hello, Harm. Assuming that changing the shell to /bin/bash is not a desirable alternative, could you please try the first workaround from this article:
https://support.plesk.com/hc/en-us/articles/12389146640791-Git-Deployment-actions-in-Plesk-are-not-executed-application-name-command-not-found
From what I understand, the MySQL SELinux package version 1.0.13-1 did not set a policy for /usr/sbin/mariadbd. Thus, in scope of PPPM-14846 what our team did was to set SElinux context for /usr/sbin/mariadbd on AlmaLinux 9. They also ensured that the SELinux policies provided by Plesk do not...
Thank you for the provided details. Our team recently published an article about this issue and the same is caused by a bug in MariaDB as their packages are not fully compatible with the system SELinux policy.. Please find the details and the workaround here...
@safemoon , I am unable to replicate the issue with the following query:
curl -k -X DELETE -u root:pass -H "Accept: application/json" "https://plesk.example.com:8443/api/v2/domains/1"
I cannot confidently confirm whether the options you are planning to add won't cause any conflicts. Regarding the spoofing issue, maybe this could help:
https://support.plesk.com/hc/en-us/articles/12377380746903-How-to-protect-a-Plesk-mail-server-against-mail-spoofing
Thank you for the update and confirmation. Unfortunately, I am not sure what might be causing this specific issue. I would suggest opening a ticket with Plesk support for further investigation on your server. To sign-in and open a ticket please go to:
https://support.plesk.com
If you got your...
Hi, @Dmytro . What I can suggest is trying to uninstall ModSecurity and then re-installing it. Also, you might try switching "Run rules on" from Nginx to Apache or vice versa.
The error in question indicates that Plesk was unable to connect to the MySQL service. As far as I am aware, this often happens if there's interruption of the database service. Could you please check the status systemctl status mariadb and confirm if there is any correlation between the running...
@pleskuser67553 , a fix for the issue was introduced back in Plesk Obsidian 18.0.68. For what is worth, I can no longer replicate it on a fresh AlmaLinux 9.6 environment. Can you please open a new bug report with more details on the issue you are experiencing and steps to reproduce it? Thank you...
I am glad to hear the workaround helped. It is a product issue (PPPM-13576). When TLSv1 is disabled for Plesk service the proper operation of Premium Antivirus is prevented.