• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • 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.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Search results

  1. J

    Resolved PUM error persists....

    You're a hero !! , This worked ! now only getting the warning, but I can upgrade . Thank you so much ! root@webserver:/usr/share/keyrings# apt update Hit:1 Index of /RUBY_0.0.2 noble InRelease Hit:2 Index of /pool/PSA_18.0.67_16313 noble InRelease...
  2. J

    Resolved PUM error persists....

    where can I get this missing key ?
  3. J

    Resolved PUM error persists....

    aha.. no there isn't root@webserver:/usr/share/keyrings# ls -l total 72 -rw-r--r-- 1 root root 13978 Feb 10 16:30 dart.gpg -rw-r--r-- 1 root root 1160 Jan 22 15:40 kernelcare.gpg -rw-r--r-- 1 root root 3607 Nov 26 2023 ubuntu-archive-keyring.gpg -rw-r--r-- 1 root root 1227 Nov 26 2023...
  4. J

    Resolved PUM error persists....

    This is the content of /etc/apt/sources.list.d/kcare.list deb [arch=amd64,arm64 signed-by=/usr/share/keyrings/kcare.gpg] Index of /kernelcare-ubuntu/24.04/ noble main
  5. J

    Resolved PUM error persists....

    root@webserver:/etc/apt/sources.list.d# ls -l total 32 -rw-r--r-- 1 root root 134 Feb 10 16:31 dart_stable.list -rw-r--r-- 1 root root 190 Feb 10 16:22 google-chrome.list -rw-r--r-- 1 root root 126 Jan 7 17:13 kcare.list -rw-r--r-- 1 root root 110 Jan 3 16:29 plesk-ext-grafana.list...
  6. J

    Resolved PUM error persists....

    already tried this :-( root@webserver:~# gpg --keyserver keyserver.ubuntu.com --recv-keys 6DC3D600CDEF74BB gpg: key 6DC3D600CDEF74BB: "KernelCare <[email protected]>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 root@webserver:~# apt-get clean error still...
  7. J

    Resolved PUM error persists....

    Thank you for your reply. I read the this should be fixed in 18.0.67 however, I already run plesk 18.0.67 update #2 And there is definitely an error which stops the whole process. Err:13 Index of /kernelcare-ubuntu/24.04/ noble InRelease The following signatures couldn't be verified because...
  8. J

    Resolved PUM error persists....

    Hello everyone, I'm pretty new at Plesk. I got this PUM error while updating my Ubuntu 24.04.1 LTS server with Plesk Obsidian 18.0.67 Update #2 Got the error for a month now, I searched the internet and found more than one post about it, but no solution. I did everything that was offered but...
Back
Top