I have update docker command adding ip addresses to the port mapping for tcp and udp protocols. However I am still getting the QUIC Misconfigured message.
So perhaps indeed something with an older processor, although I repeat that until a month or so ago it worked fine.
yeah, I know. We updated QUIC dependencies from the upstream.
HI @Alexey,
Unfortunately providing the address in the port mapping didn’t help.
I would like to say again, that I am running the node on several synology NASes. I am facing this problem only on the two where there NIC adapters are more than one. The default Gateway is on the one from where I want to have the communication, but I am not sure why is it confused.
Any further ideas of how that could be solved?
As it was already discussed 18 times, the bug is likely in network libraries storagenode is using. It can be solved by either downgrading the libraries (and testing the whole thing again), reaching out to their maintainers and figuring out the problem, having them fix it, upgrading libraries and testing the whole thing again. It may be fixed in the future libraries without any pressure from storj as well.
Storj drags their feet on it because it is a very low priority – nobody uses QUIC. There is/was very little to none traffic.
As a node operator you shall ignore it. There is nothing to solve. Node works just fine.
Please let’s close this thread, and all future threads about QUIC Misconfigured, until the already submitted bugs are closed. Beating this dead horse just wastes everybody’s time.
Storj should consider hiding the QUIC status in the UI until this is resolved. Otherwise we’ll keep seeing these topics.
Okay mate. Got it.
Thanks a lot and apologies…
Unfortunately @arrogantrabbit is right, this issue has a low priority:
Single Node - 16GB on Synology (apologies for the delay)
After upgrading to version 1.92.1 my node is misconfigured. TCP fastopen works.
Qnap with Realtek RTD1296 4-core 1,4GHz
Hello Roberto, it’s the same with me. After the update to the new version 1.92.1, one node is “misconfigured”. The other 2 with version 1.91.2 have the status “OK”.
Qnap “arm32”
Container station
Version 3.0.5.623 (2023/08/30)
Assuming you are running this in Docker on Syno NAS.
restart: unless-stopped
The problem happens, in my experience, when the container starts before the NAS has finished all it’s own network negotiation. Following the above I no longer have the misconfiguration QUIC error.
Thanks for trying, still no luck here… Running Synology DS718+ 2x4TB, all ports are open, I’ve restarted the NAS and Router, deleted the container and restarted it, and still nothing. 
Node has been running flawlessly for months until I noticed the “Misconfigured” today. From what I can tell from the above posts, this is nothing to worry about?
Yes, ignore it. But out of sheer curiosity you can check if this helps.
To follow the suggestion from @arrogantrabbit for the docker node you may try to specify the local IP in the port-mapping option (-p), i.e.
-p 192.168.10.11:28967:28967/tcp \
-p 192.168.10.11:28967:28967/udp \
where 192.168.10.11 is the local IP of your Synology.
Hello Alexey, hello Team, there is nothing new for me.
I added the IP in front of the port for the Qnap and the node. But this didn’t help either. It remains. QUIC: Misconfigured
The other two nodes from the same Qnap continue to run with the older version (1.91.2) with the status Quic: ok.
I also tried the port scanner again. This shows all three ports are open.
If anyone else has any suggestions, I’ll move the error to the new version 1.92.1
Is version 1.92.1 currently being rolled out or has distribution been stopped?
If your node is online, that’s enough. QUIC is an additional protocol, if your node doesn’t support it - not a big deal (yet).
they will be updated in time
You always can check that on https://version.storj.io/
The only question is that the Quic ability was lost in the last update. Can that be explained? Because the hardware is the same for all nodes. What I also want to say is that before the update Quic worked.
We updated the support of QUIC from the upstream. And seems it’s more strict than before.
Just realised that one of my nodes also have QUIC misconfigured. It’s running 1.92.1. The other nodes are on 1.92.2 and all of them have QUIC working. I guess I just wait for the auto-update to take me away from 1.92.1 and QUIC should be working again?
Maybe yes, maybe not. Depends somehow on architecture and OS.
ARM-based devices may have this problem.
You may also just refresh the dashboard, QUIC is checked on each check-in (every hour by default), it could be fixed itself.