• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue Broken update after switching from Obsidian 18.0.72 to 18.0.73

Petrs

New Pleskian
Server operating system version
Debian 13
Plesk version and microupdate number
Plesk Obsidian v18.0.73_build1800250927.14 os_Debian 13.0
Yesterday I upgraded Plesk 18.0.72 to Plesk 18.0.73, everything is functional, but if you try to run an update or fetch updates in the section, a notification appears:

Error: Unable to get list of packages:

2025-10-02 14:13:13 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2025-10-02 14:13:14 ERROR: '13'
2025-10-02 14:13:14 ERROR: Exited with returncode 1



When I attempt to run the automatic Plesk repair, after about 2 minutes it freezes on repairing the Plesk database, consumes all of my 30 GB RAM, and the server crashes. After a reboot, the server comes back online, but the Plesk repair does not complete. I tested reinstalling Plesk, but it didn’t help.

Has anyone experienced this issue?

Please share any fix. Thank you.
 
If you are using Debian 13, you might run into random issues since Debian 13 isn't technically fully supported (yet). Support for a lot of packages is being added after each update so it's getting there.

With that said, can you check what shows up in your /var/log/plesk/install/autoinstaller3.log log? It's possible that there's a duplicate entry of a repo or a discontinued repo that's triggering it and that autoinstaller3.log file should give us some insights.
 
Back
Top