• 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 BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Using Scaleway S3 for Plesk backups

carini

carini

Basic Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.63_build1800240902.09
Anyone is using Scaleway S3 (Europe's empowering cloud provider | Scaleway) as a backup storage.

In the last two weeks we are experiencing a LOT of aborted backup. The worst part is that the backup process even fail to terminate in error and we need to kill the process manually.

Note:

In panel.ini a maximum timeout and maximum number of tries has already been set:

INI: 
[ext-s3-backup]


; https://talk.plesk.com/threads/amazon-s3-backup-connecting-to-scaleway-object-storage.357132/
RegionForCustomEndpoint = fr-par


ConnectionTimeout = 120
MaxResumeAttempts = 20
MaxResumeFailures = 60

But if I look at backup process i find the backup process stuck

Mon Oct 14 07:01:43 CEST 2024

Code: 
    PID    PPID USER       TT       STAT %CPU NLWP     TIME %MEM        RSS        DRS       SIZE                  STARTED CMD
 897195  788641 root       ?        SN    0.0    1 00:00:02  0.6      50056     203246      43916 Mon Oct 14 05:42:10 2024  |       \_ /usr/bin/sw-engine -c /opt/psa/admin/conf/php.ini /opt/psa/admin/sbin/backup_restore_helper --extension-transport ext://s3-backup/server/ -operation open-write -path backup_2410140424.tar28

The connection with Scaleway is in ESTAB state, but apparently there is no traffic

Code: 
Netid   State        Recv-Q   Send-Q                       Local Address:Port                                     Peer Address:Port                             Process
tcp     ESTAB        0        0                                 10.5.0.5:58960                                    51.159.62.19:443                               users:(("sw-engine",pid=897195,fd=11))

Anyone with the same problem?

Scaleway worked almost fine since now and we are struggling to find a good alternative solution at a cheap price
 
Backblaze Cloud Storage B2 is a solid alternative. It offers affordable pricing and has data centers in the EU as well. You can find more information on connecting Plesk to Backblaze here:

Resolved - Connect to Backblaze B2 (S3-compatible)

Hi all, Backblaze have released an S3 compatible API. I have been using Scaleway but wish to migrate to Backblaze B2. Has anyone figured out how to get this working? I get the error: `Error: Unable to upload a file to the storage: Backblaze does not support the 'x-amz-request-payer' header...
talk.plesk.com talk.plesk.com
 
You must log in or register to reply here.

Similar threads

E
Issue Extension Amazon S3 Backup / error remote storage
Replies
2
Views
1K
Erwan
E
Back
Top