Same issue for one of my two nodes, which got upgraded to v1.67.1. The other node shows that QUIC configured correctly, but the one which got upgraded started to show this error. No changes were made to router or node config (otherwise node which did not upgrade yet would also show same error).
I also went to RDP to server and checked if corresponding ports are opened via site, and site reports that they are opened.
Tried to restart node and now it shows QUIC as correctly configured, but judged by other replies it may report error again later.
5h in after restart of node - error did not appear again.
If after upgrading to 1.67.1 QUIC Misconfigured appears, it is enough to press the F5 key to “fix” it The Reload key inside the page does not help, but F5 solves all problems except for the wrong Current Month Earnings, and for that we will wait for a newer version…
On a NAS with Docker, I run 2 nodes on 2 disks. The watchtower is set to update both nodes. How can one be at 1.67.3 and the other at 1.66.1? Dosen’t it update the storagenode:latest image for both in the same time? I don’t know how linux works…
checked on my node today after about a week and everything was okay.
10 minutes later the QUIC changes to “misconfigured” seemingly out of nowhere. I didn’t even restart the PC. All I did after checking it was go to a few webpages and check discord.
I noticed the “uptime” and “last contact” were identical when I first checked the node. They both said “144 hours”. I do not think last contact could have been 144 hours ago because my online percentage didn’t change. I don’t know if these are unrelated issue.