Any success with Minio Backups

  • Hello! I’ve seen many posts here about minio backups failing with the “ERROR: S3 Bucket “[bucket-name-that-was-auto-selected-by-BackWpUp-itself]” does not exist!”, but I don’t seem to find any helpful solutions to this issue.

    Has anyone resolved it?

    I looked at a Trace on my minio server, and I see BackWPUp select the BucketList, but I don’t see it make any connection at all at the point where it fails to do the upload. It’s like it’s not even trying to connect.

    Does it only look at custom server details for the settings screen and not actually for the backup? Like…is it looking at whatever is selected in the “Select a S3 service” list when it’s backing up instead of the “Or a S3 Server URL” section?

    Is there a way to tell it, “no, please, just look at my custom S3 Server URL during backups”?

    Thanks!

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Thread Starter davethenerd

    (@davethenerd)

    Perhaps some insight here. I tried to have it create a new bucket, and I get this error at the top of the screen:

    Error executing "CreateBucket" on "https://mgg-wp.[myserverurl.com]:9001/"; AWS HTTP error: cURL error 6: Could not resolve host: mgg-wp.[myserverurl.com]; Unknown error (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

    Seems it’s taking my endpoint of https://[myserverurl.com]:9001/ and trying to do a DNS lookup for [new-bucket-name].[myserverurl.com] which obviously doesn’t exist. This leads me to think I need to use “Pathstyle-only bucket” option, but that also doesn’t seem to stay checked.

    Maybe this is the issue?

Viewing 1 replies (of 1 total)
  • The topic ‘Any success with Minio Backups’ is closed to new replies.