i had to delete and re download my docker image to force it to update because it was constantly restarting due to the disk space bug however i have a new issue! my last contact was 17753589h 2m ago! basically day 0 logs all say unable to ping the servers not entirely sure why as it was all working fine till the 1.152.5 update 
Check logs. Find the failure. Triage it. Fix it.
Nobody can guess what is broken in your end without evidence.
The answer is within 100 words of the word ping in the logs. Keep reading.
The log is basically this repeated so the remote server cannot ping my node is what it means? just rechecked my router settings and they seem correct and my ddns is correct shows my ip address in the logs plus i can connect to some of my other services via it still. so some firewall in docker thats changed 
docker is certainly not my strong point its still a big learning curve.
2026-04-27T22:06:10Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “satellite_id”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “attempts”: 11, “error”: “ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp MYIP:28967: connect: connection refused”, “errorVerbose”: “ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp MYIP:28967: connect: connection refused\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:232\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:169\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:163\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”}
It says, the connection from the server to IP MYIP at port 28967 was refused.
- Check that this is your IP
- check that its’ your public IP
- check that firewall allows connections to that port
- check that DNAT rules on your router is correct.
- check that node listen interface is correct
- check that port nodes is listening on is the same as in the DNAT rule.
1 Like
very odd my config file had disappeared no idea why but looking back through the log it complained of an error on line 22 of the config but restarted and it was like this it must have corrupted it and deleted it if thats even possible. Re created the the config file and working fine!
Stop using docker. Has been discussed many rimes. 90% of issues discusssed on this forum are docker issues. Drop it. It’s garbage. I don’t understand why people choose technical solution based on what is marketed better.
Yes i stopped then removed the container and also deleted the image then in the end had to delete the bin file in my storage location because everytime it kept on v1.152.5 with the hdd size bug constantly restarting.
I’m not that good at using linux so usually end up having to follow instructions for most things and it appears that the only instructions are for installing it in docker. Seems most things seem to point you to use docker but its not the most user friendly thing to use especially with dyslexia the amount of times i have to re type commands because i spelt it wrong. 
If the config file was corrupted, then a node didn’t read it and used defaults also values of provided environment variables.
The address should be provided in the environment variable ADDRESS with a -e ADDRESS=MYIP:28967 option of your docker run command, not in a config file.