Formerly working node, broken after reboot

You could try adding some other service to your vm besides storj and ssh…maybe a web server or database or even an nc
Then test to see if you can connect to these from various

1 Like

Is it possible that you have changed the default port in the server.address option of the config.yaml file?

Screenshot 2024-08-08 at 22.07.09
Dont recall editing this but this is what I got. Does it need a hostname/IP address on the line or just the port?

this syntax is equivalent to

server.address: 0.0.0.0:28967

So, it should listen on all interfaces and the port 28967.

Please try to change the external port to 28968 for example and update docker run command with -p 28968:28967/tcp -p 28968:28967/udp -e ADDRESS=external.address.tld:28968 and update your firewall rules and the router’s rules to forward a new port.
Also, please check your No-IP domain:

nslookup external.address.tld 8.8.8.8

It should return the WAN IP and it should match the address on yourgetsignal.


docker logs for the node and nslookup

external.address.tld is a placeholder for your external address. Please use your own, the real one.

Sorry bout that, thanks for being patient. Updated the post.

Does the returned address match the WAN IP and the IP on yougetsignal?
“Rate limited” meaning that your node was unavailable and the satellite is throttle the node, because it’s trying to check-in with unavailable external address and port.

You may also try to open http://192.168.1.214:28967 in your browser, or use your external address instead of a local one, it should open a page with the node’s state.

Not sure what you mean by this. Assuming your asking about the nslookup command, I linked images for the output of my noIP host name and WAN IP.

There is an address 0.0.0.0 which is wrong. Seems your DDNS client doesn’t work and didn’t update your DDNS domain.
There should be you WAN IP and it should match the address on the yougetsignal site.

http://192.168.1.214:28967 and http://192.168.1.214:28968 both giving “192.168.1.214 refused to connect.”

Then either the node is not running, or local IP is different or something blocking the port.


Screenshot 2024-08-08 at 23.24.54


Node seems to be up, pretty sure something is blocking the port as you suggest.

Routers can get stuck… try re-booting it.
1/4 of cent

1 Like

Please, check that it’s resolved to the specified address:

nslookup sentinelnet.ddns.net 8.8.8.8

No real resolution in this for those reading the thread facing similar issues. Migrated the node to a new host (synology) and works fine. Problem most likely was something with the former host (porxmox). Used this guide for synology. My docker run commands for multinodes on Synology NAS

2 Likes