# Migrate\_to\_s3 fails

**URL:** <https://meta.discourse.org/t/migrate-to-s3-fails/209499>\
**Category:** Self-hosting\
**Tags:** s3\
**Created:** [November 18, 2021, 6:54am UTC](https://meta.discourse.org/t/migrate-to-s3-fails/209499 "2021-11-18T06:54:02Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Simon\_Manning](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon_manning/32/198596_2.png) [@Simon\_Manning](https://meta.discourse.org/u/Simon_Manning)\
**Post date:** [November 18, 2021, 9:24pm UTC](https://meta.discourse.org/t/migrate-to-s3-fails/209499/8 "2021-11-18T21:24:51Z")

</div>

If there’s not an obvious solution to get it to upload successfully, either of options 1 or 3 seem like good ways to go. 2 I would probably leave to Discourse, specifically the job to clean up orphaned uploads, the interval for which is controlled by the `clean orphan uploads grace period hours` setting.

It might be a good idea to grab the file before it’s deleted though. If it doesn’t contain any sensitive data, it could be useful for testing why it can’t be uploaded during the migration.

---

_[View the full topic](https://meta.discourse.org/t/migrate-to-s3-fails/209499)._