• Resolved pvdh2

    (@pvdh2)


    I’ve been using updraft plus for about a year without issues, using s3generic to backup to minio. 1.16.20 had a change “TWEAK: Force the predecessor Amazon S3 SDK to use virtual-hosted style bucket identification instead of path style”, which broke my configuration.
    I stuck with 1.16.17 till now, but it is quite annoying to have an outdated plugin.

    So: how do I need to modify my configuration?
    Configuration with 1.16.17:
    s3 location: s3generic://bucketname
    s3 end-point: DNS-name-of-server
    “Test S3 Settings” reports: “S3 settings test result: Success: We accessed the bucket, and were able to create files within it. The communication with DNS-name-of-server was encrypted.”

    Configuration with 1.16.21 without any modifications:
    S3 settings test result: Failure: We successfully accessed the bucket, but the attempt to create a file in it failed. Please check your access credentials. (UpdraftPlus_S3::putObject(): [6] Could not resolve host: bucketname.DNS-name-of-server)

    No surprise here, bucketname.DNS-name-of-server is no valied DNS-record.

    So, is there a new requirement that bucketname.DNS-name-of-server needs to resolve? Given the changelog I’d expect the plugin to split it into bucketname and DNS-name-of-server?
    Do I need to change the syntax of my configuration? I tried several modifications like adding slashes, but didn’t improve it.

    Best regards
    Patrick

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor bcrodua

    (@bcrodua)

    Hi,

    Please can you try to wipe out your UpdraftPlus setting? You can use the “Wipe out” option in the “Advance Tools” tab.

    Then, re-setup your remote storage again and test a new backup process.
    Do you still get the same issue?

    Regards,
    Bryle

    Thread Starter pvdh2

    (@pvdh2)

    Interesting idea. Didn’t change a thing, though.

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    Hi,

    It’s fixed in our development version. As such, just stick with 1.16.17 until the next release, which should be later this month.

    David

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    (This was resolved in the 1.6.22 release).

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘how to configure s3generic after 1.16.20?’ is closed to new replies.