docs(admin): document share link URL behaviour with multiple trusted domains#14989
Open
skjnldsv wants to merge 1 commit into
Open
docs(admin): document share link URL behaviour with multiple trusted domains#14989skjnldsv wants to merge 1 commit into
skjnldsv wants to merge 1 commit into
Conversation
…domains When multiple trusted_domains are configured, generated URLs (share links, download links, notifications) use the hostname from the incoming request. This is a common source of confusion for admins running split-horizon DNS or dual internal/external access, as share links created internally contain the internal hostname and break for external users. Add a new subsection to reverse_proxy_configuration.rst explaining the behaviour and showing how to force a canonical hostname via overwritehost and overwrite.cli.url. Fixes #11623 Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
artonge
reviewed
May 21, 2026
|
|
||
| When multiple entries are listed in ``trusted_domains``, Nextcloud accepts | ||
| requests on all of them but generates URLs based on the hostname of each | ||
| incoming request. This means share links, download URLs, and notification |
Contributor
There was a problem hiding this comment.
For share link, isn't the URL build when the user copies it from the web UI and not at creation time?
Member
Author
There was a problem hiding this comment.
No, only the token. On copy it's being assembled iirc
Contributor
There was a problem hiding this comment.
Then the sentence and paragraph below are false
Member
Author
There was a problem hiding this comment.
Not really, people usually copy them when they create a link and send it to people. Same for mail. Maybe I should rephrase 🤔
I guess I could say "copied" instead of "created" ? Do you think that would be clear enough ?
Contributor
📖 Documentation Preview📄 1 changed documentation pageLast updated: Thu, 21 May 2026 11:04:55 GMT |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
What and why
When multiple
trusted_domainsare configured, Nextcloud generates URLs(share links, download links, notifications) using the hostname from the
incoming request. In split-horizon DNS or dual-access setups (internal
cloud.local+ externalcloud.example.com), share links createdinternally contain the internal hostname and break for external users.
The fix (
overwritehost+overwrite.cli.url) was already mentionedelsewhere in the docs but the connection to this specific problem was never
made explicit. This adds a dedicated subsection to
reverse_proxy_configuration.rstexplaining the behaviour and showingthe correct config.
🖼️ Screenshots
No visual/layout changes — prose and code block addition only.
✅ Checklist
codespellor similar and addressed any spelling issues