• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Error System Updates

theplaza

New Pleskian
Server operating system version
Ubuntu 24.04.5 LTS
Plesk version and microupdate number
18.0.82
Hello,

How can I solve this problem: Error: Cannot get package list: 2026-11-04 09:44:23 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2026-11-04 09:44:23 ERROR: Previous Plesk installer call finished unsuccessfully. PUM will not perform any update operations until Plesk installation is fixed. 2026-11-04 09:44:23 ERROR: Exited with returncode 50.

Thank you
 
Hi! here is the report:
plesk repair installation

Reconfiguring the Plesk installation

Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp18.0.82-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Reconfiguring mail subsystem...
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
Restoring SELinux contexts...
Reconfiguring SSL ciphers and protocols...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...
Fixing permissions on Panel packages files
The file '/var/parallels/autoinstaller-installation-failure.flag' is present, which may indicate problems with recent update.
Please check '/var/log/plesk/install/plesk_18.0.82_repair.log' for details

Check:

tail -n 50 /var/log/plesk/install/plesk_18.0.82_repair.log
INFO: Executing upgrade task: 2019-04-25-14-46-58 (forced)
SUCCESS: Upgrade step 2019-04-25-14-46-58_ReportUsage.php was successfully done.
INFO: Executing upgrade task: 2020-03-19-17-13-39 (forced)
SUCCESS: Upgrade step 2020-03-19-17-13-39_UpgradeExtensions.php was successfully done.
done
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Reconfiguring mail subsystem...
Trying to execute plesk repair mail to synchronize mail server settings and Plesk Database...
Repairing the mail server configuration
Reconfiguring all domains and mailboxes ......................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Restoring SELinux contexts...
Trying to register service sw-cp-server... Trying to enable automatic respawn for service sw-cp-server.service... done
done
Trying to register service sw-engine... Trying to enable automatic respawn for service sw-engine.service... done
done
Trying to register service dovecot... Trying to enable automatic respawn for service dovecot.service... done
done
Trying to register service pc-remote... Trying to enable automatic respawn for service pc-remote.service... done
done
Trying to register service nginx... Trying to enable automatic respawn for service nginx.service... done
done
Trying to register service psa... Trying to enable automatic respawn for service psa.service... done
done
Reconfiguring SSL ciphers and protocols...
Trying to configure SSL ciphers and protocols for: ... done
Regenerating web servers' configuration files...
Cleaning active Panel sessions...
Fixing permissions on Panel packages files
The file '/var/parallels/autoinstaller-installation-failure.flag' is present, which may indicate problems with recent update.
Please check '/var/log/plesk/install/plesk_18.0.82_repair.log' for details

Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_18.0.82_repair.log' and '/var/log/plesk/install/plesk_18.0.82_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Plesk support.
Trying to restart service apache2... active
done
SUCCESS: Upgrade step Plesk\Upgrade\Action_UpgradeExtensions was successfully done.
done

**** Product repair completed successfully.
 
same here on two brand new VPSs with Ubuntu 24.04.5 and Plesk 18.0.82#1, after this morning's update. Both updated "correctly" and panel+sites work fine, but something broke the updating system / pum and now a "Check Updates" click fails with the same error
 
Following Sebahat's advice, it seems to be unblocked now. But I wanted confirmation from the log.
The thing is, it seems believable that the issue has something to do with the combo Ubuntu 24.04.5 + this specific update.
I had 6 other VPS with Ubuntu 22 that updated flawlessly.The only two with U24 failed. Can't be a coincidence. Thing is, many people could simply have not seen anything wrong - I spotted the issue just because I didn't get the notification email from the 2 servers. How did you spot it? Just trying to check new updates this morninga? Because otherwise, the servers work (and the sites too)
 
Just to clarify: repairing plesk didn't do anything. It proved that nothing important in the autoupdate process actually went wrong; it simply was stopped before the very last step.
The autoinstaller-installation-failure file wasn't removed by the repair procedure; I moved the file (btw it's just an empty placeholder file with size 0) in my root dir just to check and (as expected) now the "Check for updates" button works again.
I DISABLED ALL PLESK AUTOUPDATES for now, since it's unclear if the issue was specific to 18.0.82#2 or general. I expect that Plesk staff will investigate the matter in a deeper way.
 
@theplaza , just to confirm were you able to complete the update after the repair?

@Andrea Bampi , the issue is commonly caused by interrupted update process, corrupted Plesk installation, and package inconsistencies. I just performed a test update on an Ubuntu 24 server from Plesk Obsidian 18.0.82 Update #1 to Plesk Obsidian 18.0.82 Update #2 and the process went through without issues. If repairing the installation doesn't work in your case, please check what additional details have been logged into /var/log/plesk/install/autoinstaller3.log. Thanks in advance.
 
Thanks for testing this.

Your successful Ubuntu 24.04 test suggests this is not a deterministic Ubuntu 24 issue, but on my side I had the same failure on two separate brand-new Ubuntu 24.04.5 VPSs, both upgrading automatically from 18.0.82 Update #1 to Update #2.

For comparison, I have six Ubuntu 22.04 servers and all six completed the same automatic update successfully (this morning, at 0630).

On both affected Ubuntu 24 servers, the actual Plesk upgrade appears to complete correctly. The failure happens immediately afterwards, during report-update.

Example from one server:

Cumulative upgrade of Plesk (final stage) has been completed.

[2026-11-04 06:31:44.794729] Plesk Installer process has received termination signal and will stop working (signal number 15).
[2026-11-04 06:31:44.800097] Launching component and product checkers...
[2026-11-04 06:31:44.800132] FileFetcher: get file (<empty>)/report-update
[2026-11-04 06:31:44.800178] Downloading file report-update: 0%
[2026-11-04 06:31:44.803420] Plesk Installer process has received termination signal and will stop working (signal number 15).
[2026-11-04 06:31:44.804821] Error: Interrupted by user
At almost exactly the same time, the system journal shows:

Nov 04 06:31:44.793773 systemd[1]: Stopping run-plesk-task-686.service - Plesk task: Daily Maintenance: InstallUpdates ...
After this, /var/parallels/autoinstaller-installation-failure.flag remains present and PUM fails with:

Previous Plesk installer call finished unsuccessfully.
PUM will not perform any update operations until Plesk installation is fixed.
Exited with returncode 50.
I ran plesk repair installation on one server. It completed successfully with no repair errors, but it did not remove the failure flag and PUM remained blocked.

After moving that zero-byte flag out of /var/parallels, "Check for Updates" immediately started working again.

Also, before doing this:

dpkg --audit
pgrep -a apt
pgrep -a dpkg
all returned clean/no output.

So the interesting part seems to be that Daily Maintenance: InstallUpdates is being stopped while the autoinstaller is still finishing report-update.

For now I have disabled automatic Plesk updates only on my three Ubuntu 24.04 servers, until it is clearer whether this was specific to Update #2 or could happen again on a future update.
 
Thank you for the additional details. I ran a manual update, and it looks like the issue might be related to the automatic update. I will attempt to replicate the SIGTERM with an additional test with an automatic update and follow up with more details tomorrow. Thanks for your patience in the meantime.
 
Back
Top