QUIC misconfiguration in v1.86.1

Yes, it worked after I specified the server address to include the local adapter IP explicitly, as described above.

# public address to listen on
#server.address: :28967
server.address: 10.0.70.2:28967

It worked up until 2 hours ago, when they updated to 1.90.2.

Now it does not work regardless of whether the address is specified. Apparently, it’s now more “broken” than it was before.

Ok, I see. I’ll poke around and see if there is any progress on those bug reports, which might help.

2 Likes

I have this error in my log too. The system updated overnight to 1.90.2, was on 1.89.2 yesterday (I update automatically). Checked config.yaml and my IP and port are still there.
Restarting the freebsd jail in my case, didn’t help neither.
I do think I had ingress after the error has occurred as I am at 16Gb so far today and the error started at 00:16 hours.
Any thoughts?

My freebsd jails have also this error since they upgraded from 1.89 to 1.90.

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.

1 Like

SYNOLOGY - Docker Container also issue only node with latest version: