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

Resolved Amazon S3 Backup fails with wasabi s3 storage

spuky

New Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian 18.0.68 Update 1
Error:
Unable to create the remote backup: Transport error: Extension transport: ext://s3-backup/server/: Checksum Type mismatch occurred, expected checksum Type: null, actual checksum Type: crc32

Same error on 3 Servers...

Plesk Obsidian 18.0.68 Update 1 / Amazon S3 Backup Version 1.5.1-2514
 
Me too!
on 2 Servers

Unable to create the remote backup: Transport error: Extension transport: ext://s3-backup/server/: Checksum Type mismatch occurred, expected checksum Type: null, actual checksum Type: crc32

Plesk Obsidian 18.0.67 Update #3 Web Host Edition / CentOS Linux 7.9.2009 (Core)
Amazon S3 Backup Version 1.5.1-2514
 
It appears that this is occurring after the “Amazon S3 Backup” update on March 19, 2025 (timezone is JPT [+09:00] ).

[root@helloworld s3-backup]# pwd
/usr/local/psa/admin/plib/modules/s3-backup
[root@helloworld s3-backup]# ls -al

drwxr-xr-x 9 root root 128 3月 19 03:34 .
drwxr-xr-x 31 root root 4096 3月 21 03:26 ..
drwxr-xr-x 2 root root 33 3月 19 03:33 controllers
drwxr-xr-x 3 root root 64 3月 19 03:33 hooks
drwxr-xr-x 2 root root 195 3月 19 03:33 library
-rw-r--r-- 1 root root 6139 3月 19 03:34 meta.xml
drwxr-xr-x 3 root root 21 3月 19 03:33 resources
drwxr-xr-x 2 root root 30 3月 19 03:33 scripts
drwxr-xr-x 11 root root 182 3月 19 03:33 vendor
drwxr-xr-x 3 root root 21 3月 19 03:33 views
 
  • Like
Reactions: sli
Hello, everyone. Thank you for reporting the issue. Our team is already working on introducing a hostfix for the Amazon S3 Backup extension - EXTPLESK-8857. The ETA for the release is today.
 
Back
Top