Trusted domain entry 11 invalid in ipv6 environment

Trusted Domain entry 11 is invalid when IPv6 is used.

Line 14 in 2ada653

pub_ip="$(curl -m4 icanhazip.com 2>/dev/null)"

Line 16 in 2ada653

    
           [[ "$pub_ip"   != "" ]] && ncc config:system:set trusted_domains 11 --value="$pub_ip"

Option -m4 seems to be undefined, hence curl -m4 icanhazip.com always returns IPv6.

Solution

if ipv6 is returned then the value should be enclosed in brackets „[]“ when set (line 16)
run curl -4 icanhazip.com in order to always return ipv4 (line 14)

Thank you, that's indeed a typo. It'll be fixed in the next release

@theCalcaholic

created a PR: #2075 ... @theCalcaholic I thought you wanted to have a max time and as it is a good idea I have kept the typo 😄. Also an ipv6 support is not really bad, what do you think?

-m, --max-time

Set the maximum time in seconds that you allow each transfer to take. Prevents your batch jobs from hanging for hours due to slow networks or links going down. This option accepts decimal values.

If you enable retrying the transfer (--retry) then the maximum time counter is reset each time the transfer is retried. You can use --retry-max-time to limit the retry time.

The decimal value needs to be provided using a dot (.) as decimal separator - not the local version even if it might be using another separator.

If --max-time is provided several times, the last set value is used.

Examples:

curl --max-time 10 https://example.com
curl --max-time 2.92 https://example.com

See also --connect-timeout and --retry-max-time.

Merge branch 'devel' into fix-nextcloud#2060-invalid-ipv6-value

Merge pull request #2075 from lukaszgoworko/fix-#2060-invalid-ipv6-value

Navigation Menu

Repository navigation

Trusted domain entry 11 invalid in ipv6 environment #2060

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Trusted domain entry 11 invalid in ipv6 environment #2060

Description

Activity

theCalcaholic commented on Sep 30, 2025

lukaszgoworko commented on Oct 16, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions