Commit bfd23a5e authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Move DO spaces troubleshooting to DO spaces section

parent bed71f1d
...@@ -193,10 +193,14 @@ This example can be used for a bucket in Amsterdam (AMS3). ...@@ -193,10 +193,14 @@ This example can be used for a bucket in Amsterdam (AMS3).
gitlab_rails['backup_upload_remote_directory'] = 'my.s3.bucket' gitlab_rails['backup_upload_remote_directory'] = 'my.s3.bucket'
``` ```
1. [Reconfigure GitLab] for the changes to take effect 1. [Reconfigure GitLab] for the changes to take effect
CAUTION: **Warning:**
If you see `400 Bad Request` by using Digital Ocean Spaces, the cause may be the
usage of backup encryption. Remove or comment the line that
contains `gitlab_rails['backup_encryption']` since Digital Ocean Spaces
doesn't support encryption.
#### Other S3 Providers #### Other S3 Providers
Not all S3 providers are fully-compatible with the Fog library. For example, Not all S3 providers are fully-compatible with the Fog library. For example,
...@@ -694,8 +698,3 @@ For more information see similar questions on postgresql issue tracker[here](htt ...@@ -694,8 +698,3 @@ For more information see similar questions on postgresql issue tracker[here](htt
[reconfigure GitLab]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure [reconfigure GitLab]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source [restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
### 400 Bad Request on Digital Ocean Spaces
If you see `400 Bad Request` by using Digital Ocean Spaces the cause may be the usage of `gitlab_rails['backup_encryption']`. You must remove or comment the line you contain `gitlab_rails['backup_encryption'] = '...'`.
Digital Ocean Spaces doesn't implement encryption.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment