Cannot update IPv6 with deSEC

[neko-js]

I thought I can simply switch to ipv6 by setting "ip_version" to "ipv6". Here is my config.json:

{
  "settings": [
    {
      "provider": "desec",
      "domain": "dedyn.io",
      "host": "hostname",
      "token": "token",
      "ip_version": "ipv6",
      "ipv6_suffix": "",
      "provider_ip": false
    }
  ]
}

But unfortunately it does not update the IP. The web GUI displays:

I have set up AAAA on deSEC website. I assume that my configuration file is wrong. Can anyone help me out?

[qdm12]

What version are you running? Try pulling the latest image, it has many fixes recently done in the last 2-3 weeks. 🤔

[neko-js]

I am running the latest version. Installed it like 12 hours ago. I will also mention, that it works with IPv4.

[qdm12]

Ok! What do you have in the container logs?

[neko-js]

Here is the container log. It says that it "cannot assign requested address". I accessed the APIs directly and they all work, providing my public IPv6 address.

2024-02-01 10:52:36 ddns-updater  | Running version latest built on 2024-01-31T14:34:20.254Z (commit 875cd02)
[...]
2024-02-01 10:52:36 ddns-updater  | 2024-02-01T09:52:36Z INFO Settings summary:
2024-02-01 10:52:36 ddns-updater  | ├── HTTP client
2024-02-01 10:52:36 ddns-updater  | |   └── Timeout: 10s
2024-02-01 10:52:36 ddns-updater  | ├── Update
2024-02-01 10:52:36 ddns-updater  | |   ├── Period: 5m0s
2024-02-01 10:52:36 ddns-updater  | |   └── Cooldown: 5m0s
2024-02-01 10:52:36 ddns-updater  | ├── Public IP fetching
2024-02-01 10:52:36 ddns-updater  | |   ├── HTTP enabled: yes
2024-02-01 10:52:36 ddns-updater  | |   ├── HTTP IP providers
2024-02-01 10:52:36 ddns-updater  | |   |   └── all
2024-02-01 10:52:36 ddns-updater  | |   ├── HTTP IPv4 providers
2024-02-01 10:52:36 ddns-updater  | |   |   └── all
2024-02-01 10:52:36 ddns-updater  | |   ├── HTTP IPv6 providers
2024-02-01 10:52:36 ddns-updater  | |   |   └── all
2024-02-01 10:52:36 ddns-updater  | |   ├── DNS enabled: yes
2024-02-01 10:52:36 ddns-updater  | |   ├── DNS timeout: 3s
2024-02-01 10:52:36 ddns-updater  | |   └── DNS over TLS providers
2024-02-01 10:52:36 ddns-updater  | |       └── all
2024-02-01 10:52:36 ddns-updater  | ├── Resolver: use Go default resolver
2024-02-01 10:52:36 ddns-updater  | ├── Server
2024-02-01 10:52:36 ddns-updater  | |   ├── Listening address: :8000
2024-02-01 10:52:36 ddns-updater  | |   └── Root URL: /
2024-02-01 10:52:36 ddns-updater  | ├── Health
2024-02-01 10:52:36 ddns-updater  | |   └── Server listening address: 127.0.0.1:9999
2024-02-01 10:52:36 ddns-updater  | ├── Paths
2024-02-01 10:52:36 ddns-updater  | |   └── Data directory: /updater/data
2024-02-01 10:52:36 ddns-updater  | ├── Backup: disabled
2024-02-01 10:52:36 ddns-updater  | └── Logger
2024-02-01 10:52:36 ddns-updater  |     ├── Level: info
2024-02-01 10:52:36 ddns-updater  |     └── Caller: hidden
2024-02-01 10:52:36 ddns-updater  | 2024-02-01T09:52:36Z INFO reading JSON config from file /updater/data/config.json
2024-02-01 10:52:36 ddns-updater  | 2024-02-01T09:52:36Z INFO Found single setting to update record
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z INFO Reading history from database: domain dedyn.io host hostname ipv6
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z INFO [backup] disabled
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z INFO [http server] listening on :8000
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z INFO [healthcheck server] listening on 127.0.0.1:9999
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z WARN obtaining ipv6 address: try 1 of 3: Get "https://api6.ipify.org": dial tcp [2607:f2d8:2010:2::3]:443: connect: cannot assign requested address
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z WARN obtaining ipv6 address: try 2 of 3: dial tcp6 [2606:4700:4700::1111]:853: connect: cannot assign requested address
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z WARN obtaining ipv6 address: try 3 of 3: Get "http://ip1.dynupdate6.no-ip.com": dial tcp [2a07:dc00:1330:2::204]:80: connect: cannot assign requested address
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z ERROR Get "http://ip1.dynupdate6.no-ip.com": dial tcp [2a07:dc00:1330:2::204]:80: connect: cannot assign requested address
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z WARN Skipping update for hostname.dedyn.io because ipv6 address was not found
2024-02-01 10:52:37 ddns-updater  | 2024-02-01T09:52:37Z ERROR setting initial up to date status: IP to update is not valid

[qdm12]

Ok, many things to unpack, but the quick TLDR for you is your Docker setup or host or network doesn't have IPv6 enabled, so it fails to fetch it, that's why you get connect: cannot assign requested address. Now on the various problems that came out of this, such as the UI being weird, or the logs being not so helpful:

• ebd852f sets the record status to FAIL with the message Public IP not found, if the public IP fetching fails for the record IP version (ipv6 in your case). That won't leave the record in that ugly UNSET state.
• 6f71982 explicitly logs the error that IPv6 is not supported if all 3 tries result in an error containing connect: cannot assign requested address
• 443daad changes log messages to be less repetitive/more informative. Each try error (1 to 3) gets logged at the DEBUG level, and all of them are logged in a single log line at the ERROR level if all tries fail. That should also reduce noise in case one of the tries fail, which happens from time to time.

You'll need to pull the latest image again to get these changes 😉

I'll mark this as the answer since that should be it, but feel free to comment if you have any... comment 😄 Thanks for taking the time to report this!

[neko-js]

Thank you for looking into this and making the log functions better. I looked into enabling IPv6, but I'm running Docker in Windows and the official guide mentions:

IPv6 is only supported on Docker daemons running on Linux hosts.

There goes my dream. 🐱

[qdm12]

Give me a 24 hours, I'm about to make a v2.6.0 release which will have attached binaries for windows

If you can't wait, you can install Go and then in a terminal type go install github.com/qdm12/ddns-updater/cmd/updater@latest and you should then have an updater.exe program available in your PATH. You can use flags equivalent to environment variables (example RESOLVER_ADDRESS is the flag --resolver-addreas). I would be happy to have a first windows beta tester 😄

[neko-js]

I just tried this out and it simply works! Thanks!!