QUIC Misconfigured in v1.67.1

[humbfig]

@humbfig

My updated node is also showing QUIC Misconfigured. Is this also a visual bug?

To answer my own question, I’d say yes. A refresh of the page fixes QUIC.

EDIT: I mean a refresh of the browser page fixed QUIC. Refreshing the dashboard using the top left button did not fix QUIC. Just saying…

[Alexey]

@DD7

If problem still affects many node operators, should Storj temporarily pause the auto-upgrade? Is that possible? @Alexey

At least until we know the exact cause and have a fix?

QUIC Misconfigured in v1.67.1

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…

and the version with a fix is in rollout:

QUIC Misconfigured in v1.67.1

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…

See https://version.storj.io/

[heunland]

@DD7

There should be some kind of mechanism in the node software/network that make sure the rollout of every new version is gradual.

Please note that we already are doing the rollouts of each new release in small batches, not all at once for all nodes for the exact reason you just stated.

[RandallStevens]

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.

I have “both protocols” set up on my router.

[LordWigo]

Well this is not my case I have tried everything (restarts, change router, recreate router rules, recreate nodes etc…). See here:

QUIC stop working after SYNOLOGY DSM update

Hello community, I have properly configured my nodes (on Windows and under Docker on SYNOLOGY NAS). I have updated SYNOLOGY DSM system. Everything went fine, docker operates properly and nodes under docker as well. Node on Virtual Machine (WINDOWS10) works properly. Only issue which I have is QUIC looks uncofigured. I tried re-add one node but still is the same: [image] I did not change anything on router and this works properly for all nodes from this NAS: [image] This is how I am conf…

Wigo

[snorkel]

Why don’t you all do a manual update to 1.67.3? It seems all the quick errors come from 1.67.1… so, manual update.

[Alexey]

We rolling out new versions by waves to do not shutdown the network.
So please be patient, it will be updated when its time to come.

[DD7]

@Alexey

So please be patient,

Don’t tell me to be pa… oh wait it came already.

[RandallStevens]

@Alexey

I stopped, removed, and then started the docker again…

Now it says I’m running 1.66.1.

But it fixed the QUIC misconfiguration!!!

[Alexey]

There is a more quick fix:

QUIC Misconfigured in v1.67.1

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…

[BrightSilence]

@RandallStevens

Now it says I’m running 1.66.1.

1.67.1 was pulled because of a bug, so this is nothing to worry about. You’ll get 1.67.3 soon.

[X64win]

I am sorry but all is Ok with port 28967.

[atxjl]

Hi there,
Since v1.67.3 is running, QUIC is back again with no changes in my network configuration!
Thanks to the StorJ team for fixing this issue.
Regards, atxjl

[robertL]

I have four nodes and two are showing QUIC as Misconfigured. I use Uptimerobot and no alarm. I also perform a page refresh every day or a few days.

Today I noticed that nodes with Version 1.67.3 and 1.67.1 have QUIC Misconfigured whereas the two nodes still on Version 1.66.1 have QUIC as OK.

It sounds like version 1.67.x has a bug.
Has anyone else seen this?

[Stob]

This has been talked about before - QUIC Misconfigured in v1.67.1

Ctrl+F5 in browser fixes dashboard display issue if no other problem exists.

[robertL]

Thanks, I had even rebooted but the recommendation worked.

Thanks again for the tip.

[snorkel]

Whould be great if CTRL+F5 will double the income too

[RandallStevens]

I pressed F5 several times.

I have also stopped and restarted the container several times.

I’m still getting QUIC misconfigured sometimes. It does say 1.67.3 now though

It’s really like pulling a slot machine with the reload button or F5 on my browser. Sometimes it says okay, sometimes misconfigured. Usually online, but occassionally offline.

I now have red warnings for suspension and online…

@Alexey