nextcloud / nextcloud/documentation

Multiple domains reverse SSL proxy

Open
#9,466 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop feature: install and update manual: admin technical debt
Dominant language
JavaScript
Stars
628
Forks
2.5k
Avg merge
2d 11h
Merged PRs (30d)
135

Description

https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html#multiple-domains-reverse-ssl-proxy

This is absolutely not understandable, because:
Its called "Multiple domains reverse SSL proxy"
-> So you think you could host nextcloud through a reverse proxy with multiple domains.
-> This is not correct, because:
--> If you set: 'overwritehost' => 'mydomain.com',
---> Nextcloud will redirect 302 every domain to mydomain.com
So in the end this is only a redirection rule, but you cannot host nextcloud with multiple domains.

https://help.nextcloud.com/t/nginx-reverse-proxy-multiple-domains/135730
There are people that asking the same, i think they have the exact same issue, because that snippet above is not understandable.



Multiple domains reverse SSL proxy
If you want to access your Nextcloud installation http://domain.tld/nextcloud via a multiple domains reverse SSL proxy https://ssl-proxy.tld/domain.tld/nextcloud with the IP address 10.0.0.1 you can set the following parameters inside the config/config.php.

<?php
$CONFIG = array (
  'trusted_proxies'   => ['10.0.0.1'],
  'overwritehost'     => 'ssl-proxy.tld',
  'overwriteprotocol' => 'https',
  'overwritewebroot'  => '/domain.tld/nextcloud',
  'overwritecondaddr' => '^10\.0\.0\.1$',
);

Lets take that documentation and split it up:

  • trusted_proxies
    -- Absolutely understandable, this is fine, since your proxy has an ip
  • overwritehost
    -- To What? your proxy internal dns name? (don't forget nextcloud is hosted externally)
    -- There is no internal dns name, and if you set this to your nextcloud external dns name of one of your domains, nextcloud will always redirect 302 --> As result this is not "Multiple domains reverse SSL proxy"
    -- This is a single domain hosted nextcloud behind a proxy, with redirects.
  • overwriteprotocol
    -- This is fine and understandable, tho nextcloud will never need this behind a reverse proxy, only in rare circuumstances.
  • overwritewebroot
    -- This is not fully understandable either. Because same as with the host, so the domain part is actually probably not needed.
  • overwritecondaddr
    -- I don't understand this either, tho it has the longest description text.

So basically, i could make a PR, with a better description and example.
But someone has to explain to me, what on this "Multiple domains reverse SSL proxy" is actually Multiple?

Cheers

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked “Multiple domains reverse SSL proxy” section in the Nextcloud administrator documentation and compare it with the linked help.nextcloud.com discussion. Determine what “multiple domains” is intended to describe, then clarify the parameter explanations and example so the supported setup and its limitations are unambiguous.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.