Hi everyone, since a couple of days my nodes cannot connect through QUIC but I did not change anything network-related since months. I only updated truenas scale to the latest version and now my nodes show they are misconfigured, any idea?
Thanks
lol. Those two statements are contradictory. You have changed the whole network stack!
You shall ignore misconfigured quic
Or you may attempt to fix it as described at linked thread if red text bothers you.
1 Like
Not really, I don`t understand why updating OS would influence my nodes that are hosted inside docker containers. Port-forwarding is set as it used to be since months, truenas let pass UDP and TDP without influencing the traffic.
Anyway I see a drop in the download section so apparently it is affecting me:
For now I’ll just ignore the red text and keeping the nodes up
Thanks @arrogantrabbit
Network stack lives in the kernel. Docker containers are os-level virtualization. They talk to the host’s kernel, just like any other process would. When you updated TrueNAS, you have replaced the entire network stack node interacts with.
It has nothing to do with port forwarding. You can actually read the linked thread if you want to learn more, there is no reason to repeat everything here again.
You don’t see drop on download section. You see the idiotic way graphs are rendered. It was also discussed before. New data not being stored - #12 by arrogantrabbit
Next, even if you did see drop in traffic, it would have been classic case of correlation without causation. If you read the linked post, you’d known that less than 1% of traffic use quic.
And lastly, in the very same linked post there are instructions on how to fix it, with a quite a high success rate:
Sometimes I feel like an idiot searching on behalf of random people (something they should have done before creating a new topic in the first place), and posting them links only to be entirely disregarded as evidenced by their follow up comments.
Good plan.
1 Like
Hello @outright1534,
Welcome to the forum!
Please also replace the DuckDNS/ASUS to No-IP: Search results for 'quic & duckdns order:latest' - Storj Community Forum (official)
1 Like
Same here (20 char).
Cheers.
Hmmm, since I posted the above, my other node, not running on TrueNAS, is now reporting QUIC Misconfigured as well.
Looking in the logs, both have the following message (different host names), from the same satellite, about 20 minutes apart:
2025-04-30T16:09:12-07:00 WARN contact:service Your node is still considered to be online but encountered an error. {"Process": "storagenode", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: lookup storj.xxxxxxxx.net on 10.91.0.10:53: server misbehaving"}
And no, I’m not using DuckDNS.
Cheers.
And the analysis, root cause, and recommended action would be exactly the same, regardless of how many times or different people ask.
1 Like
Duckdns would affect your node address resolution, not protocol specific shenanigans.