# Impossibile abilitare gli upload in Digital Ocean Spaces

**URL:** <https://meta.discourse.org/t/cant-enable-uploads-in-digital-ocean-spaces/119622>\
**Category:** Product Support\
**Created:** [6 Giugno 2019, 1:32am UTC](https://meta.discourse.org/t/cant-enable-uploads-in-digital-ocean-spaces/119622 "2019-06-06T01:32:23Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![lucasbasquerotto](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lucasbasquerotto/32/133376_2.png) [@lucasbasquerotto](https://meta.discourse.org/u/lucasbasquerotto)\
**Post date:** [6 Giugno 2019, 12:11pm UTC](https://meta.discourse.org/t/cant-enable-uploads-in-digital-ocean-spaces/119622/6 "2019-06-06T12:11:57Z")

</div>

> [@tshenry](#):
>
> The name you enter for the `s3_upload_bucket` setting must be globally unique

I thought that was based on the buckets of the account, but that makes sense, because the bucket identifier is accessed without the account user/organization name.

That said, the error `Bucket already exists` was misleading (at least for me). I thought it (the code) was saying that the bucket existed under my account, because it tries to create it with my credentials (if the error was `Bucket name already exists under another account` or something along those lines I would have solved it immediatelly; in any case, I don’t think the error message was generated by discourse itself).

Anyway, thanks for the explanation!

---

_[View the full topic](https://meta.discourse.org/t/cant-enable-uploads-in-digital-ocean-spaces/119622)._
