-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DuckDNS add-on stopped updating IP addresses #2668
Comments
Just want to add, I have one installation with the same issue. Just a continuous WARNING message in the logs over time. Never updates the IPv4 (I don't use v6). Have verified the host can access the required internet sites for proper updates. Oddly, I have three other installs that do not have this issue. Addon Version: 1.15 s6-rc: info: service s6rc-oneshot-runner: starting |
I am seeing the same symptoms. On version 1.15, repeated "WARNING: " lines in the logs every 5 minutes. I only have ipv4 updates configured. When I ssh into my home assistant instance, I can successfully run |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The issue is still here. Do not close it, please! Reinstallation of the addon does not help. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have the same problem: last month autoupdate stop work :-( |
I found a workaround: I configured the official DuckDns integration (https://www.home-assistant.io/integrations/duckdns/) and it updates the ip. The addon is able to generate certificates. |
thx, but is an complicated solution (i don't need home-assistant). There is a log od duckdns client? |
This is still reproing for me; it should be reopened. |
Describe the issue you are experiencing
At some point the DuckDNS add-on stopped updating both IPv4 and IPv6 address. I cannot say when it happened, I didn't access my host from outside for a while.
There are warning in the add-on log, see below.
But if I run
curl -s "https://www.duckdns.org/update?domains={my domain}&token={my token}&ipv6={my ipv6}&verbose=true"
manually in the SSH add-on, I get:And I can see the address is updated on duckdns.org.
The same happens for the Ipv4 - no automatic updates, but manual update works fine.
Am I doing something wrong?
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Duck DNS
What is the version of the add-on?
1.15.0
Steps to reproduce the issue
My configuration:
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started # INFO: Using main config file /data/workdir/config + Account already registered! [12:49:53] WARNING: [12:49:53] WARNING: [12:49:54] INFO: Renew certificate for domains: .....
The
WARNING
line is repeated continuously.The text was updated successfully, but these errors were encountered: