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.
I've tried asking before on a proper way to mark my thread as resolved, however didn't get a response to that particular query. From what I had searched in the forum is that I don't have sufficient privledges to mark it as resolved myself. Is this something I could do myself or what is the process?
That solution worked. We had enabled skip-name-resolve to mitigate some aggressive crawls from AI think tanks on our real estate servers. Looks like this inadveterently prevented localhost to resolve to 127.0.0.1.
I recently upgraded both the source and destination servers to MariaDB 11.4 and Plesk Obsidian 18.0.64. File sync works without issues, and the migrator is able to create database objects; however, the migration fails when syncing database records with the following error:
Interestingly, when...
After upgrading to Plesk Obsidian 18.0.64 and MariaDB 11.4 (from 10.11), I am encountering a persistent deprecation warning when running plesk db commands:
I’ve confirmed that /usr/bin/mysql is correctly symlinked to mariadb:
To further troubleshoot, I also added an alias in .bashrc to alias...
Chrooted should work fine. We have all our subscriptions set to chrooted when they want SFTP access. Check to see if the default port 22 is accessible on your system, or if you've customized the port check that one. Additionally, make certain that you don't have any allow/deny rules that...
I tried using the skip-ssl configuration, but the same error occurred during the upgrade. I ended up following the instructions on MariaDB's website to enable TLS for the database server: Securing Connections for Client and Server
I used OpenSSL to self-sign a certificate, and after that, the...
Thanks for the resource! I did use the repository builder, which is how I initially set up my current repository. After adjusting MaxScale to maintain the current version instead of the latest, the warning about MaxScale is no longer appearing. However, the issue with MariaDB's TLS/SSL...
Thanks for the quick response. I've tried this but it just creates a new repo primarily for the MariaDB Server. Unfortunately my issue is with the MaxScale repo.
This is what the repo looks like built by the suggested tool:
So not having any issues with the MariaDB repo. Do you know if the...
I am encountering an issue while attempting to upgrade from Plesk Obsidian 18.0.63 to 18.0.64 on a CentOS 7 server. During the upgrade, I receive the following error related to the MariaDB MaxScale repository:
The upgrade process is failing due to this, with the following message:
I have tried...
We're getting this error on 6 brand new servers after last night's update. None of the servers have any Docker packages installed and there are no Docker extensions installed.
Let's Encrypt expires after 90 days and I see that it is possible to automatically renew it. Is this possible without having to change the primary domain's certificate back to the paid one every 90 days? We manage over 300 domains and it would be too costly to have to do this every 3 months. I...
We could use Let's Encrypt on the aliases, however I don't see anywhere to bind certificate to a domain alias in Plesk. Only for the primary domain. Please advise.