All of my node dashboards on one device (running docker rootless) are showing “QUIC: Misconfigured”. Using Pingdom , I see storj RPC ping succeed: started from: St.Petersburg, Russia TCP: dialed node in 703ms TCP: pinged node in 167ms TCP: total: 870ms QUIC: dialed node in 700ms QUIC: pinged node i…

Just to follow up on what the cause of my issue actually was: My AAAA record for my storj subdomain had become out of date (prefix from ISP changed) but my A record was still correct. When I fixed this all my storj nodes under this subdomain are showing “QUICK OK” on the dashboard again. When I was…

[image] QUIC misconfiguration in v1.86.1 troubleshooting 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 das…

Thanks, I assumed that might not be it since it mentions FreeBSD (I’m running Linux) and it was opened three years ago (mine just regressed recently). But if the whole feature is effectively deprecated I can happily ignore the warnings.

This sounds like your configuration is changed recently, because there was no changes related to QUIC for a long time. You may try to use a workaround: [image] Binding to a specific interface to stabilize QUIC connectivity Node Operators TLDR: if you are havin…

Trying to set server.address in config to any of hostname -i’s output within the image, or 0.0.0.0, or my router IP (can’t bind), or my server IP (can’t bind) all don’t seem to work. Seems like things are complicated a bit since it’s running in Docker. I’ll just keep it the way it was with QUIC misc…

In the case of docker, you may try to bind the listening port to the one of your cards, connected to the internet directly or via router. QUIC Misconfigured is often related to setups where you have more than a one network interface, and listening at 0.0.0.0 on the host could cause QUIC not working. …

I tried passing in the host network IP explicitly to docker’s port passthrough, and that doesn’t resolve the “misconfigured” reporting in the dashboard (but still shows success with Pingdom ). It does break my IPv6 connection though which was working properly. --network host fails due to insufficien…

If the Misconfigured flag in the dashboard bothers you – you need to: ensure you have only one adapter and bind to a specific IP avoid docker (run the storagenode directly, or with podman if you have to). ensure port number does not change through DNAT and various forwards. If this still does no…

focus on ensuring TFO works It does, including within the docker containers on all of my nodes across multiple servers. The flag is updated once an hour, and the issue is random. it can work for some packets and fail for others. I can ignore it as a low priority issue, just the explanation of…

[image] Flobe: it being flaky in my dashboard (always “misconfigured”) These use different paths probably. Check these threads: QUIC misconfiguration in v1.86.1 - #9 by arrogantrabbit Binding to a specific interface to stabilize QUIC connectivity Setup node through a VPN - #6 by arrogantrab…

The Storj network supports IPv6, but IPv4 is required, so dual stack is best.

QUIC Misconfigured despite pingdom showing QUIC working

Node Operators troubleshooting

Alexey May 7, 2026, 3:38am 4

This sounds like your configuration is changed recently, because there was no changes related to QUIC for a long time.
You may try to use a workaround: