starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-08-02 10:38:41 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

Bug: ERROR program is unhealthy: lookup IP addresses do not match #276

New Issue
Closed
opened 2025-11-20 04:22:14 -05:00 by saavagebueno · 12 comments
saavagebueno commented 2025-11-20 04:22:14 -05:00
Owner
Copy Link

Originally created by @tiberio87 on GitHub (Apr 30, 2023).

Originally assigned to: @qdm12 on GitHub.

  1. Is this urgent:No

  2. DNS provider(s) you use: Cloudflare

  3. Program version: Latest

    Running version latest built on 2023-04-17T11:30:42Z (commit 522cc7c)

  4. What are you using to run the container: docker-compose

  5. Extra information:


  # Cloudflare DDNS - Dynamic DNS Updater
  ddns-updater:
    image: qmcgaw/ddns-updater
    container_name: ddns-updater
    restart: always
    network_mode: bridge
    ports:
      - 8001:8000/tcp
    dns:
      - 1.1.1.1       
    volumes:
      - $DOCKERDIR/appdata/ddns-updater:/updater/data # Owned by UID 1000
    environment:
      <<: *default-tz-puid-pgid
      RESOLVER_ADDRESS: 1.1.1.1:53
      RESOLVER_TIMEOUT: 5s
      PERIOD: 12h
      UPDATE_COOLDOWN_PERIOD: 5m
      PUBLICIP_DNS_TIMEOUT: 3s
      HTTP_TIMEOUT: 10s
      # Web UI
      LISTENING_PORT: 8000
      # Backup
      BACKUP_PERIOD: 0 # 0 to disable
      BACKUP_DIRECTORY: /updater/data/backups
      # Other
      LOG_LEVEL: info    
      # SHOUTRRR_ADDRESSES: $DISCORD_SHOUTRRR_ADDRESS
    labels:
      ## AUTO Update
      - "com.centurylinklabs.watchtower.enable=true"

Logs:


========================================
========================================
============= ddns-updater =============
========================================
=========== Made with ❤️ by ============
======= https://github.com/qdm12 =======
========================================
========================================

Running version latest built on 2023-04-17T11:30:42Z (commit 522cc7c)

🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new
🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new
✨ New feature? https://github.com/qdm12/ddns-updater/issues/new
☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new
💻 Email? quentin.mcgaw@gmail.com
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2023-04-30T09:54:08+02:00 INFO reading JSON config from file /updater/data/config.json
2023-04-30T09:54:08+02:00 INFO Found single setting to update record
2023-04-30T09:54:08+02:00 INFO Reading history from database: domain ## host @
2023-04-30T09:54:08+02:00 INFO [healthcheck server] listening on 127.0.0.1:9999
2023-04-30T09:54:08+02:00 INFO [http server] listening on :8000
2023-04-30T09:54:08+02:00 INFO [backup] disabled
2023-04-30T09:54:09+02:00 INFO IPv4 address of ## is ## and your IPv4 address is ##
2023-04-30T09:54:09+02:00 INFO Updating record [domain: ## | host: @ | provider: cloudflare | ip: ipv4] to use ##
2023/04/30 09:54:43 "GET http://##:8001/ HTTP/1.1" from ##62516 - 200 1705B in 47.085µs

Configuration file (remove your credentials!):


{
    "settings": [
      {
        "provider": "cloudflare",
        "zone_identifier": "##",
        "domain": "##",
        "host": "@",
        "ttl": 600,
        "token": "##",
        "ip_version": "ipv4"
      }
    ]
  }

Host OS: Ubuntu

Originally created by @tiberio87 on GitHub (Apr 30, 2023). Originally assigned to: @qdm12 on GitHub. <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> 1. Is this urgent:No 2. DNS provider(s) you use: Cloudflare 3. Program version: Latest <!-- See the line at the top of your logs --> `Running version latest built on 2023-04-17T11:30:42Z (commit 522cc7c) ` 4. What are you using to run the container: docker-compose 5. Extra information: ``` # Cloudflare DDNS - Dynamic DNS Updater ddns-updater: image: qmcgaw/ddns-updater container_name: ddns-updater restart: always network_mode: bridge ports: - 8001:8000/tcp dns: - 1.1.1.1 volumes: - $DOCKERDIR/appdata/ddns-updater:/updater/data # Owned by UID 1000 environment: <<: *default-tz-puid-pgid RESOLVER_ADDRESS: 1.1.1.1:53 RESOLVER_TIMEOUT: 5s PERIOD: 12h UPDATE_COOLDOWN_PERIOD: 5m PUBLICIP_DNS_TIMEOUT: 3s HTTP_TIMEOUT: 10s # Web UI LISTENING_PORT: 8000 # Backup BACKUP_PERIOD: 0 # 0 to disable BACKUP_DIRECTORY: /updater/data/backups # Other LOG_LEVEL: info # SHOUTRRR_ADDRESSES: $DISCORD_SHOUTRRR_ADDRESS labels: ## AUTO Update - "com.centurylinklabs.watchtower.enable=true" ``` Logs: ``` ======================================== ======================================== ============= ddns-updater ============= ======================================== =========== Made with ❤️ by ============ ======= https://github.com/qdm12 ======= ======================================== ======================================== Running version latest built on 2023-04-17T11:30:42Z (commit 522cc7c) 🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new 🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new 💻 Email? quentin.mcgaw@gmail.com 💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12 2023-04-30T09:54:08+02:00 INFO reading JSON config from file /updater/data/config.json 2023-04-30T09:54:08+02:00 INFO Found single setting to update record 2023-04-30T09:54:08+02:00 INFO Reading history from database: domain ## host @ 2023-04-30T09:54:08+02:00 INFO [healthcheck server] listening on 127.0.0.1:9999 2023-04-30T09:54:08+02:00 INFO [http server] listening on :8000 2023-04-30T09:54:08+02:00 INFO [backup] disabled 2023-04-30T09:54:09+02:00 INFO IPv4 address of ## is ## and your IPv4 address is ## 2023-04-30T09:54:09+02:00 INFO Updating record [domain: ## | host: @ | provider: cloudflare | ip: ipv4] to use ## 2023/04/30 09:54:43 "GET http://##:8001/ HTTP/1.1" from ##62516 - 200 1705B in 47.085µs ``` Configuration file (**remove your credentials!**): ``` { "settings": [ { "provider": "cloudflare", "zone_identifier": "##", "domain": "##", "host": "@", "ttl": 600, "token": "##", "ip_version": "ipv4" } ] } ``` Host OS: Ubuntu
saavagebueno commented 2025-11-20 04:22:15 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jun 12, 2023):

I don't see the error log in your logs, can you share it?

The error you saw can happen if we just updated and we then lookup, since updating the DNS records can take time to propagate. What's the frequency of the error log you saw?

@qdm12 commented on GitHub (Jun 12, 2023): I don't see the error log in your logs, can you share it? The error you saw can happen if we just updated and we then lookup, since updating the DNS records can take time to propagate. What's the frequency of the error log you saw?
saavagebueno commented 2025-11-20 04:22:16 -05:00
Author
Owner
Copy Link

@tiberio87 commented on GitHub (Jun 12, 2023):

Running version latest built on an unknown date (commit 5676673)

📣 Environment variables parsing was changed on 12 June, please report any issue you might have

🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new

🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new

✨ New feature? https://github.com/qdm12/ddns-updater/issues/new

☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new

💻 Email? quentin.mcgaw@gmail.com

💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12

2023-06-12T16:57:50+02:00 INFO Settings summary:

├── HTTP client

|   └── Timeout: 10s

├── Update

|   ├── Period: 10m0s

|   └── Cooldown: 5m0s

├── Public IP fetching

|   ├── HTTP enabled: yes

|   ├── HTTP IP providers

|   |   └── all

|   ├── HTTP IPv4 providers

|   |   └── all

|   ├── HTTP IPv6 providers

|   |   └── all

|   ├── DNS enabled: yes

|   ├── DNS timeout: 3s

|   └── DNS providers

|       └── all

├── Resolver: use Go default resolver

├── IPv6

|   └── Mask bits: 128

├── Server

|   ├── Port: 8000

|   └── Root URL: /

├── Health

|   └── Server listening address: 127.0.0.1:9999

├── Paths

|   └── Data directory: /updater/data

├── Backup

|   ├── Period: 0s

|   └── Directory: /updater/data/backups

├── Logger

|   ├── Caller: no

|   └── Level: INFO

└── Shoutrrr

    ├── Addresses

    |   └── discord://*****

    └── Parameters

        └── title=DDNS Updater

2023-06-12T16:57:50+02:00 INFO reading JSON config from file /updater/data/config.json

2023-06-12T16:57:50+02:00 INFO Found 2 settings to update records

2023-06-12T16:57:50+02:00 INFO Reading history from database: domain ***.*** host @

2023-06-12T16:57:50+02:00 INFO Reading history from database: domain ***.***host www

2023-06-12T16:57:50+02:00 INFO [healthcheck server] listening on 127.0.0.1:9999

2023-06-12T16:57:50+02:00 INFO [http server] listening on :8000

2023-06-12T16:57:51+02:00 INFO [backup] disabled
@tiberio87 commented on GitHub (Jun 12, 2023): ```log Running version latest built on an unknown date (commit 5676673) 📣 Environment variables parsing was changed on 12 June, please report any issue you might have 🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new 🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new 💻 Email? quentin.mcgaw@gmail.com 💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12 2023-06-12T16:57:50+02:00 INFO Settings summary: ├── HTTP client | └── Timeout: 10s ├── Update | ├── Period: 10m0s | └── Cooldown: 5m0s ├── Public IP fetching | ├── HTTP enabled: yes | ├── HTTP IP providers | | └── all | ├── HTTP IPv4 providers | | └── all | ├── HTTP IPv6 providers | | └── all | ├── DNS enabled: yes | ├── DNS timeout: 3s | └── DNS providers | └── all ├── Resolver: use Go default resolver ├── IPv6 | └── Mask bits: 128 ├── Server | ├── Port: 8000 | └── Root URL: / ├── Health | └── Server listening address: 127.0.0.1:9999 ├── Paths | └── Data directory: /updater/data ├── Backup | ├── Period: 0s | └── Directory: /updater/data/backups ├── Logger | ├── Caller: no | └── Level: INFO └── Shoutrrr ├── Addresses | └── discord://***** └── Parameters └── title=DDNS Updater 2023-06-12T16:57:50+02:00 INFO reading JSON config from file /updater/data/config.json 2023-06-12T16:57:50+02:00 INFO Found 2 settings to update records 2023-06-12T16:57:50+02:00 INFO Reading history from database: domain ***.*** host @ 2023-06-12T16:57:50+02:00 INFO Reading history from database: domain ***.***host www 2023-06-12T16:57:50+02:00 INFO [healthcheck server] listening on 127.0.0.1:9999 2023-06-12T16:57:50+02:00 INFO [http server] listening on :8000 2023-06-12T16:57:51+02:00 INFO [backup] disabled ```
saavagebueno commented 2025-11-20 04:22:16 -05:00
Author
Owner
Copy Link

@tiberio87 commented on GitHub (Jun 12, 2023):

With the latest update everything seems to work perfectly, thanks.

@tiberio87 commented on GitHub (Jun 12, 2023): With the latest update everything seems to work perfectly, thanks.
saavagebueno commented 2025-11-20 04:22:16 -05:00
Author
Owner
Copy Link

@goluftwaffe commented on GitHub (Oct 16, 2023):

I do have the same problem, I think my problem is that I'm not sure what to put in "domain" and "host for dnsomatic... I've put my personal root domain in domain and one of my host name that I use to reach my server at home...

The updates work, but the IP on web page doesn't change and the containers stays unhealthy:

2023-10-16T16:47:22-04:00 ERROR program is unhealthy: lookup IP addresses do not match: newip instead of oldip for myhost.mydomain.com
2023-10-16T16:47:22-04:00 INFO Shutdown successful

2023-10-16T16:46:22-04:00 DEBUG config read: {
  "settings": [
    {
      "provider": "dnsomatic",
      "domain": "mydomain.com",
      "host": "myhost",
      "username": "user",
      "password": "pass",
      "provider_ip": true,
      "ip_version": "ipv4"
    }
  ]
}
2023-10-16T16:46:22-04:00 INFO Found single setting to update record
2023-10-16T16:46:22-04:00 INFO Reading history from database: domain mydomain.com host myhost
2023-10-16T16:46:22-04:00 INFO [http server] listening on :8000
2023-10-16T16:46:22-04:00 INFO [healthcheck server] listening on 127.0.0.1:9999
2023-10-16T16:46:22-04:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false
2023-10-16T16:46:22-04:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: newip, v6: invalid IP
2023-10-16T16:46:22-04:00 DEBUG IPv4 address of myhost.mydomain.com is newip and your IPv4 address is newip, skipping update
2023-10-16T16:46:23-04:00 INFO [backup] disabled
2023/10/16 16:46:26 "GET http://192.168.1.145:8000/ HTTP/1.1" from 192.168.1.96:56295 - 200 1686B in 42.235µs

Thank you!

@goluftwaffe commented on GitHub (Oct 16, 2023): I do have the same problem, I think my problem is that I'm not sure what to put in "domain" and "host for dnsomatic... I've put my personal root domain in domain and one of my host name that I use to reach my server at home... The updates work, but the IP on web page doesn't change and the containers stays unhealthy: ``` 2023-10-16T16:47:22-04:00 ERROR program is unhealthy: lookup IP addresses do not match: newip instead of oldip for myhost.mydomain.com 2023-10-16T16:47:22-04:00 INFO Shutdown successful ``` ``` 2023-10-16T16:46:22-04:00 DEBUG config read: { "settings": [ { "provider": "dnsomatic", "domain": "mydomain.com", "host": "myhost", "username": "user", "password": "pass", "provider_ip": true, "ip_version": "ipv4" } ] } 2023-10-16T16:46:22-04:00 INFO Found single setting to update record 2023-10-16T16:46:22-04:00 INFO Reading history from database: domain mydomain.com host myhost 2023-10-16T16:46:22-04:00 INFO [http server] listening on :8000 2023-10-16T16:46:22-04:00 INFO [healthcheck server] listening on 127.0.0.1:9999 2023-10-16T16:46:22-04:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false 2023-10-16T16:46:22-04:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: newip, v6: invalid IP 2023-10-16T16:46:22-04:00 DEBUG IPv4 address of myhost.mydomain.com is newip and your IPv4 address is newip, skipping update 2023-10-16T16:46:23-04:00 INFO [backup] disabled 2023/10/16 16:46:26 "GET http://192.168.1.145:8000/ HTTP/1.1" from 192.168.1.96:56295 - 200 1686B in 42.235µs ``` Thank you!
saavagebueno commented 2025-11-20 04:22:16 -05:00
Author
Owner
Copy Link

@LeVraiRoiDHyrule commented on GitHub (Feb 7, 2024):

Hi, I am having an error which I think is very similar. I am trying to update my IP on Cloudflare. It works, but it updates continuously as it is unable to check if the IP is already correctly set. And the healthcheck fails with the following error:
2024-02-08T00:07:28+01:00 ERROR program is unhealthy: lookup IP addresses do not match

