• 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 The repository no longer has a Release file

Patashoow

Basic Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
Plesk Obsidian 18.0.47
Hello,

I'm using Plesk Obsidian 18.0.47 with Ubuntu 20.04 and I'm having the following error:
Reason: INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
ERROR: E:The repository 'http://autoinstall.plesk.com/pool/PSA_18.0.47_10005 focal Release' no longer has a Release file.
ERROR: Exited with returncode 1.

Should I upgrade both Plesk and Ubuntu to fix the issue? Also if I do so, which consequences there will be on my server (it's actually hosting different applications and websites).

Is it safe to temporarily ignore it for now?

Thanks for any help you could give.
 
I previously missed that you are still using Plesk version 18.0.47, which is no longer supported and for which the corresponding release file is no longer available (hence the error). Best suggestion I can think of is the update Plesk to the newest version.
 
I think that I have somehow to do it but will this impact in any way my actual websites and applications? Is there anything to take into consideration before upgrading my Plesk version?
 
Back
Top