Your storagenode tries to connect to the satellite, which double checks if the address (reported by the storagenode) can be accessed.
This is the address which is configured on the storagenode side (in case of docker with ADDRESS="xxx:20005"
First, I would try to access the same ip and port from any other machine. With a new enough storagenode it should response with a generic json message (you can try from the browser: http:// xxx.121.130.122:20005)
You may used a DNS in storagenode configuration, in that case it can be a DNS caching issue, but you can also double check if it works with dns)
If it works well from a browser, please let me know the NodeId and/or email. I tried to find the missing xxx from the IP address, but couldn’t find similar nodes in the satellite log. You can send me a private message, and I will check what satellite thinks about your node…
It doesn’t respond, but knows about it and writes it to the log? How does it know? From the satellite?
Is the router, firewall or ISP so smart that it only blocks from that one satellite? And only at times?
In view of this, how do I get data to store, and I am according to this satellite offline?
The node check-in on the satellite and while the connection to the satellite is open, it can receive scores update and feedback from the satellite about connectivity of your node with provided public connection information.
you getting data not from the satellite but from the customers (which obviously have a different IP and likely location too than the satellite). And transferring data to the customers, not to the satellite.
The only data exchanged between your node and the satellite is for bookkeeping, online checks, audits and repairs. Since your online score is not zero, sometimes your node was able to respond to audits.
You may check with these scripts when this happened and how many audits are missed:
So you need to check why packets from IPs of that satellite are blocked on your side (firewall, router, ISP).
From the cache, or it’s resolved from time to time, but unstable. This could be if the DNS provider have some issues.
Please check a count of requested and count of responded audit requests from the output of the script above.
The audit score is affected, when your node responded to the audit request and did not provide a piece for audit or it’s broken, it will grow with any successful audit.
The online score is affected, when your node did not respond on the audit request at all, it will grow if your node responded on the audit request with any result.
your node should be available for days to see a grow, the online score is calculated within rolling 30 days window, so it should went out of the period when it was offline.
of course it will not fix the problem, since the problem somewhere between your node and the satellite, but it will show how many audits were missed and when. If you used DDNS with unstable resolution (like changeip.org or other their domains), this could be a problem.
But you said
So do you still see errors like
the satellite is trying to connect your node to check connection, it’s not ICMP ping, it’s a complete dRPC request. In this case your node is not responding on this request, like if the message was dropped somewhere before arriving to the node.
With all due respect, I don’t understand what you are writing to me about
I have only one address and one port: xx.xx.xxx.122:20675
As you can see in the picture there is no problem with connectivity to five satellites, only one.
Then what is wrong with my IP and port? After all, I don’t have different IPs and ports for different satellites!
It’s not hard to guess what the Open Port Check Tool shows for the 633rd time, but if you don’t believe it:
It is on the satellite side that there are different interfaces:
Is it possible that a node sometimes responds to a drcp ping request, but not to the address the satellite expects it to?