# Trouble with Google Bucket for backup
**URL:** https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959
**Category:** Self-hosting
**Tags:** backups
**Created:** [January 28, 2020, 4:37pm UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959 "2020-01-28T16:37:40Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 28, 2020, 4:37pm UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959/1 "2020-01-28T16:37:40Z")
On a site where backups and uploads to Google buckets was working, the backup page now says:
```
Failed to access backup storage: A header or query you provided requested a function that is not implemented.
```
I thought that it might be a bucket permissions issue (but that didn’t really make sense because the same configuration was working a couple weeks ago), but re-reading that message, it sounds like somehow Discourse is trying to do something that’s, uh, _not implemented_. (Which also seems far-fetched).
S3 uploads to a Google bucket (albeit a different one) are working just fine. There is a production site on 2.4.0.beta9 and a staging site running 2.4.0.beta10 (and I just did another upgrade on the staging site).
It’s a standard 2-container install with only standard plugins and the S3 settings configured with `env:` in the `.yml` file. EDIT: I deleted those ENV settings from `yml` and rebuilt (destroy, start didn’t remove them) and the issue remains.
I don’t see any obvious (to me) commits that could be related.
EDIT: There is yet another [standard install](https://meta.discourse.org/t/142537?silent=true) instance running `2.4.0.beta8` with the same settings and it’s working, so it appears that something happened between beta8 and beta9. This does seem like a 🐛. @gerhard could this somehow be related to your backup changes?
P.S. I checked a site using DigitalOcean Spaces and it’s working fine for backups.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [January 28, 2020, 6:24pm UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959/2 "2020-01-28T18:24:52Z")
Are you getting the error as soon as you visit `/admin/backups`? I didn’t change anything in that area recently, but we updated the `aws-s3` gem between `beta8` and `beta10` from version 1.36.1 to 1.60.1. It’s possible that this doesn’t work with Google buckets anymore. Maybe you find the cause in the [CHANGELOG](https://github.com/aws/aws-sdk-ruby/blob/master/gems/aws-sdk-s3/CHANGELOG.md). You could test with different versions of the gem to narrow it down.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 28, 2020, 6:32pm UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959/3 "2020-01-28T18:32:18Z")
> [@gerhard](#):
>
> Are you getting the error as soon as you visit `/admin/backups` ?
Yes.
> [@gerhard](#):
>
> I didn’t change anything in that area recently
Darn.
> [@gerhard](#):
>
> updated the `aws-s3` gem between `beta8` and `beta10` from version 1.36.1 to 1.60.1.
Yuck. I’ll ping an engineer at Google who probably won’t know and see what else I can find.
Thanks very much.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 28, 2020, 7:18pm UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959/4 "2020-01-28T19:18:13Z")
So, by entering the container and editing `Gemfile` and changing
```
gem 'aws-sdk-s3', require: false
```
to versions of
```
gem 'aws-sdk-s3', '1.51.0', require: false
```
and then doing
```plaintext
bundle install --no-deployment
sv restart unicorn
```
to see if it worked or not, a binary search through the versions shows that `1.51.0` is the last version that works, so something in `1.52.0` “Feature - Adding support in SelectObjectContent for scanning a portion of an object specified by a scan range.” is where the problem began.
I’m not sure what to do next. I guess I’ll open an issue over at [GitHub - aws/aws-sdk-ruby: The official AWS SDK for Ruby · GitHub](https://github.com/aws/aws-sdk-ruby), but I’m not sure that they care, right? So maybe open a ticket with the Google?
And Discourse still works for uploads on Google Buckets, just not backups.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [December 14, 2023, 10:54am UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959/5 "2023-12-14T10:54:55Z")
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [December 14, 2023, 6:39pm UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959/6 "2023-12-14T18:39:16Z")
Presumably this has been solved, as Google appears to be supported at
> [@Configure an S3 compatible object storage provider for uploads](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916#google-cloud-platform-storage-5):
>
> information_source This topic covers how to configure some common S3 compatible Object Storage providers (S3 clones). See [Set up file and image uploads to S3](https://meta.discourse.org/t/setting-up-file-and-image-uploads-to-s3/7229) for more details about Amazon AWS S3 configuration, which is officially supported and used internally by Discourse for our hosting services. Provider Service Name Works with Discourse? [Amazon AWS](#aws-s3-2) S3 Yes [Digital Ocean](#digital-ocean-spaces-3) Spaces Yes [Linode](#linode-object-storage-4) Object Storage Yes [Google Cloud](#google-cloud-platform-storage-5) Storage Yes [Scaleway](#scaleway-object-storage-6) Object Storage Yes [Vultr](#vultr-object-storage-7) Obj…
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 13, 2024, 6:40pm UTC](https://meta.discourse.org/t/trouble-with-google-bucket-for-backup/139959/7 "2024-01-13T18:40:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.