New release candidate is already deployed on QA Satellite Changelog General 501755a go.mod: bump storj.io/common 3921bc6 cmd/tools/segment-verify: don’t stop segments csv processing too soon ae0b658 cmd/jobq: add GCP profiling support 7f80e40 ci: increase timeouts 20b9ee1 go.mod: bump common …

I imagine the saltellite keeps the vetting records, because it sends the audits. Maybe if an audit was missed by the node, the satellite considers it unvetted, even though the node responded to 100+ audits? Just speculating…

@Alexey create a ticket in storj repo, please. This should be scheduled during future spring plannings.

My windows nodes showing QUIC misconfigured after upgrade to v1.131. Nothing else changed from my side. :thinking:

Try the “specify binding IP explicitly” workaround. QUIC library in go seems to be utter garbage is unstable crap can benefit from improvement .

Explicit binding did not help. I wonder if it is worth to spend time on solving this issue? Is there anything using QUIC?

[image] alpharabbit: is worth to spend time on solving this issue? Nope: [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 quite rarely use QUIC in pro…

The node dashboard showed the vetted state while it's not vetted opened 08:33AM - 19 Jun 25 UTC (UTC) [image] AlexeyALeonov Bug …

All windows nodes showing QUIC OK now. I have no idea what happened, maybe storj solved the problem at satellite side.

[image] This does not look right. One satellite not vetted after 12 months but still receiving traffic. Earnings calculator shows it is vetted

You may subscribe to the issue above, or send a pull request with a fix, we will be happy to review it and merge.

Release preparation v1.131

Product Discussions STORJLINGS

arrogantrabbit June 18, 2025, 11:34pm 15

Nope: