I’m not too sure what happened, but my node stopped running overnight and is now showing “last contact: OFFLINE”. I’ve checked the port forwarding and the dynamic DNS and they are all set up correctly with no IP changes. I’m running node version v0.17.0 as well.
I had already done these troubleshooting steps before creating the ticket except checking the /app/identity folder, however all files are there correctly.
My node was operational since the update to v0.17. I see now that watchtower has upgraded the node to v.0.19. Are there any differences with that version from .17 that could cause the node to stop working after many hours of uptime?
Local IP in the port forwarding rule, it should be the same as IP of your PC with docker
nslookup your.ddns.address 184.108.40.206 should return the same IP as p.1
Firewall. It should have an incoming rule to allow any traffic from the any source to the TCP 28967 port and your PC as a destination. If you have any outgoing rule, then you should create an outgoing rule to allow any traffic from your PC as a source and any host with any port as a destination.
Yes, i found the problem. My second router had changed it’s IP. It was showing correct this morning even when i checked it, but for some reason, I see the different number now. I’ve changed that IP in the port forwarding and now the node is online.