_0m0t3ur Posted June 26, 2018 Share Posted June 26, 2018 (edited) 2 minutes ago, aptalca said: No, the container doesn't need any ports mapped because there are no incoming connections to this container. You can just set networking mode to bridge and not map any ports Ok. I'll change to bridge mode. There were no pre-set options in the container for paths, etc. I wasn't sure if you meant that I should be adding them. Some containers that have paths specified, I've also been able to specify additional paths for other purposes. For example in Plex specifying a path for movies. Then creating another for tv shows. Thanks for your help. Edited June 26, 2018 by DoItMyselfToo Quote Link to comment
aptalca Posted June 26, 2018 Share Posted June 26, 2018 1 hour ago, DoItMyselfToo said: Ok. I'll change to bridge mode. There were no pre-set options in the container for paths, etc. I wasn't sure if you meant that I should be adding them. Some containers that have paths specified, I've also been able to specify additional paths for other purposes. For example in Plex specifying a path for movies. Then creating another for tv shows. Thanks for your help. Nope, no paths needed either. Just supply the subdomain and the token as environment variables and that's it Quote Link to comment
FreeMan Posted September 24, 2018 Share Posted September 24, 2018 I set up 2 new subdomains at duckdns and manually set the IPs to 127.0.0.1 for testing. I installed the docker on my backup machine, gave it 10 minutes and nothing changed (even after a logout/login at duckdns). I restarted the docker and it updated the IP immediately. I set it back to 127.0.0.1, waited 5 minutes and it updated to the correct IP again. Installed it on my primary server, did the same IP test and it updated correctly the first time. Now I just need to advertise the new domain to everyone who's accessing my server and away I go. no more changeip.com or their Homing Beacon app running on my Win10 machine. Thanks to LSIO for another great docker. Quote Link to comment
garion Posted October 18, 2018 Share Posted October 18, 2018 Hi, is it possible duckdns point vpn ip (via privoxy) instead isp ip? Quote Link to comment
JonathanM Posted October 18, 2018 Share Posted October 18, 2018 32 minutes ago, garion said: Hi, is it possible duckdns point vpn ip (via privoxy) instead isp ip? Why would you want to do that? Quote Link to comment
garion Posted October 18, 2018 Share Posted October 18, 2018 3 minutes ago, jonathanm said: Why would you want to do that? Forget it. It was a silly question because vpn has no full portfordwarding so it can’t work. the idea was act as a filter. I have a calibre web in unraid and sometimes I connect in unprotected public WiFi’s via duckdns subdomain. I know I can install an OpenVPN server in unraid and connect with my phone to my internal unraid ip + calibre port (and deleting virtual server port fordward in the router). maybe there is another way to increase security. I have read some about nginx as reverse proxy but not sure if it’s the right way. Quote Link to comment
aptalca Posted October 18, 2018 Share Posted October 18, 2018 15 minutes ago, garion said: Forget it. It was a silly question because vpn has no full portfordwarding so it can’t work. the idea was act as a filter. I have a calibre web in unraid and sometimes I connect in unprotected public WiFi’s via duckdns subdomain. I know I can install an OpenVPN server in unraid and connect with my phone to my internal unraid ip + calibre port (and deleting virtual server port fordward in the router). maybe there is another way to increase security. I have read some about nginx as reverse proxy but not sure if it’s the right way. Nginx reverse proxy is the right way for that. Check out the letsencrypt image. It works with duckdns 1 Quote Link to comment
Zoc Posted November 25, 2018 Share Posted November 25, 2018 (edited) Hi I'm having issue updating my ip with this docker. Duckdns manually set to 192.0.2.1 to verify function. Docker freshly installed via CA. Docker does run but it never updates the IP. Previous posts speak about a log, where can i find that? Main server logs shows nothing related. Consoling into the docker and running /app/duck.sh returns the following: /app/duck.conf: line 1: <mytoken>: command not found Something went wrong, please check your settings Sun Nov 25 22:11:28 CET 2018 Running the command in duck.sh manually does return OK and correctly updates the IP. curl -s "https://www.duckdns.org/update?domains=<mydomain>&token=<mytoken>&ip=" duck.sh #!/usr/bin/with-contenv bash . /app/duck.conf RESPONSE=`curl -s "https://www.duckdns.org/update?domains=$SUBDOMAINS&token=$TOKEN&ip="` if [ "$RESPONSE" = "OK" ]; then echo "Your IP was updated at "$(date) else echo "Something went wrong, please check your settings "$(date) fi What am I missing? Any suggestions @aptalca? Thanks! /Zoc Edited November 25, 2018 by Zoc Quote Link to comment
aptalca Posted November 25, 2018 Share Posted November 25, 2018 52 minutes ago, Zoc said: Duckdns manually set to 192.0.2.1 to verify function. What does that mean? Did you set it on the duckdns website? Check the container log. What does that say? Quote Link to comment
Zoc Posted November 28, 2018 Share Posted November 28, 2018 On 11/25/2018 at 11:22 PM, aptalca said: What does that mean? Did you set it on the duckdns website? Check the container log. What does that say? Hi @aptalca Yes, it means I manually set the IP on duckdns.org to track when it actually updates. The log is full of the same error message: /app/duck.conf: line 1: <mytoken>: command not found Something went wrong, please check your settings Wed Nov 28 20:05:00 CET 2018 /app/duck.conf: line 1: <mytoken>: command not found Something went wrong, please check your settings Wed Nov 28 20:10:00 CET 2018 (docker logs duckdns) /Zoc Quote Link to comment
aptalca Posted November 28, 2018 Share Posted November 28, 2018 1 hour ago, Zoc said: Hi @aptalca Yes, it means I manually set the IP on duckdns.org to track when it actually updates. The log is full of the same error message: /app/duck.conf: line 1: <mytoken>: command not found Something went wrong, please check your settings Wed Nov 28 20:05:00 CET 2018 /app/duck.conf: line 1: <mytoken>: command not found Something went wrong, please check your settings Wed Nov 28 20:10:00 CET 2018 (docker logs duckdns) /Zoc It sounds like your duckdns.conf is messed up somehow. It is only supposed to contain two lines, and two items each, separated by an equal sign, no spaces. Check to see if it's the correct format. You can also pm me the contents (I believe duckdns lets you recreate the token) Also, are there any special characters in your token other than hyphen? 1 Quote Link to comment
Zoc Posted November 28, 2018 Share Posted November 28, 2018 There we have it! There was somehow a space introduced in the beginning of the token when the container was installed. This then apparently followed me around when i reinstalled. Sometimes the simple things.. Thanks @aptalca! Quote Link to comment
aptalca Posted November 29, 2018 Share Posted November 29, 2018 9 hours ago, Zoc said: There we have it! There was somehow a space introduced in the beginning of the token when the container was installed. This then apparently followed me around when i reinstalled. Sometimes the simple things.. Thanks @aptalca! Glad to hear it works now Quote Link to comment
Cathnan Posted December 8, 2018 Share Posted December 8, 2018 Hi, I set up the container and the IPv4 update works perfectly and I can reach nextcloud no problem at all. But it seems that in the default configuration my IPv6 is not updated. Is there a way to update the IPv6 as well? Quote Link to comment
aptalca Posted December 8, 2018 Share Posted December 8, 2018 10 hours ago, Cathnan said: Hi, I set up the container and the IPv4 update works perfectly and I can reach nextcloud no problem at all. But it seems that in the default configuration my IPv6 is not updated. Is there a way to update the IPv6 as well? Ipv6 is not supported in this image Quote Link to comment
Horyd Posted January 10, 2019 Share Posted January 10, 2019 my duckdns IP is being updated with my docker networking address as opposed to my ethernet card's DHCP assigned IP address. Quote Link to comment
aptalca Posted January 11, 2019 Share Posted January 11, 2019 7 hours ago, Horyd said: my duckdns IP is being updated with my docker networking address as opposed to my ethernet card's DHCP assigned IP address. Post a screenshot of your settings Quote Link to comment
Lebowski Posted January 20, 2019 Share Posted January 20, 2019 On 11/29/2018 at 7:34 AM, Zoc said: There we have it! There was somehow a space introduced in the beginning of the token when the container was installed. This then apparently followed me around when i reinstalled. Sometimes the simple things.. Thanks @aptalca! If you copy and paste the token from duckdns it has a space in front of it. 1 Quote Link to comment
meoge Posted March 19, 2019 Share Posted March 19, 2019 Should I be concerned that I get the "Something went wrong" message along with the "You IP was updated" message? It seems to fail more than it succeeds. If this is normal than I'm fine with it because it does succeed several times a day, but seems strange that it would work for a couple times and then fail multiple times. Your IP was updated at Mon Mar 18 16:10:12 EDT 2019 Your IP was updated at Mon Mar 18 16:15:01 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:20:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:25:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:30:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:35:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:40:09 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:45:05 EDT 2019 Your IP was updated at Mon Mar 18 16:50:05 EDT 2019 Your IP was updated at Mon Mar 18 16:55:11 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:00:05 EDT 2019 Your IP was updated at Mon Mar 18 17:05:08 EDT 2019 Your IP was updated at Mon Mar 18 17:10:03 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:15:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:20:06 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:25:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:30:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:35:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:40:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:45:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:50:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:55:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:00:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:05:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:10:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:15:05 EDT 2019 Your IP was updated at Mon Mar 18 18:20:09 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:25:06 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:30:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:35:05 EDT 2019 Your IP was updated at Mon Mar 18 18:40:05 EDT 2019 Your IP was updated at Mon Mar 18 18:45:09 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:50:05 EDT 2019 Your IP was updated at Mon Mar 18 18:55:07 EDT 2019 Something went wrong, please check your settings Mon Mar 18 19:00:05 EDT 2019 Your IP was updated at Mon Mar 18 19:05:10 EDT 2019 Something went wrong, please check your settings Mon Mar 18 19:10:05 EDT 2019 Your IP was updated at Mon Mar 18 19:15:07 EDT 2019 Something went wrong, please check your settings Mon Mar 18 19:20:06 EDT 2019 Your IP was updated at Mon Mar 18 19:25:04 EDT 2019 Your IP was updated at Mon Mar 18 19:30:01 EDT 2019 Your IP was updated at Mon Mar 18 19:35:05 EDT 2019 Your IP was updated at Mon Mar 18 19:40:05 EDT 2019 Your IP was updated at Mon Mar 18 19:45:09 EDT 2019 Your IP was updated at Mon Mar 18 19:50:06 EDT 2019 Your IP was updated at Mon Mar 18 19:55:07 EDT 2019 Your IP was updated at Mon Mar 18 20:00:07 EDT 2019 Your IP was updated at Mon Mar 18 20:05:05 EDT 2019 Your IP was updated at Mon Mar 18 20:10:08 EDT 2019 Your IP was updated at Mon Mar 18 20:15:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 20:20:05 EDT 2019 Quote Link to comment
aptalca Posted March 19, 2019 Share Posted March 19, 2019 1 hour ago, meoge said: Should I be concerned that I get the "Something went wrong" message along with the "You IP was updated" message? It seems to fail more than it succeeds. If this is normal than I'm fine with it because it does succeed several times a day, but seems strange that it would work for a couple times and then fail multiple times. Your IP was updated at Mon Mar 18 16:10:12 EDT 2019 Your IP was updated at Mon Mar 18 16:15:01 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:20:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:25:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:30:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:35:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:40:09 EDT 2019 Something went wrong, please check your settings Mon Mar 18 16:45:05 EDT 2019 Your IP was updated at Mon Mar 18 16:50:05 EDT 2019 Your IP was updated at Mon Mar 18 16:55:11 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:00:05 EDT 2019 Your IP was updated at Mon Mar 18 17:05:08 EDT 2019 Your IP was updated at Mon Mar 18 17:10:03 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:15:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:20:06 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:25:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:30:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:35:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:40:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:45:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:50:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 17:55:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:00:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:05:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:10:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:15:05 EDT 2019 Your IP was updated at Mon Mar 18 18:20:09 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:25:06 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:30:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:35:05 EDT 2019 Your IP was updated at Mon Mar 18 18:40:05 EDT 2019 Your IP was updated at Mon Mar 18 18:45:09 EDT 2019 Something went wrong, please check your settings Mon Mar 18 18:50:05 EDT 2019 Your IP was updated at Mon Mar 18 18:55:07 EDT 2019 Something went wrong, please check your settings Mon Mar 18 19:00:05 EDT 2019 Your IP was updated at Mon Mar 18 19:05:10 EDT 2019 Something went wrong, please check your settings Mon Mar 18 19:10:05 EDT 2019 Your IP was updated at Mon Mar 18 19:15:07 EDT 2019 Something went wrong, please check your settings Mon Mar 18 19:20:06 EDT 2019 Your IP was updated at Mon Mar 18 19:25:04 EDT 2019 Your IP was updated at Mon Mar 18 19:30:01 EDT 2019 Your IP was updated at Mon Mar 18 19:35:05 EDT 2019 Your IP was updated at Mon Mar 18 19:40:05 EDT 2019 Your IP was updated at Mon Mar 18 19:45:09 EDT 2019 Your IP was updated at Mon Mar 18 19:50:06 EDT 2019 Your IP was updated at Mon Mar 18 19:55:07 EDT 2019 Your IP was updated at Mon Mar 18 20:00:07 EDT 2019 Your IP was updated at Mon Mar 18 20:05:05 EDT 2019 Your IP was updated at Mon Mar 18 20:10:08 EDT 2019 Your IP was updated at Mon Mar 18 20:15:05 EDT 2019 Something went wrong, please check your settings Mon Mar 18 20:20:05 EDT 2019 No idea why it's doing that. But if it is updating every so often, it should be fine. Quote Link to comment
fachizel90 Posted May 5, 2019 Share Posted May 5, 2019 Hi is it possible to use multiple tokens in the config file? If I wanted to use more than 5 subdomains can i register on a different email address and add the other token in the config? Quote Link to comment
aptalca Posted May 5, 2019 Share Posted May 5, 2019 (edited) 4 hours ago, fachizel90 said: Hi is it possible to use multiple tokens in the config file? If I wanted to use more than 5 subdomains can i register on a different email address and add the other token in the config? No. But you can create a second container with a different name and set that up with the other duckdns account. But why do you need that many if they all point to the same IP? Edited May 5, 2019 by aptalca Quote Link to comment
fachizel90 Posted May 5, 2019 Share Posted May 5, 2019 1 minute ago, aptalca said: No. But you can create a second container with a different name and set that up with the other duckdns account. But why do you need that many if they all point to the same IP? Thanks that should work just experimenting with several things. Quote Link to comment
Cessquill Posted May 7, 2019 Share Posted May 7, 2019 On 5/5/2019 at 7:51 PM, fachizel90 said: Thanks that should work just experimenting with several things. Just in case you weren't aware - you can have multiple sub-sub domains all hanging off one duckdns account, so plex.myname.duckdns.org, web.myname.duckdns.org, tautulli.myname.duckdns.org, ombi.myname.duckdns.org, etc. are all possible straight out the box. Might be of use, depending on what you're playing with. Quote Link to comment
pervin_1 Posted June 9, 2019 Share Posted June 9, 2019 Anybody have any idea why DuckDNS docker works 99% of times, it always succeeds updating my IP address, but when my internet goes down ( IP change overnight ), it fails to update my address with the usual message something went wrong please check your settings. The only to fix it is to restart the docker; then it works again. I would appreciate any help. Thank you in advance! Quote Link to comment
Recommended Posts
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.