Custom S3 doesn’t work and hasn’t worked since July 2019

  • Resolved qhbl

    (@qhbl)


    4 years, 10 months ago

    Hi

    We upload backups to Wasabi using custom s3 link, but I have just checked and the last successful backup took place on 11 July 2019.

    The system can list all the buckets when I add the Wasabi url in job settings, but when I run the job, at the end it fails with the following message:
    ERROR: S3 Bucket “big” does not exist!
    100%
    Job completed

    100%
    ERROR: Job has ended with errors in 6 seconds. You must resolve the errors for correct execution.

    I looked at the Wasabi buckets and the last upload was on 11 July 2019, I am not sure if there were any changes made to the software at that time?

    Currently have everything latest installed, here are the details.

    WordPress version 5.3.2
    BackWPup version 3.7.0 Get pro.
    PHP version 7.2.24-0ubuntu0.18.04.2 (64bit)
    MySQL version 10.1.43-MariaDB-0ubuntu0.18.04.1
    cURL version 7.58.0
    cURL SSL version OpenSSL/1.1.1
    WP-Cron url https://URL/wp-cron.php
    Server self connect Not expected HTTP response:Status-Code: 200
    Server: nginx
    Date: Thu, 23 Jan 2020 14:47:02 GMT
    Content-type: text/html; charset=UTF-8
    Vary: Accept-Encoding
    Expires: Wed, 11 Jan 1984 05:00:00 GMT
    Cache-control: no-cache, must-revalidate, max-age=0
    Content-encoding: gzip

    Please help, backups are important.

Viewing 11 replies - 1 through 11 (of 11 total)
Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Custom S3 doesn’t work and hasn’t worked since July 2019’ is closed to new replies.