you should start by verifying that your ddns has the correct ip address registered…
the error just seems to say that the node is offline… so maybe port forwarding in the router that was lost… and i would ofc try to turn stuff off and back on again
most likely internet connection, firewall…
when starting to troubleshoot stuff like this i usually start by looking at the easiest to solve issues first and ask myself … what changed… it’s rare that stuff just stops working for no reason…
stuff is always changing… could be something as simple as your storagenode gets it’s LAN IP address from a DHCP server in your router and then somebody else on the network assigned a static IP address to something and the DHCP server moved the storagenode to a new IP address to keep the network working.
check your internet, connection and port routing to the storagenode.
your node may have updated from 1.17.4 to 1.18.1 during the night… maybe watchtower isn’t configured correctly … if you are using docker…
as a temporary patch you can use the current ip address in the docker run command, which will get you up and running until you solve the ddns issue.
i haven’t really setup or done much with the ddns services so ain’t really much help in that regard… you should have a program or an account at a website which would control your ddns address… tho it can also be controlled by your router… the router as controlling the ddns is the recommended solution…
most likely if you access your ddns account you can most likely see whats wrong.
some ddns services needs one to renew the address and such… i duno
atleast now you know what to hit to fix it
good luck
ddns services are plentiful… find one you like make an account, download their software or setup your router to update them with your dynamic online ip address
should be clearly explained at whatever ddns you choose… i would look at the forum for some recommendation, there may be a number of bad seeds or annoying ddns providers you might want to avoid…
ofc you might also easily be able to fix the current one… when you figure out what went wrong with it.
for docker to start the storagenode a command structure like:
docker run … insanely long extensive command is run which has all your ip address, port mappings and storage folder mounts and such
its described on the link.
you should have it stored somewhere… either in watchtower or for ease of copy paste … remember to do a
docker stop storagenode
docker rm storagenode
else the docker run … command won’t work
its sorted… just renamed the broken config in Docker and then created a new container with new DNS details. Back online now… many thanks for the help !!
happy to help
remember the ddns service needs to be updated with your ip address, else when your ipaddress changes or whatever it will stop working because it has an old address.
this is either done by the internet router which is a good idea, because it helps reduce latency when the ip is changed…
else a piece of software will need to run on the storagenode host which keeps a track of your online ip and updates the ddns service with the new ip address when it changes…
this must be setup correctly else this will be a very temporary fix…
but the command isn’t anywhere… normally you just write it, so it will just reuse the last used run command for active containers?
i suppose that would make good sense because then it would be easy to start, stop and upgrade even if jumping around from watchtower to manual or vice versa
