Ap1.storj.io Suspension Issues since 11/14/2025

Node Operators troubleshooting
,
1

Hey Friends. Hoping you can help me with a conundrum I have been having since my node updated to 1.141.2. I am suspended on ap1.storj.io with a Suspension of 30.76%, Audit of 100% and Online of 99.58%. No changes on my side, except it looks like my node updated on 11/14/25 to v1.141.2. I see in my firewall logs that around that time it started blocking traffic from Bulgaria and Russia, as well as a few attempts from China. The traffic seems innocent enough; mostly from AWS ec2 instances and from Vendetta LLC (which appears to be a large hosting platform/colo), but I automatically block traffic from these countries. Could this be my problem, or just a coincidence that these logs line up with the timing of my ap1.storj.io issues?

Thanks in advance!

2

Hello @cosmo,
Welcome back!

It will lead to less data.
Please, check your logs for audit errors:

3

Thanks, Alexey. It has been a while, but that is because my node has just been humming along by itself :slight_smile:

2025-11-15T20:44:05-08:00	ERROR	piecestore	download failed	{"Piece ID": 
"NQ3ZKG6SKPFFCN5Y7ANAVDEERPH6WPRXTBQCA55KASDBZ7W6YVAQ", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": 
"GET_REPAIR", "Offset": 0, "Size": 2319360, "Remote Address": "95.216.145.105:37622", "error": "write tcp 
myInternalIP:28967->95.216.145.105:37622: wsasend: An existing connection was forcibly closed by the remote host.", "errorVerbose": 
"write tcp myInternalIP:28967->95.216.145.105:37622: wsasend: An existing connection was forcibly closed by the remote host.\n\tstorj.io
/drpc/drpcstream.(*Stream).rawFlushLocked:428\n\tstorj.io/drpc/drpcstream.(*Stream).MsgSend:489\n\tstorj.io/common/pb.(*drpcPiecestore_Do
wnloadStream).Send:416\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).sendData.func1:879\n\tstorj.io/storj/storagenode/piecestore.w
ithTimeout[...]:1149\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).sendData:877\n\tstorj.io/storj/storagenode/piecestore.(*Endpoin
t).Download.func7:772\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93"}

I see this traffic in my firewall logs as well (95.216.145.105). It shows as Finland and allowed. I’ll keep digging!

4

You are breaking Node Operator Terms and Conditions by doing so.

3 Likes
5

Wouldn’t want that! :slight_smile:

2 Likes
6

Question..

What / how is the block taking place in your firewall? Inspection and dynamic blocking based on feed i would suspect.. ?

Generally I do full exception on such filters for node traffic.

7

Checking in this morning, node is unsuspended and showing Suspension 100%, Audit 100%, Online 99.48% for ap1.storj.io.

My audit logs show two piecestore download failed messages in 22 hours, so I think I am going to chalk this one up to the satellite being wonky for a bit. Note also that I received 11 node suspended/unsuspended emails within 5 hours. :man_shrugging:

Thanks all for the tips/advice!

8

It’s your node was wonky by throwing the unknown errors on an audit requests :slight_smile:
The provided excerpt is an interruption of the network connection seems made by your external firewall on the repair request. This may lead to suspension, because the suspension score is dropping when the node returns an unknown errors on audit or repair request.
“file not found”, a corrupted piece, “I/o error” or three timeouts in a row on the same piece - all known and will affect the audit score instead.

So, I guess your firewall is to blame.