Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

never connects to APIs? #474

Open
hmijail opened this issue Feb 27, 2024 · 0 comments
Open

never connects to APIs? #474

hmijail opened this issue Feb 27, 2024 · 0 comments

Comments

@hmijail
Copy link

hmijail commented Feb 27, 2024

Using inadyn 2.12, as installed with brew and with brew --HEAD. macOS 14.3.1

I have prepared 2 configurations in my .conf file. Both of them seem to start working as expected... but never actually connect to the server APIs.

For example:

$ inadyn -l debug --foreground  --force -1 -f  ~/inadyn.conf
Feb 27 16:37:05  inadyn[20387] <Notice>: In-a-dyn version 2.12.0 -- Dynamic DNS update client.
Feb 27 16:37:05  inadyn[20387] <Warning>: Guessing DDNS plugin '[email protected]' from 'no-ip.com'
Feb 27 16:37:06  inadyn[20387] <Info>: Resolving hostname hmcsys.dynv6.net => IP# 104.28.250.151
Feb 27 16:37:06  inadyn[20387] <Info>: Resolving hostname all.ddnskey.com => IP# 34.198.182.201
Feb 27 16:37:06  inadyn[20387] <Debug>: Get address for [email protected]
Feb 27 16:37:06  inadyn[20387] <Debug>: Starting command to get my public IP#: INADYN_PROVIDER="[email protected]" INADYN_USER="XXX" /Users/mija/bin/get-local-ipv6.sh
Feb 27 16:37:06  inadyn[20387] <Debug>: Command 'INADYN_PROVIDER="[email protected]" INADYN_USER="XXX" /Users/mija/bin/get-local-ipv6.sh' returns 36 bytes
Feb 27 16:37:06  inadyn[20387] <Debug>: Command response:
Feb 27 16:37:06  inadyn[20387] <Debug>: XXX:YYY:ZZZ:0:3c68:50cf:eca8:967
Feb 27 16:37:06  inadyn[20387] <Debug>: Checking IPv6 address XXX:YYY:ZZZ:0:3c68:50cf:eca8:967 ...
Feb 27 16:37:06  inadyn[20387] <Debug>: IPv6 address XXX:YYY:ZZZ:0:3c68:50cf:eca8:967 is valid.
Feb 27 16:37:06  inadyn[20387] <Info>: Current IP# XXX:YYY:ZZZ:0:3c68:50cf:eca8:967 at [email protected]
Feb 27 16:37:06  inadyn[20387] <Debug>: Get address for [email protected]
Feb 27 16:37:06  inadyn[20387] <Debug>: Starting command to get my public IP#: INADYN_PROVIDER="[email protected]" INADYN_USER="XXX" /Users/mija/bin/get-local-ipv6.sh
Feb 27 16:37:06  inadyn[20387] <Debug>: Command 'INADYN_PROVIDER="[email protected]" INADYN_USER="XXX" /Users/mija/bin/get-local-ipv6.sh' returns 36 bytes
Feb 27 16:37:06  inadyn[20387] <Debug>: Command response:
Feb 27 16:37:06  inadyn[20387] <Debug>: XXX:YYY:ZZZ:0:3c68:50cf:eca8:967
Feb 27 16:37:06  inadyn[20387] <Debug>: Checking IPv6 address XXX:YYY:ZZZ:0:3c68:50cf:eca8:967 ...
Feb 27 16:37:06  inadyn[20387] <Debug>: IPv6 address XXX:YYY:ZZZ:0:3c68:50cf:eca8:967 is valid.
Feb 27 16:37:06  inadyn[20387] <Info>: Current IP# XXX:YYY:ZZZ:0:3c68:50cf:eca8:967 at [email protected]
Feb 27 16:37:06  inadyn[20387] <Notice>: Update forced for alias hmcsys.dynv6.net, new IP# XXX:YYY:ZZZ:0:3c68:50cf:eca8:967
Feb 27 16:37:06  inadyn[20387] <Notice>: Update forced for alias all.ddnskey.com, new IP# XXX:YYY:ZZZ:0:3c68:50cf:eca8:967

$

Both No-IP and DynV6 websites report that no updates have happened.
I tried using a wrong password/token and got no errors, either.

I only noticed that something is missing after the "Update forced for alias..." because I found some log to compare in some other GitHub issue, where there was a "Sending IP# update to DDNS server" line. I guess that's missing here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant