Node status went offline with no

[khvnhtung]

![Screen Shot 2020-04-19 at 21.33.23|690x413](upload://Dm

mn46VXQzUp6QZO9poLevqRNx.png)
Is this because my storage is full? I’ve attempted twice to reboot the device but the status still remained offline. Should I delete the storagenode and make a new one?
Here’s the logs if you need more info.
https://pastebin.com/KJHqxE7b

[Alexey]

You should not delete the node. But you should fix the OFFLINE issue:

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

[khvnhtung]

I checked and it says the port is still open. All the other instructions in the page, I’ve read and follow but I don’t see anything wrong with my setup.

[direktorn]

so you haven’t even read the log?

[BrightSilence]

Your node is seeing traffic according to the logs you’re posting. Nothing seems to be wrong. Please try refreshing the dashboard page with CTRL+F5.

[khvnhtung]

I don’t find any errors in it. It’s clean as far as my experiences tell but the information in the dashboard is contradicting each other.

[khvnhtung]

Thanks for the advice, I tried accessing it in private tabs to avoid web caches and they still reported as being Offline.

[Alexey]

Please, try to press Ctrl-F5. IE will not work either. The Brave too.

[khvnhtung]

I tried Ctrl + F5 and it doesn’t work either.

[Alexey]

Ok, then let’s check together each step.

Node stopped responding overnight. Still shows OFFLINE after restart

ok, let check it together. WAN IP on the main page of the router. Please, compare it with IP there: https://www.yougetsignal.com/tools/open-ports/ , they should match Local IP in the port forwarding rule, it should be the same as IP of your PC with docker nslookup your.ddns.address 8.8.8.8 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 y…

[Alexey]

If you have another node, make sure that you didn’t confuse ports.
Dashboard is working in Chrome, Firefox and Edge. All other could not work. The Brave and IE will not work.
Your logs shows that your node has been working until April 17, but now it’s offline. This is let me thinking, that either your public IP has changed or the local IP of your PC has changed.

[John.A]

All ip and port changes and numbers can get confusing from time to time.
Next node im going to do ill have to start write down everything and so its gets bullet proof

[khvnhtung]

Dang it, I have finally found the culprit. Just like you said it was due to the dynamic DNS not updating, I setup too many dynamic DNS that I messed up and checked the wrong one. Now that I have figured out, I rerun the Dynamic DNS setup to update the pi’s ip address. It’s working now, thank you. Totally my bad.