Yes, you are right the autocorrection is a wonderful invention, always may make your day
Hi ,
Is vetted status in API ?
Thanks
Yes, it can be found in /api/sno endpoint.
vettedAt "2021-02-13T07:11:17.67771Z"
To my pleasant surprise the Quic is back up and running from version 1.31.7 on 64-bit ARM, Realtek RTD1296 4-core 1.4GHz
This is the situation as far as vetted is concerned
Eu seems normal, I live in Rome
Is it only going to show in US date format ? - for UI might be good to be User friendly date, API to be DB ISO date
Oh nice find - good of the developers if they took that into account
I was running node on windows, on any version 1.131 and found frequent misconfigs on QUIC, so I finally rolled back to version 1.130.8.
Hello @minerone,
Welcome to the forum!
You may try this workaround:
Here is another one.
[EDIT]
Found two more nodes,
I still have several nodes not updated to v1.131.7 We will see if more unvetted nodes show up.
Please add to the GitHub issue and subscribe to it
I’ve tried it and double checked NAT forwarding, firewalls, and so on, but QUIC is still misconfigured. Version 1.130.8 is still the best for me.
I would update to the latest version and ignore quic
Is there any impact if we ignore the quick and what will be the long-term effects?
Did you read this post linked above? Release preparation v1.131 - #15 by arrogantrabbit
Virtually no customers are using quic
However, every single customer attempts TFO. Therefore I would channel the efforts to verifying that TFO is working instead, It will be much more impactful. QUIC is only interesting to Google, as evidence by it incessant breakages in the upstream library.
If I was storj I would remove QUIC from dashboard and add TFO status instead.
How to check if TFO is working: Please enable TCP fastopen on your storage nodes - #184 by arrogantrabbit
I agree with you, if QUIC often has problems it should be taken out of the dashboard because it is very annoying.