docs: clarify htaccess.RewriteBase is a backend path, not public URL#14938
Merged
Conversation
Contributor
📖 Documentation Preview📄 1 changed documentation pageLast updated: Wed, 20 May 2026 05:49:54 GMT |
The previous description implied the value should mirror the public URL, causing users behind a reverse proxy to misconfigure the setting and hit infinite redirect loops. The value is an Apache RewriteBase directive and must reflect where Nextcloud is served on the backend (relative to DocumentRoot), not the public-facing URL prefix. Split into "Direct setup" and "Reverse proxy" sections with a concrete example of each, and added a matching note in the Pretty URLs section of the source installation guide. Fixes #13428 Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
skjnldsv
force-pushed
the
fix/htaccess-rewritebase-reverse-proxy
branch
from
7efe6df to
486ce78
Compare
miaulalala
approved these changes
May 20, 2026
Member
Author
|
/backport to stable34 |
Member
Author
|
/backport to stable33 |
Member
Author
|
/backport to stable32 |
This was referenced May 20, 2026
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 changed and why
The previous description of
htaccess.RewriteBaseimplied the value shouldmirror the public URL (e.g.
/nextcloudforhttps://domain.com/nextcloud/).This is wrong in reverse-proxy setups where the proxy strips the URL prefix
before forwarding to the backend server. A user with
domain.com/nextcloud/forwarded to
localhost:8080/(Nextcloud at DocumentRoot) must set the valueto
/, not/nextcloud— using/nextcloudcauses infinite redirects.The fix:
on the backend, not the public URL prefix
.. note::in the Pretty URLs section ofsource_installation.rstwith the same clarification
cc @hwalinga
🖼️ Screenshots
No visual/layout changes — text-only.
✅ Checklist
codespellor similar and addressed any spelling issues