10.7 backup to Digital Ocean spaces error

I have a new install of 10.7 CE and can’t seem to configure backup to Digital Ocean Spaces. My config for a space in Singapore (SGP1) is below:

gitlab_rails['backup_upload_connection'] = {
  'provider' => 'AWS',
  'region' => 'sgp1',
  'aws_access_key_id' => 'my-access-key-id-string',
  'aws_secret_access_key' => 'my-secret-access-key-string',
  'endpoint' => 'sgp1.digitaloceanspaces.com'
gitlab_rails['backup_upload_remote_directory'] = 'my.bucketname'

Running gitlab-rake gitlab:backup:create generates the following error:

Uploading backup archive to remote storage gitlab-bkup ... rake aborted!
URI::InvalidURIError: bad URI(is not URI?): ://gitlab-bkup.s3.amazonaws.com:

Looking at the output the URI is being appended with “s3.amazonaws.com” rather than “sgp1.digitaloceanspaces.com” but I can’t figure out where this is coming from.

Has anyone else come across this?


Ben, I have been having the same issue and am thinking this is a bug, it also seems like the documentation could be a little better to explain why some fields are the way they are and where the defaults are.

Doing a quick search in some of the directories for the amazonaws.com I found the following file and the line below.


#     endpoint: 'https://s3.amazonaws.com' # default: nil - Useful for S3 compliant services such as DigitalOcean Spaces

it looks like if this line is in the active gitlab.yml (I assume it is a config for the some part of the system) it should set the default to amazonaws.com when left blank. What we are seeing is when we enter in a different address it is simply appended to the default.

Gitlab is huge and not being any good at Ruby it is pretty much beyond most of my grasp but I will keep poking about and maybe if we change the default value to point to digital ocean that may help.

1 Like

I submitted at a bug.