No network changes over the past 6 months and everything has run reasonably well till now. Occasionally I’d find the STORJ docker stopped. I’m not sure what that’s about but it only happens about once per month.
This QUIC misconfig issue has been happening since about Monday. It randomly goes down and then restarting or start/stopping doesn’t seem to help. I need to leave it off for a few minutes before starting and it usually resolves the problem.
Nothing has changed over the past few months regarding network infrastructure. If it were filtering UDP I’d assume it’d be consistently down and not working for the first 5 minutes and then down after that.
Perhaps your router has several similar features as pointed by @LordWigo or even your ISP have something similar.
I noticed, that some ISPs started to implement “smart” protection for their customers, blocking any income traffic.
Here’s my issue with that - if I restart the storj docker instance it works for some time before switching to ‘misconfigured’. If a firewall rule had blocked UDP it shouldn’t be working at all, shouldn’t it?
yes, but with some kind of throttle grey-list - it’s likely be expected.
So I would check these options on the router or firewall or antivirus.
By the way, there is no point to check the node’s activity - all data is encrypted anyway and your node stores only 1/80 piece of the segment (!) of the file. Just waste of CPU cycles on checking its activity.