You can ignore misconfigured quic:
There hasn’t been any progress on those QUIC bugs. It’s considered low priority because apparently uplinks quite rarely use QUIC in production. I suppose we’re recommending not to worry about what the dashboard says about your QUIC status for now.
You can attempt to fix misconfigured quic:
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…
I have also recently noticed that it’s more stable if the port number remains the same throughout the forwards and bindings. I.e. if you decide to use port 28893, then port-forward it to 28893, and tell docker to port forward it to 28893, and tell node to listen at 28893.
1 Like