os-ddclient

[skyeci2018]

All very odd. I did a full rebuild up to the latest version. Same issue after reboot. File and timestamp changed back to original file. Not sure what else I can do. Something is replacing the file upon a reboot.....annoyingly it works how I need but can't get it to keep the contents of the file...

Surely I can't be the only one with this issue..

[CGrisamore]

Yes, very confusing.  Have you considered using chmod to set permissions of ddclient.conf to read only? 

[skyeci2018]

That sounds like a plan. I will try that tonight when I get home and report back...

[tofflock]

That sounds like a plan. I will try that tonight when I get home and report back...

I would also be inclined to create another file in that directory (/usr/local/etc I believe) with your own file name and contents.  Do this before rebooting, and check that it survives the boot process.  This would help to eliminate a file system etc problem/feature - because I don't think we know anything about your test system.

Just a thought...

PeterF

[skyeci2018]

Hi Peter
I will do this too but the build is literally a fresh build with no changes by myself to the config.

[skyeci2018]

Hi Peter.

I can confirm a random file in the same folder survives a reboot. So far no luck in resolving it.

[AdSchellevis]

if you want to use ddclient without the gui components, just install ddclient (and not os-ddclient), Any plugin will always flush the configuration files on disk with the contents as configured.....

Code Select Expand


pkg install ddclient


Should probably do the trick.

Best regards,

Ad

[skyeci2018]

Thank you. I will try this later tonight.

[skyeci2018]

thanks to all for your help. I have now got it working with no deletion of the contents of my ddclient.conf config.
installed the package manually and then set it up using a free host name from dynu. They provided some basic script examples for ddclient which I have replicated into my conf file. Its updating every 5 minutes  as expected with confirmation in the sys log

ddclient[7427]   55641 - [meta sequenceId="1"] SUCCESS: mydomain.ddnsfree.com: skipped: IP address was already set to my address

[CGrisamore]

I performed the upgrade this morning to 22.1.9 (which included an update to the ddclient plugin).  After rebooting I found that my existing ddclient.conf file had been replaced with a newly generated version which contained the content previously entered in the OPNsense web interface.  I had manually edited my ddclient.conf file as my provider uses a token which contains an ampersand and the OPNsense web form would not allow entry of an ampersand so had I not spotted this I would have been left with a nonworking configuration.

Heads up to all who have manually customized ddclient.conf, after upgrading  check your ddclient.conf  file located in /usr/local/etc directory.  Lucky I had a copy saved elsewhere that I could transfer to the OPNsense box.

[xboarder56]

Hi All,

Edit: solution was to disable force ssl

Trying to configure DDclient on 22.1.9 but running into the following error (replaced IP):

Code Select Expand

2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84797 - [meta sequenceId="4"] WARNING: Wait at least 5 minutes between update attempts.
2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84797 - [meta sequenceId="3"] WARNING: last updated <never> but last attempt on Sat Jun 25 18:28:53 2022 failed.
2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84797 - [meta sequenceId="2"] WARNING: skipping update of example.com from <nothing> to 111.111.111.111.
2022-06-25T18:29:04-07:00 Notice ddclient[82993] 84222 - [meta sequenceId="1"] WARNING: file /var/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''

[jondoe]

I have updated to 22.1.9 with ddclient 3.9.1. GoDaddy is still not available in the GUI. How Do I configure GoDaddy in /usr/local/etc/ddclient.conf?

[skyeci2018]

I upgraded and encountered no issues with my conf file after the process completed. Will we get a widget sometime like was possible before?

thanks

[andersgo@gmail.com]

I finally managed to get my DynDNS to work with ddclient

checkip -t 1/0 did not provide any reply. Removing it completely worked

# /usr/local/opnsense/scripts/ddclient/checkip -i re0 -s dyndns
xxx.xxx.xxx.xxx

[TrueType]

It shouldn't be this hard to get it working when the last plugin was working flawlessly, please someone with developing skills look into this thread..