Wondering if anyone had some guidance on what's going on. Had ddclient up and running right before the upgrade to 23.7.x seemed to work after the upgrade. I noticed today I could no longer connect to my VPN, noticed my wan IP wasn't correct so checked ddclient and noticed it hasn't updated since the 23rd of this month. See log output. Seems like it's unable to detect my wan IP for some reason.
Depending on your configuration could try changing the backend to native or some other tweaks may be required
Quote from: newsense on August 28, 2023, 01:21:13 AM
Depending on your configuration could try changing the backend to native or some other tweaks may be required
Weird, so I just checked it was set to native, so I switched it to ddclient then applied, but no change. Decided to switch it back, then applied and the IPs updated. What in the world?
Well the message "no global IP" means you use interface based detection and your WAN address was private. With that you can't update the DNS entry in the Internet as it would be unreachable.
I'd recommend IP check method "freedns" with interface unset (unless you really want to have multi-WAN).
It works for both ddclient and native. That being said the message was emitted from native backend and I'm not sure ddclient will even let you know about this.
Cheers,
Franco
Quote from: franco on August 28, 2023, 09:17:09 AM
Well the message "no global IP" means you use interface based detection and your WAN address was private. With that you can't update the DNS entry in the Internet as it would be unreachable.
I'd recommend IP check method "freedns" with interface unset (unless you really want to have multi-WAN).
It works for both ddclient and native. That being said the message was emitted from native backend and I'm not sure ddclient will even let you know about this.
Cheers,
Franco
That's how I had it with my initial config, if I set it to free dns and unset the interface, I get this error, I was able to work around it last time by selecting the interface directly. Assumed that was proper confiig after it worked.
failed to set new ip [{"result":null,"success":false,"errors":[{"code":9005,"message":"Content for A record must be a valid IPv4 address."}],"messages":[]}]
It seems like the internal curl invoke fails, because it can't fetch a global address because it cannot reach the selected check IP server which would return that. Not sure if DNS issue or routing issue.
Cheers,
Franco
Quote from: franco on August 29, 2023, 01:41:57 PM
It seems like the internal curl invoke fails, because it can't fetch a global address because it cannot reach the selected check IP server which would return that. Not sure if DNS issue or routing issue.
Cheers,
Franco
Thoughts on troubleshooting? Setup is pretty simple. Firewall> bridged modem > Internet.
Sent from my Pixel 6 Pro using Tapatalk
try different methods for WAN IP and see how things go. Dependingon your setup eben "Inteface" might work, have this running here (not with 23.7 though....) with bridged modem setup...
I don't mean to whine about this plugin, but if feels broken. Using the method of FreeDNS worked once but now is failing like before, and now it has a public IP listed that doesn't match anything I have now oddly. Could have been during a fail-over event over my ATT LTE connection. But doesn't look like it's able to get the current WAN IP now that it's failed back.
Edit: To add to this, it only seems to update one time. The only way I can get subsequent updates is to change the backend and restart the service, it'll work that one time, but fail every time afterward. I changed it back to watching the interface this time to get the correct WAN ip on my primary WAN link, it was hung on what I can only guess was my external IP for my ATT LTE Modem.
Is this plugin working well for others? Is it just my multi-wan setup that's breaking this?
It'd be a bit of work but I might have to bring this farther inside my network if I can get this sorted on the firewall.