[Support] Linuxserver.io - DuckDNS


Recommended Posts

2 hours ago, Myleslewis said:

Not sure if this is the right place to post this, however my IP changed the other day but I had to manually update it on duckdns.org, when I check the logs I get the following message repeated at 5 min intervals:

 

Something went wrong, please check your settings Sat May 23 15:10:03 BST 2020
/app/duck.conf: line 1: f844c07d-6640-4969-b0af-a3535718d11e: command not found

 

Not sure where the issue lies, my side on DuckDNS side.

 

Thanks,

 

Myles

 

Looks like your config is wrong. What does it say on line 1?

 

Link to comment
On 5/23/2020 at 7:31 AM, Myleslewis said:

Not sure if this is the right place to post this, however my IP changed the other day but I had to manually update it on duckdns.org, when I check the logs I get the following message repeated at 5 min intervals:

 

Something went wrong, please check your settings Sat May 23 15:10:03 BST 2020
/app/duck.conf: line 1: f844c07d-6640-4969-b0af-a3535718d11e: command not found

 

Not sure where the issue lies, my side on DuckDNS side.

 

Thanks,

 

Myles

 

I was having this problem earlier, it turns out there was a leading space at the start of the token from when I copied the token from duckdns. When I removed the leading space everything worked.

  • Like 3
Link to comment
  • 3 weeks later...

Hi everyone,

 

I'm a full blown noob when it comes to UnRAID (come from OMV on top of Debian), and am still at the very beginning of my learning curve (not even sure it's a curve yet, more like a flat line).

 

Here's the situation I've hit myself in the face with:

 

I have full access from the internet to my Nextcloud (as does my wife, don't want any trouble there), however, when I try to access my UnRAID web page, all I get is a "Welcome to our server" message;

image.png.c38ebfc9496c74f158833d52af8b797b.png

 

This is my DuckDNS docker configuration:

image.thumb.png.fdf0608eab950d5b797fa382584285e4.png

image.thumb.png.4377f50430951fb9a3bf67d88e7d9639.png

My LetsEcrypt log reads the following:

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
-------------------------------------

To support the app dev(s) visit:
Let's Encrypt: https://letsencrypt.org/donate/

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
Variables set:
PUID=99
PGID=100
TZ=America/La_Paz
URL=duckdns.org
SUBDOMAINS=vsnextcloud,vsunraid
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=true
DHLEVEL=2048
VALIDATION=http
DNSPLUGIN=
[email protected]
STAGING=

2048 bit DH parameters present
SUBDOMAINS entered, processing
SUBDOMAINS entered, processing
Only subdomains, no URL in cert
Sub-domains processed are: -d vsnextcloud.duckdns.org -d vsunraid.duckdns.org
E-mail address entered: [email protected]
http validation is selected
Certificate exists; parameters unchanged; starting nginx
Starting 2019/12/30, GeoIP2 databases require personal license key to download. Please retrieve a free license key from MaxMind,
and add a new env variable "MAXMINDDB_LICENSE_KEY", set to your license key.
[cont-init.d] 50-config: exited 0.
[cont-init.d] 60-renew: executing...
The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
[cont-init.d] 60-renew: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

Server ready

(removed real email address for evident reasons).

 

So, I know the setup is working.

 

Maybe something missing in the letsencrypt config files?

 

The reason I ask is because I do have a LetsEncrypt conf file for my Nextcloud, but I have no idea if I need to set up a separate conf file for the UnRAID web access.

 

What can I do to get to the login screen?

 

Any and all help will be greatly appreciated.

Link to comment

Thank you so much.

 

Now I have a direct tunnel into my house form each of my devices when traveling.

 

So far UnRAID is working much better and is more solid than any of my previous OMV instances.

 

Plus, the response from the community (granted, this was my first reaching out) is much faster and to the point.

Link to comment
  • 1 month later...
8 hours ago, andyd said:

In case this is an issue for anyone else using multiple subdomains: don't use spaces between the domain and comma. it will fail to pick up the domains correctly

That's why the readme states "comma separated, no spaces" 😉

  • Like 1
  • Haha 1
Link to comment
  • 2 weeks later...

So I set up the docker, but for some reason it keeps detecting my IP as something that is not my IP.  The docker seems to be running fine, if I manually change it to the correct IP (the one I see in my router's config) then my openVPN works fine.  Until it changes it back to the same "not my IP" IP 5 minutes later.  I followed Spaceinvader One's tutorial, didn't change any other settings.  I disabled other dockers, even disabled openVPN to see if it was somehow changing something, but nope.  Still goes back to random IP I've never seen before, it starts with 96, my real IP starts with 10, and all my network IPs start with 192.  Any clue what is going wrong?

 

Edit: I did an IP lookup online, and apparently it returns the same "not my IP" address.  It names it as part of my ISP, so could it be something my ISP is doing weird and not showing my true IP?  When I look up my actual IP, it has no info besides "Private IP Address LAN".  So I guess my ISP is just being weird?

Edited by ChIck3n
More info
Link to comment

Your LAN IP may start with 10, but that is not what you want and that wouldn't be useful 

 

It is the WAN IP of your router that you need, and it is probably working correctly. 

 

You just need to figure out what to do  next to forward ports to your servers LAN IP.

 

If you don't understand this you need to step back before you expose your server to hack attacks on the internet. 

Link to comment

IP checks including duckdns' auto check rely on pinging a remote server and asking the remote server to respond back with the address they see the request coming from.

 

Somehow your internet connection is going out through that IP you're seeing but don't recognize.

 

Does your internet connection go out through a vpn? If so, that's your vpn provider's IP

Edited by aptalca
Link to comment
8 hours ago, trurl said:

Your LAN IP may start with 10, but that is not what you want and that wouldn't be useful 

 

It is the WAN IP of your router that you need, and it is probably working correctly. 

 

You just need to figure out what to do  next to forward ports to your servers LAN IP.

 

If you don't understand this you need to step back before you expose your server to hack attacks on the internet. 

Ok, little confusion in wording here I guess.  My LAN IP is 192, I know not to use this.  The WAN IP of my router is the one starting with 10.  The one DuckDNS reports is the one starting with 96.  96 is what all the "find IP" websites return as well, and shows all the correct data for my ISP.  The only info on the 10 address is that it is a LAN IP, but this router is plugged directly into the ISP provided fiber network box.  I'm at a loss here, it's like my ISP is running me on an internal LAN or something?

 

7 hours ago, aptalca said:

IP checks including duckdns' auto check rely on pinging a remote server and asking the remote server to respond back with the address they see the request coming from.

 

Somehow your internet connection is going out through that IP you're seeing but don't recognize.

 

Does your internet connection go out through a vpn? If so, that's your vpn provider's IP

Nope, no VPN is enabled on my end.  All my devices return that IP when I go to IP check websites, but the WAN IP on my router is different.  The one DuckDNS reports has all the correct info for my ISP, so it's not like it's getting bad info, but it's just not the one on my router.  More and more it's looking like something weird my ISP is doing, but I'm not sure.

Link to comment
1 hour ago, ChIck3n said:

Ok, little confusion in wording here I guess.  My LAN IP is 192, I know not to use this.  The WAN IP of my router is the one starting with 10.  The one DuckDNS reports is the one starting with 96.  96 is what all the "find IP" websites return as well, and shows all the correct data for my ISP.  The only info on the 10 address is that it is a LAN IP, but this router is plugged directly into the ISP provided fiber network box.  I'm at a loss here, it's like my ISP is running me on an internal LAN or something?

 

Nope, no VPN is enabled on my end.  All my devices return that IP when I go to IP check websites, but the WAN IP on my router is different.  The one DuckDNS reports has all the correct info for my ISP, so it's not like it's getting bad info, but it's just not the one on my router.  More and more it's looking like something weird my ISP is doing, but I'm not sure.

Sounds like your isp put your router behind a nat, so your router is not getting the public ip (10.x.x.x are typically private addresses). The public ip address seems to be the one starting with 96.

 

What kind of fiber box are you using? Is it a router? My isp has a fiber ont on the outside of my house, which is the equivalent of a modem. They also tried to sell me their router which they claim is required for tv capability. If you have that and connected your own router to it, then you're double natted.

 

I refused their router and instead hooked up my own router (pfsense) directly to the ont unit via Ethernet so my router gets the public ip directly (I don't care for tv service).

Link to comment
  • 4 weeks later...
1 hour ago, Schicksal said:

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

https://www.duckdns.org/faqs.jsp

Q: why can't you detect IPv6 addresses?

A: our service is hosted in AWS, they do not support IPv6 on Elastic Load Balancers for the account type we have (VPC), when amazon do support it, we will start detecting it.

 

BTW, apparently there are ways to make duckdns ipv6 work, but you would have to figure it out for yourself. I don't know if it would be possible in this container.

Link to comment
  • 1 month later...

hi! i've been using this docker for some month not, but i have a strange (at least for me) problem...

duckdns says the ip address is 90.*.*.* (verified according to https://www.duckdns.org/spec.jsp ), but if i ping my (sub)domain i get a 82.*.*.* ip address. Edit: my router also says 90.* i the correct ip...

docker log tells me every five minutes: "Your IP was updated at Mon Oct 5 12:30:07 CEST 2020"

i haven't changed anything in my config...

Edited by pika
Link to comment
  • 3 weeks later...
On 10/5/2020 at 12:34 PM, pika said:

hi! i've been using this docker for some month not, but i have a strange (at least for me) problem...

duckdns says the ip address is 90.*.*.* (verified according to https://www.duckdns.org/spec.jsp ), but if i ping my (sub)domain i get a 82.*.*.* ip address. Edit: my router also says 90.* i the correct ip...

docker log tells me every five minutes: "Your IP was updated at Mon Oct 5 12:30:07 CEST 2020"

i haven't changed anything in my config...

Facing the same issue as I type this :(

Link to comment
  • 3 months later...

Hello,

As the container description is :

Quote

Duck DNS is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice. 

 

Is there a way to dynamically push the Unraid server private IP to our duckdns subdomain ?

For instance, if my RAID server change from 192.168.1.10 to 192.168.1.11, I would like mysub.duckdns.org to point to 192.168.1.11 as of now.

 

Many thanks

Link to comment
1 hour ago, Miidnight said:

 

Is there a way to dynamically push the Unraid server private IP to our duckdns subdomain ?

Private IP's can not normally be mapped to a domain.

 

If your private IP is changing, you need to fix that by configuring your router's DHCP to give Unraid the same IP every time.

  • Like 1
Link to comment

As jonathanm said you can't use an internal network ip (192.168.1.10) as a dns forward ip.. every single person on the internet, in the entire world, could have their own devices on 192.168.1.10 .. so how would it forward to you?

 

Set your router's DHCP settings to have Unraid use a static ip (set the mac address of your Unraid motherboard/network card) to 192.168.10.1 or whatever you want.

 

Then use DuckDNS to forward your domain to your PUBLIC IP address -- which always routes to you.  Access to services is directed by your router's open ports and/or reverse proxy... 

  • Like 1
Link to comment

Thank you both of you for your answer. I just wanted to be sure that is was not possible for the DuckDNS case according to the description linuxserver guys made.

 

I will set my Unraid IP as static and will assign the DuckDNS to that IP. The reason I am doing this is that I use something similar to the DuckDNS "DNS Validation method" for certificate that you can see in that article : https://github.com/dani-garcia/bitwarden_rs/wiki/Running-a-private-bitwarden_rs-instance-with-Let's-Encrypt-certs

 

A way for me to keep all internally without opening my router's ports.

 

Have a good day !

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.