• 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 Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Backup does not work since upgrade to Version 18.0.50

Jürgen_T

Regular Pleskian
Server operating system version
Ubuntu 20.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.50_build1800230207.15
Yesterday I upgraded from Version 18.0.49 to Version 18.0.50. One result: the scheduled backup for the night failed. I received the message by E-Mail:
...
<?xml version="1.0"?>
<execution-result log-location="/opt/psa/PMM/sessions/2023-02-12-002909.484/migration.result" local-dump-created="true" export-dump-created="false" local-dump-name="backup_info_2302120029.xml" export-dump-name="backup_2302120029.tar" status="warnings">
<message severity="warning">
<description>Unable to create the remote backup: Transport error: unable to check directory existence: Curl error: (28) Timeout was reached: Last FTP request: NLST Last FTP response: 150 Opening ASCII mode data connection for 'file list'</description>
</message>
</execution-result>

  1. Then I tried to open Tools&Einstellungen/Backup-Manager. Result: it was not possible to open it, task hangs
  2. Then I used Plesk repair all via web interface. Gave an 500-error when it started to repair installation.
  3. Then I used plesk repair installation via ssh => gave the following error message:
...
Bootstrapper repair finished.
SUCCESS: Upgrade step Plesk\Upgrade\Action_UpgradeExtensions was successfully done.
done

**** Product repair failed.

***** problem report *****
Warning: phpMyAdmin was configured without configuration storage in database
STOP Bootstrapper 18.0.50 repair AT Sun Feb 12 10:17:17 CET 2023

So the question is, does this belong to the buggy backup?

How can I get access to the backup-configuration and finaly how to fix this backup problem in general?

(Websites and E-Mail work as usual after the upgrade)
 
Back
Top