• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Recent content by Azurel

  1. Azurel

    Broken systemd symlinks left behind after PHP version removal/deactivation

    Username: TITLE Broken systemd symlinks left behind after PHP version removal/deactivation PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE 18.0.80#1, AlmaLinux 8.10 PROBLEM DESCRIPTION After uninstalling PHP 8.3 and deactivating PHP 8.4 through Plesk, orphaned symlinks remain in...
  2. Azurel

    IMAP folder subscriptions lost after Plesk repair/reinstallation

    I had removed the Plesk installation (version 18.0.79#4) using dnf, accidentally. Afterwards I restored it to 18.0.80#1. After the package removal (130 packages), the Plesk GUI was no longer available. I tried dnf history undo 821 but that not worked. So I had to recover the installation from...
  3. Azurel

    Issue Why are obsolete Plesk packages not cleaned up?

    I ran into a serious issue while preparing an AlmaLinux 8 to AlmaLinux 9 upgrade using the official almalinux8to9 migration script. The script flagged some old packages as blockers for the upgrade. Removing the reported packages triggered a dependency chain reaction that took several core Plesk...
  4. Azurel

    IMAP folder subscriptions lost after Plesk repair/reinstallation

    Username: TITLE IMAP folder subscriptions lost after Plesk repair/reinstallation PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk 18.0.80#1, AlmaLinux 8.19 PROBLEM DESCRIPTION After accidentally removing Plesk packages with dnf, I restored Plesk using the...
  5. Azurel

    Resolved Install or Update Plesk issue with disable ProFTPD

    Thanks. Yes, the "better" way is "chkconfig ftp_psa off" in SSH, like I said 12 year ago. haha
  6. Azurel

    Resolved Install or Update Plesk issue with disable ProFTPD

    Username: TITLE Install or Update Plesk issue with disable ProFTPD PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk 18.0.80#1, AlmaLinux 8.10 PROBLEM DESCRIPTION I want disabled "ProFTPD" in /installer/select_components.html And get this: STEPS TO REPRODUCE Disable...
  7. Azurel

    Question Upgrade Almalinux 8 to 9 with Plesk installed

    Can't edit my post. After hours repairing, this steps finaly worked. The magic was first "plesk sbin nginxmng -d" Not its with 443 und 80
  8. Azurel

    Question Upgrade Almalinux 8 to 9 with Plesk installed

    I tried it today too and what a **** show. I get: I checked So I removed Results in plesk is uninstalled! WTF? After reinstall plesk its a big mess. Something is wrong with nginx, however no config errors results in What can I do?
  9. Azurel

    Question How should Redis Docker containers in Plesk be updated?

    Hello, I am using Redis as a Docker container managed through the Plesk Docker Extension. I have some questions about the proper maintenance workflow: How can I see the currently installed/running Redis version in Plesk? The Docker container overview only shows the image "redis:latest", but...
  10. Azurel

    Question Upgrade Almalinux 8 to 9 with Plesk installed

    Requirements for converting are: My server was originally upgraded from CentOS 7 to AlmaLinux 8, which is why my "PHP by OS vendor" is still stuck on version 7.2 (it's not used). Since this is the OS vendor PHP, I cannot remove or change it via the Plesk Components Installer. What is the...
  11. Azurel

    Issue GoAccess using significantly more RAM after update to Plesk Obsidian 18.0.79?

    Thanks. The process has just terminated on its own and the memory has been released again. I checked the Monitoring graphs (CPU, processes, network) for the last 30 days and there are no traffic or resource spikes around that time. The only metric that suddenly changed is the RAM usage, starting...
  12. Azurel

    Issue GoAccess using significantly more RAM after update to Plesk Obsidian 18.0.79?

    I have now disabled GoAccess for all (2) domains in Plesk. The "goaccess" directories were removed from the server as expected. However, I noticed that the process itself is still running and continues to consume around 50 GB of RAM. Is there a recommended "plesk way" to stop/clean up these...
  13. Azurel

    Issue GoAccess using significantly more RAM after update to Plesk Obsidian 18.0.79?

    I checked my RAM monitoring history and found that the increase did not start with the Plesk update. The memory usage started to increase suddenly on July 8th. Before that date, the server never ever used that much RAM. (02. July was a server restart because almalinux security patches)...
  14. Azurel

    Issue GoAccess using significantly more RAM after update to Plesk Obsidian 18.0.79?

    I'm trying to determine whether this is a bug or just a coincidence after upgrading to Plesk Obsidian 18.0.79. Since the update, I've noticed that the GoAccess report generation suddenly consumes MUCH more memory than before. Some details: AlmaLinux 8.10 with 128 GB RAM GoAccess is started by...
  15. Azurel

    Question EULA update after upgrading to 18.0.79 – some questions

    After updating from Plesk Obsidian 18.0.78 to 18.0.79, I was presented with an "EULA Update" immediately after logging in. I have a few questions regarding this process: Shouldn't a EULA update be communicated before installing the update? Version 18.0.78 did not mention that accepting a new...
Back
Top