Support custom port for onlyoffice #5899
Open
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.
In some cases, like usage of Nextcloud at home with a single IPv4 only, it is required to deploy the Nextcloud UI on a different port than 443. This can be achieved by configuring a domain value like "example.com:12345" in the mastercontainer's configuration.json file and using a custom reverse proxy configuration.
However onlyoffice will not work in this case. It relies on the X-Forwarded-Host header set in the Caddy config and will use the domain "https://example.com" without the custom port when constructing it's Javascript requests.
Caddy supports the variable {http.request.hostport}. By using this in the Caddyfile we can add support for custom ports.