• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by anatol

  1. A

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    Thanks for Grafana solution, I applied it and solved. This link does not open anything.
  2. A

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    A this moment my temporary solutions are: 1. For Grafana commented line: added line: 2. For DSA-1024 warning created file: with the code: For munify360 is not needed a temporary solution, even it is warning, the update is working.
  3. A

    Resolved Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

    Since 31.05.2025 we have the same issue on the server with Ubuntu 24.04.2 LTS and Plesk Obsidian 18.0.70 Web Pro Edition. It is not possible to update the available packages any more. See the output of "apt update" in the attached files. The root cause seems to be that Plesk and Imunify360...
  4. A

    Question How to extract the MySQL dump of Docker based DB from and old server backup?

    And how about files from /var/docker/mysql_docker, does Plesk include them in backup?
  5. A

    Question How to extract the MySQL dump of Docker based DB from and old server backup?

    I'm trying to restore an old version of a MySQL 5.7.27 database that was running in Docker, but I don't have a database dump file. However, I do have access to an old full server backup in Plesk Backup Manager. My questions are: Is it possible to extract the database dump from the full server...
  6. A

    Issue Mapping bitnami/mysql docker container in Plesk

    After research, I discovered that Bitnami containers are non-root containers, started by default with a non-root user. The mounted files and directories must have the proper permissions for the UID 1001. To make everything working properly I did in this way (if there are better solutions, please...
  7. A

    Issue Mapping bitnami/mysql docker container in Plesk

    The issues are solved. Here is my post about how I solved them.
  8. A

    Issue Mapping bitnami/mysql docker container in Plesk

    Yes, and it was created by Plesk when I saved the container settings.
  9. A

    Issue Mapping bitnami/mysql docker container in Plesk

    I have problems with bitnami/mysql:8.1.0-debian-11-r57 image container in Plesk. When I don't any mapping settings the container starts correctly and the DB works properly. If I set mapping, the container doesn't start al all, but after changing the rights of mapped directories of Ubuntu, I can...
  10. A

    Issue Docker Problems in Plesk Obsidian 18.0.60

    For running Shopware 6 the best DB solution is using MySQL 8. With Maria DB which is by default in Plesk there are a lot of migration (SW5-> SW6) problems. After long tests we found what the best solution is to use Docker version of MySQL 8.0.36 (Image: mysql:8.0.36-debian). The only problem...
  11. A

    Question Anybody facing problems with updating to 18.0.60 or is it safe?

    We have problems with Plesk Obsidian Version 18.0.60 on Ubuntu right after update. 1. Docker containers with MySQL 8.0.36 do not show logs any more. 2. In Plesk pages there is an error: 3. This error can be fixed by clicking on "Recreate" and recreating the container, the logs will be back...
  12. A

    Issue Issue with Docker Container

    CentOS Linux 7.9.2009 Plesk Obsidian Version 18.0.35 Docker version 20.10.6, build 370c289 Docker container with MySQL 5.7.27 stopped one day ago and was not possible to start it again. Trying to start the error was: We saved the databases from mapped folder, deleted the container, removed...
See more
Back
Top