Thanks

I would like to uninstall / get rid of duckdns completey but do fail. I deleted the container but as I do no longer have access to my account (although I have email and token, I get an login error that states "wrong email or token"; while I am able to use the exact same credentials for connectiong to duckdns over other ways than persona singin), the old address is still pointing to my server. 

 

Any idea, or contact address or any helpful hint on how I could get rid of the duckdns address pointing to my server?

 

Thank you so much!

1 hour ago, hi2hello said:

I would like to uninstall / get rid of duckdns completey but do fail. I deleted the container but as I do no longer have access to my account (although I have email and token, I get an login error that states "wrong email or token"; while I am able to use the exact same credentials for connectiong to duckdns over other ways than persona singin), the old address is still pointing to my server. 

 

Any idea, or contact address or any helpful hint on how I could get rid of the duckdns address pointing to my server?

 

Thank you so much!

well, there are a couple of ways:

[email protected]

[email protected]

or https://groups.google.com/g/duckdns


Edit, since you can actually still use the api token, you can also push a force ip update out like

 

curl -sS --max-time 60 "https://www.duckdns.org/update?domains=YOUR-DOMAIN-NAME&token=YOUR-TOKEN&clear=true"

Checked their docs again. If you need to clear ipv6 as well, you can also run or open it like this

 

https://www.duckdns.org/update?domains={YOURVALUE}&token={YOURVALUE}[&ip=0.0.0.0][&ipv6=::][&verbose=true][&clear=true]

Edit: Just tested it, the curl one i send first does clear ipv6 as well. Docs were a bit uncertain with their wording

Edited July 19, 20241 yr by Mainfrezzer

Thank you very much!

I wrote to privacy@… No answer so far, that is why I was asking for options. 

I tried your proposal and have two questions:

1. Should there be a response? Probably not on i curl command, right?

2. Related to the domains. Just the domain-name without TLD, right? 

 

Anyway, thanks again for your kind advice till now. I did not know how annoying it could get, to delete a duckdns entry. 

 

Edit: Seems your proposal did the trick. The URL is no longer reachable. Checking deposited IPs on the relevant addresses returned, that there is no longer any IP related to the URL.

 

THANK YOU!

Edited July 22, 20241 yr by hi2hello

This may not apply specifically to this DuckDNS docker by linuxserver but this is the issue.

 

When I try to install I get the following.  
"...Unable to find image 'lscr.io/linuxserver/duckdns:latest' locally
docker: Error response from daemon: Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)...."

 

I am able to nslookup lscr.io from the terminal.  I am unable to ping it (this may not mean much as a lot of things are unpingable).

 

This also happened when trying to install the linuxserver plex container.  I ended up just installing another plex container.  Am I missing something?  Is there an extra step that I am not reading in the docs to use linuxserver's repository that I am missing?  I can download other containers and install them without issue.  Still new to unraid but really loving it over my very old ReadyNas NV+ and a 10 year old desktop running Plex.zelda-diagnostics-20241101-1329.zip

 

Diagnostic is attached from right after the failure.

 

Any help would be extremely appreciated.

 

Had this docker like forever... then realized recently my IP didn't get updated properly.

After investigation, found the (what now seems frequent) dreaded "Something went wrong, please check your settings...."

It turns out that the subdomains were all listed as "xxxx.duckdns.org,yyyy.duckdns.org" in the template.

Changing that to "xxxx,yyyy" (so removing the .duckdns.org" for each of them) fixed everything.

This WAS working on older versions of this docker. It would have been nice to get some kind of more visible alert than over-inflated logs. Like stopping the docker if no valid subdomain can be checked or updated.

Anyway. This was my fix