QUIC Ok then change to Misconfigured after a few minutes

[Alexey]

You can try to use this:

Binding to a specific interface to stabilize QUIC connectivity

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…

[Workaround] QUIC misconfigured

Continuing the discussion from Binding to a specific interface to stabilize QUIC connectivity: Evidently, two things need to be true for QUIC to work: As indicated in the linked post, the interface address must be explicitly included in the server.address; e.g.: server.address: 10.0.17.120:28967 The port advertised in contact.external-address and forwarded to the node must be the same. I.e. if you advertise port 28967 in contact.external-address: icecream.example.com:28967 you shall als…

QUIC is checked on each check-in on the satellites, it’s every hour by default.