Contact:service Your node is still considered to be online but encountered an error

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?

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

Left it running as is “misconfigured” it shows in dashboard , I’ll check anymore errors and report back if anything seems affected

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: