mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-08-02 10:38:41 -04:00
Bug: updates.json incorrectly used to determine current IP #524
Reference in New Issue
Block a user
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?
Originally created by @Sophist-UK on GitHub (May 14, 2025).
TLDR: Old IP address from updates.json used and then docker deployment fails
Is this urgent: Yes (not for me - but because it potentially impacts all users)
DNS provider(s) you use: dynv6.net, dynu
Program version: 2.9.0
Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)What are you using to run the container: TrueNAS Scale 24.10.2.2
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.orgc. 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
@Sophist-UK commented on GitHub (Oct 14, 2025):
Same problem again. Deleting updates.json didn't solve it this time.