• 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. B

    Issue DNS requests are denied (allow-query-cache did not match) after upgrading from Debian 10 to 12

    Same problem here, while upgrading from Ubuntu 18.04 to 20.04. Thank you @Hangover2. We only found this article here. Has an error report already been created?
  2. B

    Resolved high CPU usage by 'sw-engine' with task 'ext-log-browser-parse-maillog'

    We have the exact same issue with some of our servers. Plesk Obsidian Web Host Edition Version 18.0.61 Update Nr. 6 Problem exists since [2024-07-17 03:25:18.815] 68942:6697399ec6cf1 ERR [panel] Unable to find row with id 1446 in longtasks table.: 0: /opt/psa/admin/plib/Db/Table/Abstract.php:117...
  3. B

    Issue Docker log return 500 Internal Server Error

    We have installed the free version of the "Docker" extension on our server. Exactly one container (Elastic Agent) is currently running there. However, Plesk has been generating a 500 error for some time now. I have tried to find out if there is any further information in the LOG files...
  4. B

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    The support at Strato is in principle never a help. I have had to experience this several times. Which file generates the error for you? I have a Strato server myself and have already successfully solved the problems.
  5. B

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    :/etc/apt/trusted.gpg.d# ls -trla total 28 -rw-r--r-- 1 root root 1733 Mär 29 2021 ubuntu-keyring-2018-archive.gpg -rw-r--r-- 1 root root 2794 Mär 29 2021 ubuntu-keyring-2012-cdimage.gpg -rw-r--r-- 1 root root 2796 Mär 29 2021 ubuntu-keyring-2012-archive.gpg -rw-r--r-- 1 root root 360 Apr 3...
  6. B

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    Thank you. I will also check this.
  7. B

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    I understand that developers need access to such a system. However, this is usually not really possible for privacy reasons. We are happy to provide the relevant information - but we cannot provide blank access to one of the affected systems.
  8. B

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    using this: https://support.plesk.com/hc/en-us/articles/13499261313303
  9. B

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    Yes, this helps -- but only for 1 day -- then the messages come again
  10. B

    Resolved apt conflict with javascript-common

    I could probably solve the problem now. The cause was old packages, which were probably not removed during the upgrade. :~# apt-cache rdepends --installed javascript-common javascript-common Reverse Depends: libjs-jquery psa libjs-jquery-mousewheel libjs-jquery-mousewheel...
  11. B

    Resolved apt conflict with javascript-common

    I have the same problem - after a migration from Ubuntu 18 to 20 apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or...
Back
Top