Backup to DigitalOcean Spaces LON1 region not configurable
-
wrote on Aug 31, 2024, 3:47 PM last edited by joseph Sep 2, 2024, 6:33 AM
I am trying to set up backups to my DigitalOcean Spaces bucket.
However, the bucket is in DO's region LON1 and that is not available in the Region drop down selection list when choosing DO as the backup provider. The configuration fails.
Tried setting up 'S3 API compatible' alternative but couldn't get that to work either.
How best to proceed please?
-
@latinhypercube ok, the trick is to use
https://lon1.digitaloceanspaces.com
as the Endpoint URL and not the one in the DigitalOcean UI (which gives the bucket name in the URL). After that it works. -
I am trying to set up backups to my DigitalOcean Spaces bucket.
However, the bucket is in DO's region LON1 and that is not available in the Region drop down selection list when choosing DO as the backup provider. The configuration fails.
Tried setting up 'S3 API compatible' alternative but couldn't get that to work either.
How best to proceed please?
@latinhypercube said in Backup to DigitalOcean Spaces LON1 region not configurable:
Tried setting up 'S3 API compatible' alternative but couldn't get that to work either.
this should work. what error did you get?
-
-
wrote on Sep 2, 2024, 7:56 AM last edited by latinhypercube Sep 2, 2024, 8:04 AM
It is strange. When I try the 'S3 API compatible' route, I receive this error message:
Error listing objects. Message: null HTTP Code: NoSuchKey
However, I can see that the file path and and a test file have been created in my bucket. The backup configuration isn't saved successfully though.
I've entered valid key id and secret keys I think.
(I have this working with Scaleway but I'm looking to move to DigitalOcean)
-
@latinhypercube interesting... I can reproduce this.
-
@latinhypercube ok, the trick is to use
https://lon1.digitaloceanspaces.com
as the Endpoint URL and not the one in the DigitalOcean UI (which gives the bucket name in the URL). After that it works. -
wrote on Sep 3, 2024, 8:57 AM last edited by
Wonderful. Thank you @Joseph, that change to the endpoint URL did the trick. The configuration saved successfully.
-