# Direct S3 upload with local store raises NoMethodError instead of being rejected

**URL:** https://meta.discourse.org/t/direct-s3-upload-with-local-store-raises-nomethoderror-instead-of-being-rejected/412061
**Category:** Bug
**Tags:** s3
**Created:** [September 10, 2026, 4:06am UTC](https://meta.discourse.org/t/direct-s3-upload-with-local-store-raises-nomethoderror-instead-of-being-rejected/412061 "2026-09-10T04:06:34Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [September 10, 2026, 7:08am UTC](https://meta.discourse.org/t/direct-s3-upload-with-local-store-raises-nomethoderror-instead-of-being-rejected/412061/2 "2026-09-10T07:08:53Z")

</div>

Thanks, should be fixed per:

> <https://github.com/discourse/discourse/pull/43505>
>
> Prevent secure upload callbacks from replacing the store check for
> external uplo…ad actions. Presigned upload requests must return 404
> when S3 storage is disabled, even if direct S3 uploads are enabled.
> 
> Add regression coverage for this configuration.

---

_[View the full topic](https://meta.discourse.org/t/direct-s3-upload-with-local-store-raises-nomethoderror-instead-of-being-rejected/412061)._
