• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. Daerik

    Resolved Plesk Migrator Failing to Sync Database Records After Server Upgrade

    -- On a side note, do I just ask in my threads for a guru to mark it as resolved or do I get a buddy that I can DM? :)
  2. Daerik

    Resolved Plesk Migrator Failing to Sync Database Records After Server Upgrade

    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?
  3. Daerik

    Resolved Plesk Migrator Failing to Sync Database Records After Server Upgrade

    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.
  4. Daerik

    Resolved Plesk Migrator Failing to Sync Database Records After Server Upgrade

    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...
  5. Daerik

    Issue Deprecated Program Name Warning After Upgrading to MariaDB 11.4

    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...
  6. Daerik

    Question How to use SFTP

    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...
  7. Daerik

    Issue Error Upgrading Plesk Obsidian 18.0.63 to 18.0.64: HTTPS Error 404 - Not Found (MaxScale Repo)

    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...
  8. Daerik

    Issue Error Upgrading Plesk Obsidian 18.0.63 to 18.0.64: HTTPS Error 404 - Not Found (MaxScale Repo)

    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...
  9. Daerik

    Issue Error Upgrading Plesk Obsidian 18.0.63 to 18.0.64: HTTPS Error 404 - Not Found (MaxScale Repo)

    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...
  10. Daerik

    Issue Error Upgrading Plesk Obsidian 18.0.63 to 18.0.64: HTTPS Error 404 - Not Found (MaxScale Repo)

    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...
  11. Daerik

    Resolved API call failed: HTTP Error 500: Internal Server Error

    I stand corrected. I had removed ImunifyAV on 4 servers and Imunify QuickPatch on 1 server. I stopped receiving notifications on the 1 server.
  12. Daerik

    Resolved API call failed: HTTP Error 500: Internal Server Error

    Imunify QuickPatch extension was removed from 5 servers. Still receiving error.
  13. Daerik

    Resolved API call failed: HTTP Error 500: Internal Server Error

    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.
  14. Daerik

    Issue Permanent SEO-safe 301 Redirect from HTTP to HTTPS Effecting Aliases

    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...
  15. Daerik

    Issue Permanent SEO-safe 301 Redirect from HTTP to HTTPS Effecting Aliases

    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.
  16. Daerik

    Issue Permanent SEO-safe 301 Redirect from HTTP to HTTPS Effecting Aliases

    Thank you for the reply, virtubox. Unfortunately Let's Encrypt does not issue organization or extended validation certificates which is unacceptable for some clients. If there was a way to bind an SSL certificate generated by Let's Encrypt directly to the aliased domain while keeping the...
  17. Daerik

    Issue Permanent SEO-safe 301 Redirect from HTTP to HTTPS Effecting Aliases

    I am using Plesk Onyx Version 17.5.3 Update #24. I have Domain->Hosting Settings->Permanent SEO-safe 301 redirect from HTTP to HTTPS checked. I'm looking for a way to force HTTPS on the primary domain in the Plesk Panel without forcing HTTPS on the aliases. Alias http://alias.tld for the...
Back
Top