Bug 46204 - Nextcloud trusted_domain config cuts off IPv6 addresses
Nextcloud trusted_domain config cuts off IPv6 addresses
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-31 14:42 CET by Moritz Bunkus
Modified: 2018-05-04 12:09 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Bunkus 2018-01-31 14:42:00 CET
Installing the Nextcloud app (currently version 12.0.4) generates a config.php with the following content:

  'trusted_domains' =>
  array (
    0 => 'master.mbu-test.intranet',
    1 => '10.191.1.1',
    2 => '2001',
    3 => '10.199.104.110',
    4 => '2001',
  ),

The host has two IPv6 addresses, and those are the ones that're cut off to end up ans entries 2 and 4.

This likely isn't really a problem because users will only ever access Nextcloud via a reverse proxy on the host, and the container itself doesn't get an IPv6 address — therefore contacting the container directly from an IPv6 address isn't possible.