You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running version latest built on 2024-11-21T22:27:40.202Z (commit 89564b7)
What are you using to run the container: docker
Extra information (optional)
The service I'm using doesn't require passing the IP address. It just uses the IP address that's calling the service. So all functionality to get the current public IP adress can be disabled when the IPv4 key is not present or empty.
I've marked this as urgent because the whole ddns-updater service refuses to start. Now, I could probably add a bogus key and call it a day, but I will 100% forget about it, plus I shouldn't "litter" by sending foo=0.0.0.0 that's only there because an updater can't handle not sending this bit.
TLDR: Custom updater shouldn't require IPv4 key
Is this urgent: Yes
DNS provider(s) you use: Nederhost (custom)
Program version:
Running version latest built on 2024-11-21T22:27:40.202Z (commit 89564b7)
What are you using to run the container: docker
Extra information (optional)
The service I'm using doesn't require passing the IP address. It just uses the IP address that's calling the service. So all functionality to get the current public IP adress can be disabled when the IPv4 key is not present or empty.
I've marked this as urgent because the whole ddns-updater service refuses to start. Now, I could probably add a bogus key and call it a day, but I will 100% forget about it, plus I shouldn't "litter" by sending
foo=0.0.0.0
that's only there because an updater can't handle not sending this bit.Configuration file:
Host OS: Unraid
The text was updated successfully, but these errors were encountered: