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

Issue Apt cache fetch failed

Donnerkeil

New Pleskian
Server operating system version
Ubuntu 22.04.3 LTS
Plesk version and microupdate number
18.0.55 Update #2
After working for some weeks without problems, the following issue occured from one day to another and is now reported every day by email:

Hallo Example - Administrator, es sind Probleme mit dem Tool für Systemupdates auf Ihrem Server ip.example.com aufgetreten. Beheben Sie die Probleme manuell.

Grund: 2023-10-09 06:25:18 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-10-09 06:25:19 ERROR: Apt cache fetch failed:
2023-10-09 06:25:19 ERROR:
2023-10-09 06:25:19 ERROR: Exited with returncode 1.

Doing apt-get update and apt-get-upgrade manually by SSH works without errors. I'm not completely sure, but the issue could have occured with the microupdate #2 for 18.0.55.
 
The error message you've received suggests that there is an issue with the system update tool on your server!
 
Back
Top