• 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.

Resolved Upload backup files

dicker

Basic Pleskian
Server operating system version
Ubuntu 22.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.58 Update #2
Is there no other possibility? I can't import customers' backups via SSH every time.
File size 2GB for backup is definitely not enough.
What options are there for the customer to independently upload backup data larger than 2GB?
 
Why do the customers download such large backups in the first place? Wouldn't it be much better for them to store them to an external FTP or S3 storage space? For FTP/FTPS all tools are included in the basic version of the product. But with the Cloud Backup Pro extension they could also export their backups to Google Drive, MS OneDrive etc. It's just not best practice to download such large backup files to a local computer.
 
Of course I make backups.
The customer backup is probably older than what I have.
I don't know why the customer wants to import such an old backup.
 
Is there a solution to this problem?
 
Back
Top