Errors on log - Quic Misconfig

Node Operators troubleshooting
,
1

So i got the quic Misconfig error again, this time i was able to see something in the log
“PUT_REPAIR”, “Size”: 2319360, “Remote Address”: “5.161.44.25:41402”}
2023-08-18T17:52:39-04:00 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Error”: “contact:
failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-08-18T17:52:39-04:00 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “Error”: “contact:
failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-08-18T17:52:39-04:00 WARN contact:service Your node is still considered to be online but encountered an error. {“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”}
2023-08-18T17:52:39-04:00 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Error”: “contact:
failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-08-18T17:52:39-04:00 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “Error”: “contact:
failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-08-18T17:52:40-04:00 WARN contact:service Your node is still considered to be online but encountered an error. {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “Error”: “contact:
failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity”}
2023-08-18T17:54:18-04:00 INFO piecestore upload started {“Piece ID”: “7Y3KNFEO4F3QNEKBZVSZY256QEQZ4VUDPPUD2XBDRCIW5TC6NJWA”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Action”:
“PUT”, “Available Space”: 799545520640, “Remote Address”: “5.161.128.79:28166”}
2023-08-18T17:54:19-04:00 INFO piecestore uploaded

what to do to fix ?

2

Create a port forwarding rule for UDP 28967 to your Windows PC on your router and allow UDP 28967 on your Windows Firewall, then restart the node either from the Services applet or from the elevated PowerShell:

Restart-Service storagenode

See Step 4. Configure QUIC - Storj Node Operator Docs

3

They both were already set - weird it i refreshed it an hour later it was fixed.

4

Noting weird. It updates the online and QUIC statuses on the each check-in on the satellites (every hour by default), so the restart is actually not needed, but you may force to update it this way right away to do not wait for a hour.

1 Like