My config is the following:

{
  "settings": [
    {
      "provider": "cloudflare",
      "zone_identifier": "[REDACTED]",
      "domain": "mydomain.com",
      "host": "@",
      "ttl": 1,
      "token": "[REDACTED]",
      "ip_version": "ipv4"
    },
    {
      "provider": "cloudflare",
      "zone_identifier": "[REDACTED]",
      "domain": "mydomain.com",
      "host": "@",
      "ttl": 1,
      "token": "[REDACTED]",
      "ip_version": "ipv6"
    }
  ]
}

The problem is that ddns-updater web ui is not hosted on mydomain.com but on ddns.mydomain.com, so the healthcheck server is also on that subdomain. But what I want to update is the root of my domain. If I set "host" to ddns.mydomain.com, then it only updates this subdomain. I don't know how I am supposed to do when hosting the web ui on a subdomain.

Thanks in advance for any answer and have a great day

@LeVraiRoiDHyrule commented on GitHub (Feb 7, 2024): Hi, I am having an error which I think is very similar. I am trying to update my IP on Cloudflare. It works, but it updates continuously as it is unable to check if the IP is already correctly set. And the healthcheck fails with the following error: `2024-02-08T00:07:28+01:00 ERROR program is unhealthy: lookup IP addresses do not match` My config is the following: ``` { "settings": [ { "provider": "cloudflare", "zone_identifier": "[REDACTED]", "domain": "mydomain.com", "host": "@", "ttl": 1, "token": "[REDACTED]", "ip_version": "ipv4" }, { "provider": "cloudflare", "zone_identifier": "[REDACTED]", "domain": "mydomain.com", "host": "@", "ttl": 1, "token": "[REDACTED]", "ip_version": "ipv6" } ] } ``` The problem is that ddns-updater web ui is not hosted on `mydomain.com` but on `ddns.mydomain.com`, so the healthcheck server is also on that subdomain. But what I want to update is the root of my domain. If I set "host" to `ddns.mydomain.com`, then it only updates this subdomain. I don't know how I am supposed to do when hosting the web ui on a subdomain. Thanks in advance for any answer and have a great day
saavagebueno commented 2025-11-20 04:22:16 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Feb 7, 2024):

@LeVraiRoiDHyrule Check the Cloudflare document again, you probably want to use the proxied field as true.

The problem is that ddns-updater web ui is not hosted on mydomain.com but on ddns.mydomain.com, so the healthcheck server is also on that subdomain.

That doesn't matter / has influence on anything really.

@qdm12 commented on GitHub (Feb 7, 2024): @LeVraiRoiDHyrule Check the Cloudflare document again, you probably want to use the proxied field as true. > The problem is that ddns-updater web ui is not hosted on mydomain.com but on ddns.mydomain.com, so the healthcheck server is also on that subdomain. That doesn't matter / has influence on anything really.
saavagebueno commented 2025-11-20 04:22:16 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Feb 7, 2024):

@goluftwaffe sorry for the delay answering;

IPv4 address of myhost.mydomain.com is newip and your IPv4 address is newip, skipping update

should mean there is no need to update, strange it's getting unhealhy. You can try the newer image 2.6 ot latest since many fixes were done during the last 3 weeks.

@qdm12 commented on GitHub (Feb 7, 2024): @goluftwaffe sorry for the delay answering; ``` IPv4 address of myhost.mydomain.com is newip and your IPv4 address is newip, skipping update ``` should mean there is no need to update, strange it's getting unhealhy. You can try the newer image 2.6 ot latest since many fixes were done during the last 3 weeks.
saavagebueno commented 2025-11-20 04:22:17 -05:00
Author
Owner
Copy Link

@goluftwaffe commented on GitHub (Feb 8, 2024):

Thank you for the answer, I've move my dns name to cloudfare and all is working properly... I'm on the latest version.

