DDNS IP/updated columns do not update

[julsssark]

Thank you for the awesome new release! I upgraded without problem and added a new DDNS using Cloudflare API token (new feature in DDClient 3.10). The logs show that DDNS is being updated without error. However, the IP and Updated columns of the UI remain blank (see attachment).

Keep up the great work.

[Earthling3063]

Seeing the same after the update to 23.1 on os-ddclient 3.10, using DuckDNS. The IPs do get updated properly on DuckDNS but since Opnsense doesn't think the IPs are updated, it updates the server every time, instead of checking the WAN first to see if the IP has changed, before forcing an update.

This is the log:

Code: [Select]

2023-01-27T09:22:31-08:00 Notice ddclient[25031] 58089 - [meta sequenceId="72"] FAILED: updating ********.duckdns.org: Server said: '0'
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 57487 - [meta sequenceId="71"] RECEIVE:
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 57126 - [meta sequenceId="70"] RECEIVE: 0
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 56686 - [meta sequenceId="69"] RECEIVE: OK
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 55957 - [meta sequenceId="68"] RECEIVE: 2
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 55697 - [meta sequenceId="67"] RECEIVE:
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 55234 - [meta sequenceId="66"] RECEIVE: X-Frame-Options: DENY
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 54804 - [meta sequenceId="65"] RECEIVE: X-Clacks-Overhead: GNU Terry Pratchett
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 54033 - [meta sequenceId="64"] RECEIVE: Server: nginx/1.20.0
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 53564 - [meta sequenceId="63"] RECEIVE: Set-Cookie: AWSALBCORS=**************; Expires=Fri, 03 Feb 2023 17:22:31 GMT; Path=/; SameSite=None; Secure
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 52923 - [meta sequenceId="62"] RECEIVE: Set-Cookie: AWSALB=************; Expires=Fri, 03 Feb 2023 17:22:31 GMT; Path=/
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 52511 - [meta sequenceId="61"] RECEIVE: Connection: close
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 51833 - [meta sequenceId="60"] RECEIVE: Transfer-Encoding: chunked
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 51399 - [meta sequenceId="59"] RECEIVE: Date: Fri, 27 Jan 2023 17:22:31 GMT
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 50596 - [meta sequenceId="58"] RECEIVE: HTTP/1.1 200 OK
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 50352 - [meta sequenceId="57"] SENDING:
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 50352 - [meta sequenceId="56"] SENDING: Connection: close
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 50352 - [meta sequenceId="55"] SENDING: User-Agent: ddclient/3.10.0
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 50352 - [meta sequenceId="54"] SENDING: Host: www.duckdns.org
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 50352 - [meta sequenceId="53"] SENDING: GET /update?domains=*********.duckdns.org&token=*********&ip=***.***.***.*** HTTP/1.1
2023-01-27T09:22:31-08:00 Notice ddclient[25031] 49805 - [meta sequenceId="52"] CONNECTED: using SSL
2023-01-27T09:22:30-08:00 Notice ddclient[25031] 49352 - [meta sequenceId="51"] CONNECT: www.duckdns.org
2023-01-27T09:22:30-08:00 Notice ddclient[25031] 48890 - [meta sequenceId="50"] UPDATE: updating *********.duckdns.org
2023-01-27T09:22:30-08:00 Notice ddclient[25031] 48179 - [meta sequenceId="49"] INFO: setting IP address to ***.***.***.*** for *********.duckdns.org

[Christophe999s]

Having the same issues
I have both duckdns and cloudflare and can confirm
With both duckdns and cloudflare, the ip's are updated, but aren't showing in the columns and ddclient keeps updating.

Edit: I've opened an issue on github for ddclient reporting it didn't update duckdns while it did: https://github.com/ddclient/ddclient/issues/503

[swILeZBa]

Same issue here with dyndns and njalla.

But it seems like the problem has been fixed upstream and now we only have to wait until it makes its way to a release.

I don't know if it has been intentionally dropped but maybe the force update button would be nice to have in ddclient plugin as well for situations like these to test that the update has been done manually.

[Earthling3063]

Same issue here with dyndns and njalla.

But it seems like the problem has been fixed upstream and now we only have to wait until it makes its way to a release.

I don't know if it has been intentionally dropped but maybe the force update button would be nice to have in ddclient plugin as well for situations like these to test that the update has been done manually.

I got an update today to OPNsense 23.1_6 and os-ddclient 1.11_1 but it doesn't seem to be the fix. You can force update of ddclient via cron btw.

[julsssark]

Original issues are still present in 23.1.1.

[xpendable]

I use no-ip for my ddns and in order to have the IP/Updated columns show information I have to set the Check IP Method to googledomains and use OPNsense for the backend. However by setting OPNsense as the backend, the ddclient service on the dashboard shows that it is down and not started.

Also if I set the Check IP Method to Interface IPv4, then ddclient will start once check/set the IP and then stop the service until the next manual start.

[antsh415]

I am seeing the same. I use three services: cloudflare, duckdns, and dyndns. All three were working as expected through the 22.7 series, but since I upgraded to 23.1.1_2 none of the columns update. I use the interface WAN method for updates for all three services.

[tidarp5]

I start having this issue with duckdns since updated to 23.1.1 from 23.1_6, which is strange  .

[His.Dudeness]

Hi,
I am seeing the same after updating today. I am using "Custom Service" with protocol "DynDns2"  for selfhost.de

Check IP method -> interface
"Current IP" and "Updated" columns are empty

Log says :
FAILED: was not updated because protocol <undefined> is not supported.
FAILED: updating : unexpected status (0)

cheers
Michael

[salvador fx]

the problem is the lack of glasses of those who decided to replace this thing that never worked properly.
Opnsense loses a lot of reputation with this.
For me it was the best of all, I was even considering paying for the most complete version, but I'm starting to look for other solutions.

[franco]

I'd say the sum of useful contributions in code is sadly much less than the abundance of useless rants like this one.


Cheers,
Franco

[kintaroju]

I'd say the sum of useful contributions in code is sadly much less than the abundance of useless rants like this one.


Cheers,
Franco

I know that some users are less appreciative of your teams effort to get the product more functional and to fix bugs. But for other users that know you are working hard on this we appreciate it, just like that netmap issue with zenarmor. 


Side note when the ddclient gets updated, and you want someone to test it, just let us know, thanks again!

[Christophe999s]

I've opened an issue on github for this: https://github.com/opnsense/core/issues/6407

[franco]

I'd appreciate encouragement in the ddclient direction to release a bugfix version. As such I've marked the ticket "upstream" to reflect that it needs movement there to proceed.


Cheers,
Franco