# Release preparation v1.68

**URL:** <https://forum.storj.io/t/release-preparation-v1-68/20526>\
**Category:** STORJLINGS\
**Created:** [December 1, 2022, 1:24pm UTC](https://forum.storj.io/t/release-preparation-v1-68/20526 "2022-12-01T13:24:32Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Roberto](https://storj.bcdn.literatehosting.com/letter_avatar/roberto/32/6_22734026db12803ebb3e059622ac3534.png) [@Roberto](https://forum.storj.io/u/Roberto)\
**Post date:** [December 2, 2022, 3:06pm UTC](https://forum.storj.io/t/release-preparation-v1-68/20526/7 "2022-12-02T15:06:10Z")

</div>

[![](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/clement/135/11821_2.png)](https://forum.storj.io/u/clement)

[clement](https://forum.storj.io/u/clement)[Storjling](https://forum.storj.io/g/storjling)

[3ore](https://forum.storj.io/t/quic-misconfigured-in-v1-67-1/20324/59?u=roberto)

> [@QUIC Misconfigured in v1.67.1](https://forum.storj.io/t/quic-misconfigured-in-v1-67-1/20324/58):
>
> because right now it looks like unrelated to the bug [QUIC Misconfigured in v1.67.1](https://forum.storj.io/t/quic-misconfigured-in-v1-67-1/20324)

> [@QUIC Misconfigured in v1.67.1](https://forum.storj.io/t/quic-misconfigured-in-v1-67-1/20324/38):
>
> To answer my own question, I’d say yes. A refresh of the page fixes QUIC.

> [@QUIC Misconfigured in v1.67.1](https://forum.storj.io/t/quic-misconfigured-in-v1-67-1/20324/32):
>
> 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

I guess now is a good time to explain how the QUIC configuration check works starting from the release of v1.67.1.

We reimplemented how the QUIC check is done and that was introduced in this commit: [storagenode: overhaul QUIC check implementation · storj/storj@59b37db · GitHub](https://github.com/storj/storj/commit/59b37db67019590c5a1008d73d23f644cd0dd745).  
The commit message explains at high low, what was wrong and what we did to fix this.

```auto
The current implementation blocks the the startup until one or none
of the trusted satellites is able to reach the node via QUIC.
This can cause delayed startup. Also, the quic check is done
once during startup, and if there is a misconfiguration later,
snos would have to restart to node.

In this change, we reuse the contact service which pings the satellite
periodically for node checkin. During checkin the satellite tries
pinging the node back via both TCP and QUIC and reports both statuses.
WIth this, we are able to get a periodic update of the QUIC status
without restarting the node.

```

To be clear, it makes sense that a hard refresh changes the QUIC status. You don’t need to restart the node unlike before this change was introduced. We are reusing the contact service which periodically sends a checkin request to the satellite. The satellite then tries to ping back the node via both TCP and QUIC. If any of the satellites fails to ping back the node using QUIC, the dashboard will show the misconfigured status message which could also mean that your node was offline or checkin failed and will be retried or the UDP service port is actually misconfigured.

---

_[View the full topic](https://forum.storj.io/t/release-preparation-v1-68/20526)._