• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved error message since the latest Plesk update

dicker

Basic Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.51 Update #1
Hello, I've been getting this error message since the latest Plesk update.
Error: Could not get package list: 2023-04-24 10:31:35 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2023-04 -24 10:31:45 ERROR: 2023-04-24 10:31:45 ERROR: Exited with return code 1.
Can someone help?
 
I'd also want to encourage you to open a ticket with Plesk support on the case, because we're looking for customers who experience that issues where we can check it on their machines to find the root cause. It's a known issue, but only a few Linux installations experience it, so engineers would like to see it on a machine where this actually happens to provide a general fix.
Please provide ID PPS-14261 to support if you open a ticket and a link to this thread.
 
Before I do anything on the server, I wanted to make a fresh backup again.
However, I had to cancel that because 32 GB of RAM was used up. No more websites could be displayed.
That wasn't before either.
 
I also have this error….
I ran apt upgrade via ssh and got the following errors:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://autoinstall.plesk.com/RUBY_0.0.2 focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E W: Failed to fetch http://autoinstall.plesk.com/RUBY_0.0.2/dists/focal/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E W: Some index files failed to download. They have been ignored, or old ones used instead.
 
Back
Top