| View previous topic :: View next topic |
| Author |
Message |
jesnow
l33t
Joined: 26 Apr 2006
Posts: 856
|
 Posted: Sun Jan 29, 2023 8:06 pm Post subject: DDClient fails to connect [solved] |
 |
|
I don't know what I did to break DDClient. It worked for a couple years. but has been throwing a lot of errors the last couple months.
Like many people I use it to be able to get the address of my home machine to log into it. It didn't seem to be working, throwing a ton of errors:
| Code: |
Jan 29 13:15:22 merckx ddclient[12317]: WARNING: cannot connect to checkip.dyndns.org:443 socket: Connection timed out IO::Socket::IP configuration failed
Jan 29 13:15:22 merckx ddclient[12320]: WARNING: found neither IPv4 nor IPv6 address
Jan 29 13:15:22 merckx ddclient[12321]: WARNING: cannot connect to https:443 socket: Name or service not known IO::Socket::IP configuration failed
Jan 29 13:15:22 merckx ddclient[12322]: FAILED: updating merckx.vesarius.net: Could not connect to https://domains.google.com/checkip.
Jan 29 13:26:23 merckx ddclient[12343]: WARNING: cannot connect to checkip.dyndns.org:443 socket: Connection timed out IO::Socket::IP configuration failed
Jan 29 13:26:23 merckx ddclient[12346]: WARNING: found neither IPv4 nor IPv6 address
Jan 29 13:26:23 merckx ddclient[12347]: WARNING: cannot connect to https:443 socket: Name or service not known IO::Socket::IP configuration failed
Jan 29 13:26:23 merckx ddclient[12348]: FAILED: updating merckx.vesarius.net: Could not connect to https://domains.google.com/checkip.
Jan 29 13:37:23 merckx ddclient[12389]: WARNING: cannot connect to checkip.dyndns.org:443 socket: Connection timed out IO::Socket::IP configuration failed
Jan 29 13:37:23 merckx ddclient[12392]: WARNING: found neither IPv4 nor IPv6 address
Jan 29 13:37:23 merckx ddclient[12393]: WARNING: cannot connect to https:443 socket: Name or service not known IO::Socket::IP configuration failed
Jan 29 13:37:23 merckx ddclient[12394]: FAILED: updating merckx.vesarius.net: Could not connect to https://domains.google.com/checkip.
Jan 29 13:48:24 merckx ddclient[12430]: WARNING: cannot connect to checkip.dyndns.org:443 socket: Connection timed out IO::Socket::IP configuration failed
Jan 29 13:48:24 merckx ddclient[12433]: WARNING: found neither IPv4 nor IPv6 address
Jan 29 13:48:24 merckx ddclient[12434]: WARNING: cannot connect to https:443 socket: Name or service not known IO::Socket::IP configuration failed
Jan 29 13:48:24 merckx ddclient[12435]: FAILED: updating merckx.vesarius.net: Could not connect to https://domains.google.com/checkip.
|
So I checked the config file I've been using for years:
| Code: |
######################################################################
daemon=300 # check every 300 seconds
syslog=yes # log update msgs to syslog
#mail=root # mail all msgs to root
#mail-failure=jesiphone2020@gmail.com # mail failed update msgs to root
ssl=yes # use ssl-support. Works with
# ssl-library
# postscript=script i # run script after updating. The
# new IP is added as argument.
##
## Google Domains (www.google.com/domains)
##
# protocol=googledomains,
# login=my-auto-generated-username,
# password=my-auto-generated-password
# my.domain.tld, otherhost.domain.tld
protocol=dyndns2
use=web
server=https://domains.google.com/checkip
login=***
password=***
merckx.vesarius.net
|
So I went back and verified the login info, regenerated the credentials (what else could it be?).
| Code: |
merckx /home/jesnow # vi /etc/ddclient.conf
merckx /home/jesnow # /etc/init.d/ddclient restart
ddclient | * Stopping DDclient ...
ddclient | * start-stop-daemon: 1 process refused to stop
ddclient | * Failed to stop DDclient [ !! ]
ddclient | * ERROR: ddclient failed to stop
merckx /home/jesnow # ps ax | grep ddc
4225 ? S 0:01 ddclient - connecting to checkip.dyndns.org:443
12478 pts/4 S+ 0:00 grep --colour=auto ddc
merckx /home/jesnow #
|
This is really strange: there is no mention of dyndns.org in /etc/ddclient.conf. Why is ddclient trying to connect to it?
What have I done wrong?
Cheers,
Jon. |
|
| Back to top |
|
 |
jesnow
l33t
Joined: 26 Apr 2006
Posts: 856
|
| Posted: Sun Jan 29, 2023 8:12 pm Post subject: |
|
|
Figured it out. For the benefit of anybody confronted with a similar situation, the answer was right in the comment lines in the config file: Google domains doesn't use dyndns2 any more, but uses its own protocol which ddclient supports. The relevant section in the config file looks like this:
| Code: |
# protocol=googledomains,
# login=my-auto-generated-username,
# password=my-auto-generated-password
# my.domain.tld
|
Once I fixed that, ddclient connected to google domains just fine.
I think the dyndns.org in my /var/log/messages must be a bug. If it fails it must fall back to some hard wired default address.
Cheers,
Jon. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
