# Rebuild issue: \[Cannot set dual-stack in combination with a custom endpoint.\]

**URL:** <https://meta.discourse.org/t/rebuild-issue-cannot-set-dual-stack-in-combination-with-a-custom-endpoint/334902>\
**Category:** Bug\
**Tags:** s3, fixed\
**Created:** [November 7, 2024, 8:13am UTC](https://meta.discourse.org/t/rebuild-issue-cannot-set-dual-stack-in-combination-with-a-custom-endpoint/334902 "2024-11-07T08:13:14Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [November 7, 2024, 8:14pm UTC](https://meta.discourse.org/t/rebuild-issue-cannot-set-dual-stack-in-combination-with-a-custom-endpoint/334902/10 "2024-11-07T20:14:52Z")

</div>

@martin usually what we do here is providing a GlobalSetting to disable the behavior that people running incompatible S3 clones can then opt-in to make it work.

IMO, the current behavior should stay as the default, but provide toggles to increase compatibility.

See prior art in `DISCOURSE_S3_HTTP_CONTINUE_TIMEOUT`, `DISCOURSE_S3_INSTALL_CORS_RULE`, etc.

---

_[View the full topic](https://meta.discourse.org/t/rebuild-issue-cannot-set-dual-stack-in-combination-with-a-custom-endpoint/334902)._