Hello community, I have multiple nodes on the one SYNOLOGY NAS. Few days ago one node started flashing as “Misconfigured”: [image] I have tried restart docker container - fixed for few hours but then received email that my node went offline. Tried to delete and recreate - the same. Fixed but a…

I believe that QUIC may not work on freeBSD, and also on Linux for ARM CPUs. On Linux x86-64 it is working fine.

In my case: Old Synology NAS Showing QUIC Misconfigured 1 node configured DS1812+ “OS”: DSM 6.2 Kernel: Linux version 3.10.105 (root@build6) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #25556 SMP Tue Mar 21 22:22:21 CST 2023 CPU: Intel(R) Atom™ D2700 Newer Synology NAS Not…

So, only the old one is affected? :thinking:

That is correct. Only difference (other than HW obviously) is that I am forwarding traffic related to the DS1812+, reporting misconfiguration one, to port 28968 to make the distinction between the 2 nodes I have. But that has worked fine for past 3 years or so.

yes, I think we have something broken after update from the upstream. However, it’s not so important now [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 qui…

Hi Alexey, [image] And as usually on my Windows 10 machine on the same network behind same router: [image] Regards Wigo

Hello, I’m running some nodes from April 2023, but I am facing a problem which occurs from time to time and I can’t solve it. I have a Synology NAS in a datacenter, which has 4 LAN ports. The first one has a local management IP. The next two are bonded and configured with a local IP. The last one …

I see, then perhaps it is all Synology’es with weaker processors, since [image] therealmko: Newer Synology NAS Not showing any messages 1 node configured DS 1019+ “OS”: DSM 7.2 Kernel: Linux version 4.4.302+ (root@build7) (gcc version 12.2.0 (GCC) ) #64570 SMP Thu Jul 20 00:07:29 CST 2023 CPU…

QUIC Misconfigured after upgrade to v1.90.2

Node Operators troubleshooting

Alexey November 10, 2023, 8:31am 54

yes, I think we have something broken after update from the upstream.
However, it’s not so important now