@goluftwaffe commented on GitHub (Feb 8, 2024): Thank you for the answer, I've move my dns name to cloudfare and all is working properly... I'm on the latest version.
saavagebueno commented 2025-11-20 04:22:17 -05:00
Author
Owner
Copy Link

@LeVraiRoiDHyrule commented on GitHub (Feb 8, 2024):

@LeVraiRoiDHyrule Check the Cloudflare document again, you probably want to use the proxied field as true.

The problem is that ddns-updater web ui is not hosted on mydomain.com but on ddns.mydomain.com, so the healthcheck server is also on that subdomain.

That doesn't matter / has influence on anything really.

Thanks for your answer. I tried with the "proxied" field to true, for both ipv4 and ipv6, and I'm still having the same issue. DDNS updater is unable to check if the record has been updated and updates continuously.

@LeVraiRoiDHyrule commented on GitHub (Feb 8, 2024): > @LeVraiRoiDHyrule Check the Cloudflare document again, you probably want to use the proxied field as true. > > > The problem is that ddns-updater web ui is not hosted on mydomain.com but on ddns.mydomain.com, so the healthcheck server is also on that subdomain. > > That doesn't matter / has influence on anything really. Thanks for your answer. I tried with the "proxied" field to true, for both ipv4 and ipv6, and I'm still having the same issue. DDNS updater is unable to check if the record has been updated and updates continuously.
saavagebueno commented 2025-11-20 04:22:17 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Feb 9, 2024):

@LeVraiRoiDHyrule can you send your logs from the container running with LOG_LEVEL=debug? (make sure to remove credentials).

@qdm12 commented on GitHub (Feb 9, 2024): @LeVraiRoiDHyrule can you send your logs from the container running with `LOG_LEVEL=debug`? (make sure to remove credentials).
saavagebueno commented 2025-11-20 04:22:17 -05:00
Author
Owner
Copy Link

@LeVraiRoiDHyrule commented on GitHub (May 21, 2024):

@LeVraiRoiDHyrule can you send your logs from the container running with LOG_LEVEL=debug? (make sure to remove credentials).

Hi again. Sorry for the (very long) delay. I am still having this issue. About your advice to turn on the proxied setting in my config, this means turning on the "Proxy subdomain through cloudflare" setting at each update on Cloudflare admin panel, and I don't want to use this feature (I use Cloudflare as a simple DNS only). So I'll leave it to false. I still tried it and with proxied:true, the health server was healthy and everything was fine except that it turns on the proxy feature of Cloudflare at each update. Is ddns-updater able to work with Cloudflare without using its proxy feature ?

With that said, here is my logs with LOG_LEVEL=debug:

2024-05-21T11:56:29+02:00 INFO reading JSON config from environment variable CONFIG
2024-05-21T11:56:29+02:00 DEBUG config read: {"settings": [{"provider": "cloudflare", "zone_identifier":"REDACTED", "domain":"REDACTED.com", "host":"@", "ttl": 1, "token":"REDACTED", "ip_version":"ipv4", "proxied":false},{"provider": "cloudflare", "zone_identifier":"REDACTED", "domain":"REDACTED.com", "host":"@", "ttl": 1, "token":"REDACTED", "ip_version":"ipv6", "proxied":false}]}
2024-05-21T11:56:29+02:00 INFO Found 2 settings to update records
2024-05-21T11:56:29+02:00 INFO Reading history from database: domain REDACTED.com host @ ipv4
2024-05-21T11:56:29+02:00 INFO Reading history from database: domain REDACTED.com host @ ipv6
2024-05-21T11:56:29+02:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: true
2024-05-21T11:56:29+02:00 INFO [backup] disabled
2024-05-21T11:56:29+02:00 INFO [healthcheck server] listening on 127.0.0.1:9999
2024-05-21T11:56:29+02:00 INFO [http server] listening on :8000
2024-05-21T11:56:29+02:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: REDACTED, v6: REDACTED
2024-05-21T11:56:29+02:00 DEBUG record REDACTED.com (ipv4) is within cooldown period of 5m0s, skipping update
2024-05-21T11:56:29+02:00 DEBUG record REDACTED.com (ipv6) is within cooldown period of 5m0s, skipping update

The error of the health server is

ERROR program is unhealthy: lookup IP addresses do not match: 172.100.0.10,REDACTED instead of REDACTED for REDACTED.com 2024-05-21T12:01:29+02:00 INFO Shutdown successful

To me, it looks like there is no real error in the container but the health server seems to be the only one in error.
Would you have an idea of what could be causing this ?
Thanks in advance and have a nice day.

@LeVraiRoiDHyrule commented on GitHub (May 21, 2024): > @LeVraiRoiDHyrule can you send your logs from the container running with `LOG_LEVEL=debug`? (make sure to remove credentials). Hi again. Sorry for the (very long) delay. I am still having this issue. About your advice to turn on the `proxied` setting in my config, this means turning on the "Proxy subdomain through cloudflare" setting at each update on Cloudflare admin panel, and I don't want to use this feature (I use Cloudflare as a simple DNS only). So I'll leave it to false. I still tried it and with `proxied:true`, the health server was healthy and everything was fine except that it turns on the proxy feature of Cloudflare at each update. Is ddns-updater able to work with Cloudflare without using its proxy feature ? With that said, here is my logs with `LOG_LEVEL=debug`: ``` 2024-05-21T11:56:29+02:00 INFO reading JSON config from environment variable CONFIG 2024-05-21T11:56:29+02:00 DEBUG config read: {"settings": [{"provider": "cloudflare", "zone_identifier":"REDACTED", "domain":"REDACTED.com", "host":"@", "ttl": 1, "token":"REDACTED", "ip_version":"ipv4", "proxied":false},{"provider": "cloudflare", "zone_identifier":"REDACTED", "domain":"REDACTED.com", "host":"@", "ttl": 1, "token":"REDACTED", "ip_version":"ipv6", "proxied":false}]} 2024-05-21T11:56:29+02:00 INFO Found 2 settings to update records 2024-05-21T11:56:29+02:00 INFO Reading history from database: domain REDACTED.com host @ ipv4 2024-05-21T11:56:29+02:00 INFO Reading history from database: domain REDACTED.com host @ ipv6 2024-05-21T11:56:29+02:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: true 2024-05-21T11:56:29+02:00 INFO [backup] disabled 2024-05-21T11:56:29+02:00 INFO [healthcheck server] listening on 127.0.0.1:9999 2024-05-21T11:56:29+02:00 INFO [http server] listening on :8000 2024-05-21T11:56:29+02:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: REDACTED, v6: REDACTED 2024-05-21T11:56:29+02:00 DEBUG record REDACTED.com (ipv4) is within cooldown period of 5m0s, skipping update 2024-05-21T11:56:29+02:00 DEBUG record REDACTED.com (ipv6) is within cooldown period of 5m0s, skipping update ``` The error of the health server is ``` ERROR program is unhealthy: lookup IP addresses do not match: 172.100.0.10,REDACTED instead of REDACTED for REDACTED.com 2024-05-21T12:01:29+02:00 INFO Shutdown successful ``` To me, it looks like there is no real error in the container but the health server seems to be the only one in error. Would you have an idea of what could be causing this ? Thanks in advance and have a nice day.
saavagebueno commented 2025-11-20 04:22:17 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jun 16, 2024):

@LeVraiRoiDHyrule See https://github.com/qdm12/ddns-updater/discussions/726#discussioncomment-9786680

@qdm12 commented on GitHub (Jun 16, 2024): @LeVraiRoiDHyrule See https://github.com/qdm12/ddns-updater/discussions/726#discussioncomment-9786680
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label Priority: 💤 Low priority Status: 🗯️ Waiting for feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#276
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?