My node appears offline on the dashboard. I have checked the following:
Port 28967 is open. DDNS is working. (Checked on https://portchecker.co/ with server address of the node.)
New connections can be established, checked in docker logs storagenode
No errors found in logs, at least for the last 200 lines.
What could be happening?
Full browser refresh or restart make any difference?
No, I’ve tried hard refresh and used another browser too.
Using current external ip directly instead of ddns might be worth a try. Just to make sure this is not ddns related… 
The fact that your port is working as seen by the external port checker points squarely at DDNS issues being the cause of your node bing offline.
You cannot claim that DDNS is working because the evidence directly contradicts the statement: the fact that it resolved correctly your address once from some specific IPs does not prove that it “is working”. The fact it does not resolve from any one address proves that it does not.
Check your node log, you will find the reason why it is offline there. Restart the node, and look for satellite pings at start.
Which DDNS provider are you using specifically?
I used my domain (address for node) as well as my public IP while checking the port. They both show that the port is open.
As I mentioned before, the node log didn’t provide any useful information. Here are the last 500 lines of it:
Yes, I have tried both the IP and my domain. They both show that port 28967 is open.
Does not rule out DDNS. DDNS is comprised of multiple servers in one or more clusters, that need to replicate and keep data in sync, and sometimes they do not. The fact that your DDNS resolved correct from your location means nothing.
Known bad DDNS providers are duck dns, Asus DNS, whatever the heck Synology offers, and many more.
I’ll ask again: Which DDNS provider are you using? And what updater, and what ip detection endpoint? Show logs from your updater as well.
Not useful. I’ll ask again: show first pings from satellite and handshake following node restart
I am using dynDNS’s custom configuration: Configuring your dynDNS Client — deSEC DNS API documentation
I have a script running on my node that updates the records.
The log is too big for me to find the specific details you asked. Can you provide some keywords so I can locate them in the log?
This is looking like a perfectly working node. So dashboard might be wrong about online status. Maybe a time sync or time zone problem?
Yes, my PC had the wrong timezone because it has two operationg systems. But after correcting it and hard refreshing the dashboard, the node still appeared offline.
You are using “dedyn.io”, whatever the heck is this. Assume it’s broken. Switch to a DDNS service that has some reputation. NoIP seems to work fine according to reports, cloudflare is fine too.
It’ also important to use correct endpoint for ip detection – the cloudflare endpoint everyone seems to be using has been broken for a while. Use somethign else, ike ifconfig.me, or whatever default your updater supports.
Check the logs of that script, and confirm that last day worth of updates were correct.
I don’t remember on the top of my head – but it’s very first few messages storage node prints upon boot.
perfectly working node would have uploads and downloads from at least three satellites. This one has downloads only from two. This points strongly to DDNS issues.
try your external ip:port in brouser, it shold show you simple web page. if no then you ip is wrong or port forward problem. if ok then do the same with ddns link:port, shold show the same if not then problem in ddns.
This is possible.
You need to also restart node, and ensure the container that your node is running in has correct time zone.
Check if this timestamp is within last two hours and matches your local time:
curl -sL http://<your.node.local.ip>:14002/api/sno | jq '.lastPinged'
Please search for “ping satellite failed” error in your logs, there will be a reason.
You can also check your http://DDNS:port on the smartphone using the mobile internet (not WiFi), it should show the node’s status page.
Since they require nameservers pointing to them, its not possible for me to use them. My domain was created on dedyn.io and only they can provide DDNS service. I cannot change nameservers for my domain on their platform.
The startup log is here: 2026-04-20 03:25:21,736 WARN killing 'storagenode' (67) with SIGKILL2026-04-20 - Pastebin.com
Use noip for nodes. See if this alone is enough to fix the issue. I would not trust little local provider to operate correctly globally. If you google carefully you’ll find reports of their service reporting stale IPs in the past. Just don’t waste time with them, use established platform. (I would move all domains to cloudflare eventually, the only stable provider in my experience. Even google domains sucked – no wonder they sold the business to squarespace). it’s hard to do right and maintain correctly. Many have tried, most have failed.
Need more lines, until and including node registering with satellites.
Remaining open questions:
Problem solved. Nothing wrong with node, checked all 4 satellites, all reported last contact of 0 min ago. “Status” went back “Online” again. The cause was simply mismatched timezone on my personal computer (Not the host running the node). Thank you all for your help.