Zoc

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!

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

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