I am running ddclient-3.7.3, on FreeBSD-6.2, with IO::Socket::SSL-1.11
(both installed from FreeBSD ports).
I have been using ddclient-3.7.1 successfully with SSL until I updated
to ddclient-3.7.3. After the update, I get a SSL timeout and termination
of the update process on connecting to the first server.
I use ddclient to update against dyndns.com and opendns.com (for opendns
a patch was necessary until they recently changed their URI to be fully
Has anyone else observed timeouts when using SSL? I am able to update
successfully if I supply the timeout option in ddclient.conf but I wish
to determine why, and when, the need for this arose.
I think your message is related to this one: https://sourceforge.net/forum/message.php?msg_id=4590232
Maybe you could try the solution mentioned there?
I added timeout=120 to ddclient.conf long before that message was posted. That was why I suggested that a default timeout value is added to the ddclient code.
This was actually a bug in IO::Socket::SSL-1.11 which is fixed in IO::Socket::SSL-1.12.
The former version of IO::Socket::SSL treated a timeout value of 0 as a timeout condition. The latter treats it as not a timeout.
Thank you very much for the feedback. I appreciate the work you did for this issue.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.