• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Recent content by Raul A.

  1. R

    Issue Magento Installation

    Hi, You can install it via PECL. Just go to Tools & Settings > PHP Settings > PHP 8.3 > Manage PECL Packages
  2. R

    Issue Constantly increasing Mysql memory usage problem

    What MariaDB version are you using? Older versions are known to allocate RAM and never release it.
  3. R

    Issue ssl client

    Hi, The Nginx Virtual Host looks like this: server { listen x.x.x.x:443 ssl; http2 on; server_name example.net; server_name www.example.net; server_name ipv4.example.net; ssl_certificate /usr/local/psa/var/certificates/***...
  4. R

    Issue ssl client

    You need to set the php settings in that location. Once that location is matched, the other location that handles PHP requests is no longer matched thus any PHP file in /secure will be treated like a plain txt file, exposing the php source rather the generated output. You could enable Proxy Mode...
  5. R

    Issue Random temporary Database connection error across all Plesk sites

    It sounds like all the database service connection slots get used up. By default, you should have 200 connections and 150 connections per user, so that no single user can use up all the connection slots. Can you run the following when it happens? plesk db "show full processlist"
  6. R

    Resolved Restart Dovecot, repair mail after Server reboot

    Plesk repair mail also restarted Dovecot throughout the repair process. That is why the service recovered after running it. A simple systemctl start dovecot would have had the same result. I have noo idea whythe Dovecott service was not enabled and since when.
  7. R

    Question Server Error 500 Plesk\Exception\Database

    Don't think so. The stored databases don't influence the number of connections. Your service might be stopped, or several users use up all the connection slots.
  8. R

    Resolved Restart Dovecot, repair mail after Server reboot

    Your Postfix service might not be set to start on boot. Please share the output of systemctl status postfix If you don't have "service; enabled" run systemctl enable postfix
  9. R

    Issue Cannot upgrade Plesk, error with mariadb-maxscale in installer

    That repository no longer exists. The upgrade fails because your package manager has a broken repository configured. If you disable the broken repository, the Plesk upgrade will work. Plesk still supports CentOS 7. I don't see any issues with using MariaDB 10.11. MariaDB 11.4 is supported since...
  10. R

    Issue cli subscriptions list not return same domain's count on web access

    Try plesk bin domain -l. Every subscription can have 1 or more websites.
  11. R

    Issue Cannot upgrade Plesk, error with mariadb-maxscale in installer

    Disable the repository. Yum doesn't complete any actions because one of the repositories (the MariaDB one) no longer exists. The repositories are in /etc/yum.repos.d/. Find the file that contains the MariaDB URL and change enabled from 1 to 0.
  12. R

    Resolved Plesk updato to 18.0.69 error

    I've just upgraded on my AlmaLinux 8 server and it worked. ===> Plesk database scheme upgrade has been started. Applying migrations from: /usr/local/psa/bootstrapper/pp18.0.69-bootstrapper/migrations/ Migration 18.0.69/2025-04-04-16-09-23_add_id_to_sessions.php applied ===> Plesk database scheme...
  13. R

    Resolved Plesk updato to 18.0.69 error

    Unfortunately, it's not possible to decrypt the Plesk PHP files. Can you select data from the sessions table?
  14. R

    Resolved Plesk updato to 18.0.69 error

    Try to run a Plesk repair: plesk repair db -v Looks like you might have a broken table in the psa database.
Back
Top