• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

Resolved There was an issue with updating system packages and third-party components. pum is called with arguments: ['--list', '--repo-info', '--json']

@PeopleInside and @GerdSchrewe

Gentlemen!

In a sense, you are both right.

The problem here is that there might be workarounds for a solution that does not exist ...... and "setting cronjobs at different times", "waiting for new updates", "ignoring error messages from Plesk package manager" and so on ........ are all reasonable workarounds, in the absence of a viable solution!

Somethings might not be changed by Plesk admins, like errors in the apt sources lists - they are frequently and consistently present : one can solve this, until a new update or some other administrative action overrides the (manual) adjustments.

Something might be change by Plesk admins - for instance, removing Imunify will (more than) halve the error messages of Plesk package manager.


In summary, we are forced to work with the workaround we individually prefer, due to the lack of viable solutions.

This particular thread has added value, given the fact that most of the issues with Plesk package manager can be resolved by Plesk.

So, please do not stop the discussion - just post and report the issues that you encounter with updates!


Kind regards....
 
I see the same for a week now. There is no problem updating with apt-get. Also when I run the repo list I get the json data and no errors. :(
 
Hi greedysoul,
I'm no more using Plesk currently, however when I had this issue the solution was try a different Plesk cron time.

Plesk guide here
 
Back
Top