ItsHass
November 25, 2025, 4:30pm
1
2025-11-25T16:27:52Z WARN contact:service Your node is still considered to be online but encountered an error. {"Process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
a new one for me… - any ideas?
Roxor
November 25, 2025, 7:20pm
2
QUIC… is one of those nice-to-have things… but it’s not a critical feature. As long as I’m Status = Online… I don’t care if I’m not QUIC = OK.
1 Like
ItsHass
November 25, 2025, 7:34pm
3
Left it running as is “misconfigured” it shows in dashboard , I’ll check anymore errors and report back if anything seems affected
Alexey
November 26, 2025, 6:48am
4
You may also check, that you forwarded the UDP port, see
If all configured properly, then perhaps you have more than a one network interface on this device, thus this may help:
TLDR: if you are having flaky QUIC connectivity, go to the config file, and add an explicit interface address to the line server address line. e.g.: server.address: 10.0.17.120:28967
Backstory: I noticed that this morning, at 7:30PM PST according to the logs all three my nodes on three separate machines, in three separate states, connected in two different ways (one directly, and the other two over VPS) all lost ability to see QUICK. It was rather bizarre, and I don’t know why that happened. Th…