[Support] Linuxserver.io - DuckDNS


Recommended Posts

Hi folks. New to unraid and just installed this plugin. Love it! One thing I noticed is it tries to update every 5 minutes. I get a lot of "something went wrong" errors in the log. It does eventually update my ip. I am wondering is there is a way to update like every hour or so. Five minute intervals might be causing my issue. 

Link to comment
21 hours ago, bclinton said:

Hi folks. New to unraid and just installed this plugin. Love it! One thing I noticed is it tries to update every 5 minutes. I get a lot of "something went wrong" errors in the log. It does eventually update my ip. I am wondering is there is a way to update like every hour or so. Five minute intervals might be causing my issue. 

Not sure when your problem started but as of right now duckdns.org is down so that probably has something to do with it.  My log is filled with the same message.  I'd wait for the server to be up and then check.  I've never had an issue with the default times.

Link to comment

So i've been looking into this again and I still get a lot of "Something went wrong, please check your settings", and the DuckDNS service (website) is up.

 

If my duckdns address is testing123.duckdns.org and I only specify testing123 as the subdomain I get frequent something went wrong messages inbetween repeated "Your IP was updated at " messages ---- if the IP has not changed this should be a different message such as no change, nothing done.

 

If I specify any/multiple subdomains, such as sonarr,radarr then I get constant something went wrong messages and no IP update messages.

 

In any regard, is this DuckDNS docker still operating accurately? 

Edited by Energen
Link to comment
13 hours ago, Energen said:

So i've been looking into this again and I still get a lot of "Something went wrong, please check your settings", and the DuckDNS service (website) is up.

 

If my duckdns address is testing123.duckdns.org and I only specify testing123 as the subdomain I get frequent something went wrong messages inbetween repeated "Your IP was updated at " messages ---- if the IP has not changed this should be a different message such as no change, nothing done.

 

If I specify any/multiple subdomains, such as sonarr,radarr then I get constant something went wrong messages and no IP update messages.

 

In any regard, is this DuckDNS docker still operating accurately? 

It's still operating. Working here without errors.

 

Spoke too soon. Looks like it's not updating the IP for some reason.

Edited by saarg
Link to comment
  • 1 month later...

Hi - I am having trouble getting duckdns/swag/wireguard to work for me. I've followed a number of guides but can't get it going.

 

Symptoms:

- Going to https://MYSERVER.duckdns.org - cannot reach server. Specific ports (e.g. :8989 for Sonarr) do not work either

- Wireguard peers when service enabled cannot reach any IPs.

 

I believe I have configured all correctly, and port forwarding for Wireguard appears properly enabled.

 

Where would I start to troubleshoot this? All help appreciated.

Link to comment

Not really a big issue but does anybody know why my DuckDNS container would be mis-reporting a use of 9 Exabytes of RAM? I'm not getting any errors in the log at the time these spikes happen so I'm not worried it's broken, just is mildly annoying/funny because it makes my status graph unreadable as it scales Y to account for the spike: 

 

image.thumb.png.11044f6e9b926e429900c2d06a370549.png

 

EDIT: This is the Grafana query used to source the data from Influxdb: 

image.png.ec2833f2cf88e8563022e7fefd7f826d.png

 

And I believe this is the only portion of the telegraf.conf file that would collect memory usage data: 

image.png.a274f45bccdeb16fee22740680d557f5.png

Edited by scd780
Link to comment
On 2/14/2021 at 1:27 PM, saarg said:

It's still operating. Working here without errors.

 

Spoke too soon. Looks like it's not updating the IP for some reason.

I'm also getting a lot of errors, but it does update every now and then...

image.png.0e51b5bed3731d36f93c5266d73d17a6.png

Link to comment

I know this has been answered before, however I feel something may have changed since those answers. I would like to run a second instance of this container, however whenever I go to add it again from apps, it just changes the settings of the existing container (I have changed the name of the container, however all that does is change it from 'duckdns' to 'duckdns2' with the same subdomains and a new token - ie does not create a second instance. 

What am I missing here?

Link to comment
  • 2 months later...
On 8/20/2020 at 10:27 PM, Schicksal said:

still no IPv6 support in this docker? I have no IPv4.

 

You can use my script:

 

It obtains the IPv6 from the ethernet interface or if you like from a specific docker container.

 

Link to comment
On 4/16/2021 at 6:34 AM, Sayuuk said:

I'm also getting a lot of errors, but it does update every now and then...

image.png.0e51b5bed3731d36f93c5266d73d17a6.png

I've been having this problem for roughly 3 weeks now. I'm not getting any updates, though. Is this a problem on the docker side or the duckdns side?

Link to comment
  • 2 weeks later...
On 7/2/2021 at 3:17 AM, thatnovaguy said:

I've been having this problem for roughly 3 weeks now. I'm not getting any updates, though. Is this a problem on the docker side or the duckdns side?

Sorry mate,

 

my log is clean now - I'm unsure as to which side needed fixing...

 

Cheers

Stefan

Link to comment
Sorry mate,
 
my log is clean now - I'm unsure as to which side needed fixing...
 
Cheers
Stefan
I appreciate your reply. I finally figured it out. Wireguard was somehow meeting everything up. No clue how but disabling it fixed everything lol.

Sent from my SM-G998U using Tapatalk

Link to comment
  • 4 months later...
22 hours ago, Mattti1912 said:

Hello

 

I've installed duckdns but when i type my dynamic dns, it keeps hitting my router.. Mikrotik..

How can i change that??

 

regards

Hi, you’ll need to direct that traffic to the appropriate location via a proxy. Most people use the SWAG or NGINX-Proxy-Manager (NPM) containers. I recommend NPM, more user friendly imo! 
 

You’ll want to look into it more if this is brand new to you but the gist of it is that you forward ports 80 and 443 from your router to your proxy software and then your proxy software has NGINX config files and SSL certs to authoritatively direct traffic on your network. 
 

The flow of data would be someone visits your domain (subdomain1.duckdns.org), the duckdns service tells the user’s browser that that subdomain routes to your public IP address, the browser then sends an HTTP/S request to your public IP, this is forwarded from your router to your proxy software via the port forwarding rule, the proxy software then looks at its own config files and knows that subdomain1 goes to location X.X.X.X:XXXX on your network vs subdomain2 which goes to Y.Y.Y.Y:YYYY and forwards the traffic there for access. 
 

there’s a few good videos and guides out there so just search around and you’ll find something. The key word to use is “reverse proxy” for informational videos and “NPM” or “NGINX Proxy Manager” for guides. Just remember to NEVER open your UnRAID webGUI to the internet through a proxy like this, it’s not secure enough for that. If you need remote access, setup Wireguard instead. It’s either a plug-in or built in to unRAID now, I forget but very easy to setup and plenty of guides as well. 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.