Bug: updates.json incorrectly used to determine current IP #524

Open
opened 2025-11-20 04:24:43 -05:00 by saavagebueno · 1 comment
Owner

Originally created by @Sophist-UK on GitHub (May 14, 2025).

TLDR: Old IP address from updates.json used and then docker deployment fails

  1. Is this urgent: Yes (not for me - but because it potentially impacts all users)

  2. DNS provider(s) you use: dynv6.net, dynu

  3. Program version: 2.9.0

    Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)

  4. What are you using to run the container: TrueNAS Scale 24.10.2.2

  5. Extra information (optional)

    a. Docker image wouldn't exit Deploying.
    b. Found ERROR program is unhealthy: lookup IP addresses do not match: 195.184.243.12 instead of 94.126.149.149 for casalaranja.webredirect.org
    c. Public IP address is 195.184.243.12, both my ddns records are already set to this.
    d. Only reference to 94.126.149.149 was in updates.json (but in the early entries - not in the latest entries).
    e. I renamed updates,json to something else and restarted the container and it deployed just fine.

    I am attaching the old updates.json file so that it can be analysed.

updates.json

Originally created by @Sophist-UK on GitHub (May 14, 2025). <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> **TLDR**: *Old IP address from updates.json used and then docker deployment fails* 1. Is this urgent: Yes (not for me - but because it potentially impacts all users) 2. DNS provider(s) you use: dynv6.net, dynu 3. Program version: 2.9.0 <!-- See the line at the top of your logs --> `Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)` 4. What are you using to run the container: TrueNAS Scale 24.10.2.2 5. Extra information (optional) a. Docker image wouldn't exit `Deploying`. b. Found `ERROR program is unhealthy: lookup IP addresses do not match: 195.184.243.12 instead of 94.126.149.149 for casalaranja.webredirect.org` c. Public IP address is 195.184.243.12, both my ddns records are already set to this. d. Only reference to 94.126.149.149 was in updates.json (but in the early entries - not in the latest entries). e. I renamed updates,json to something else and restarted the container and it deployed just fine. I am attaching the old updates.json file so that it can be analysed. [updates.json](https://github.com/user-attachments/files/20211409/updates.json)
Author
Owner

@Sophist-UK commented on GitHub (Oct 14, 2025):

Same problem again. Deleting updates.json didn't solve it this time.

@Sophist-UK commented on GitHub (Oct 14, 2025): Same problem again. Deleting updates.json didn't solve it this time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#524