# Backups in zwei verschiedene S3-Regionen funktionieren nicht mehr

**URL:** https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552
**Category:** Support
**Created:** [7. Februar 2019 um 00:46 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552 "2019-02-07T00:46:40Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![barreeeiroo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barreeeiroo/32/165264_2.png) [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [7. Februar 2019 um 00:46 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/1 "2019-02-07T00:46:40Z")

</div>

Today we have updated Discourse to latest commit, and S3 backup system stopped working

When accessing to `/admin/backups`, an error failed message is raised, and the JSON outputs this:  
`The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint`

Just before updating, it was working correctly  
Now we can’t either make new backups or view current ones

* * *

We also use media uploads to S3, which is working properly at this moment  
The media bucket is “kodular-community”, and it’s hosted in Dublin

However, the backups bucket is called “kodular-community-backups” and it’s hosted in Oregon

Maybe this issue could be releated in some way to the fact that it’s trying to fetch the “kodular-community-backups” from Dublin endpoint, as it’s the region it’s specified in Admin (?)

But I don’t know why it was working before and suddenly after updating it stopped working

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [7. Februar 2019 um 01:37 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/2 "2019-02-07T01:37:17Z")

</div>

I don’t think using different regions for backups and uploads is a supported configuration. If it ever worked it was a bug.

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [7. Februar 2019 um 08:01 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/3 "2019-02-07T08:01:10Z")

</div>

Yes, it was a bug that I fixed two days ago. Both buckets must be in the same region.

---

<div class="post-metadata">

### Author: ![barreeeiroo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barreeeiroo/32/165264_2.png) [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [7. Februar 2019 um 13:02 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/4 "2019-02-07T13:02:28Z")

</div>

But how was that a bug? What was the effect of it?  
Everything was working properly before 😕

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [7. Februar 2019 um 13:19 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/5 "2019-02-07T13:19:10Z")

</div>

The bug was that the `s3_region` setting was completely ignored. That prevented Discourse from creating a new bucket and I think other things like uploading/downloading backups from the browser should have failed as well when the bucket’s region differed from the `s3_region` setting.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [7. Februar 2019 um 13:21 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/6 "2019-02-07T13:21:41Z")

</div>

It doesn’t make any sense for them to be geographically separate.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [21. Februar 2022 um 19:32 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/7 "2022-02-21T19:32:01Z")

</div>



---

<div class="post-metadata">

### Author: ![schleifer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schleifer/32/86416_2.png) [@schleifer](https://meta.discourse.org/u/schleifer)
#### Post date: [22. Februar 2022 um 01:17 UTC](https://meta.discourse.org/t/backups-to-two-different-s3-regions-no-longer-work/108552/8 "2022-02-22T01:17:11Z")

</div>

Eine Option für den Backup-Bucket in einer anderen Region wäre tatsächlich eine gute Idee. Wie schwer wäre es, das hinzuzufügen, @gerhard? Standardmäßig dieselbe wie Assets, aber überschreiben, wenn gesetzt.

Wenn Ihre Website in `us-east-1`\[1\] gehostet wird und diese Region einen Ausfall hat, können Sie immer noch ein Backup aus einer anderen Region ziehen und die Website woanders hochfahren.

* * *

1. Hosten Sie Ihre Website nicht dort. Es ist die schlechteste Region überhaupt.
