# Changelog v0.25.1

**URL:** <https://forum.storj.io/t/changelog-v0-25-1/2517>\
**Category:** STORJLINGS\
**Tags:** official-changelog\
**Created:** [November 7, 2019, 6:04pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517 "2019-11-07T18:04:04Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\
**Post date:** [November 7, 2019, 6:04pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/1 "2019-11-07T18:04:04Z")

</div>

> **[Release v0.25.1 · storj/storj](https://github.com/storj/storj/releases/tag/v0.25.1)**
>
> Changelog
> General
> 
> pkg/rpc: remove read/write deadlines as a mechanism for request timeouts (#3335)
> drpc: version bump (#3386)
> Increase default difficulty in identity CLI to 36 (#3428)
> drpc: enable...

**Increase default difficulty Part 1**  
With this release we increase the default difficulty from 30 to 36. This change is needed to protect the network against different attacks. This change only effects the identity generation and signing. **You can still use an old identity with a lower difficulty as long as it is already signed.**  
In part 1 (this release) we change the default for the identity binary but not for the certificate authority. You will still be able to sign identities with difficulty 30 or higher. If you haven’t signed your identity you should do it now. Last call 😉  
In part 2 (next release) we change the certificate authority as well. At that point you can only sign an identity with difficulty 36 or higher.

**Remove default concurrency limit**

> By default a storage node had a limit of 6 concurrent transfers and will reject additional uploads until one of the ongoing transfers is finished. We believe with dRPC the limit is not needed anymore. By default the storage nodes will now take as many uploads as they can. You can still set the limit in your config file like before. Removing it from the config will reset it to the new default value.  
> [Changelog v0.24.5](https://forum.storj.io/t/changelog-v0-24-5/2420)

Last release only halve of that change was released. This time the change is real. In addition to that we also increase the audit timeout from 25s to 5 minutes to avoid disqualifications for responding too slow. If you haven’t already **please remove any limit you might have set in your config file**. We want to test the limits of dRPC.

**Graceful exit**  
Doing our internal tests we found some edge cases that we want to cover first. Graceful exit is still under construction. Please don’t call it.

**Storj-sim requires redis**

> **[Test network](https://github.com/storj/storj/wiki/Test-network#using-redis)**
>
> Ongoing Storj v3 development. Decentralized cloud object storage that is affordable, easy to use, private, and secure. - storj/storj

**dRPC by default**  
The gateway and uplink binaries are compiled with dRPC by default but storagenode, satellite and all the other binaries are still compiled with gRPC. If you want to compile one of them from source you have to append `-tags=grpc`. If you are using one of our binaries, auto updater or docker containers you don’t need to do anything.

---

<div class="post-metadata">

**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\
**Post date:** [November 7, 2019, 8:18pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/2 "2019-11-07T20:18:43Z")

</div>

@littleskunk

I think limit is still persisting (I removed from config `storage2.max-concurrent-requests`) and after storagenode upgraded to latest version see this on log:

`docker logs storagenode 2>&1 | grep rejected`  
2019-11-07T20:01:27.060Z ERROR piecestore upload rejected, too many requests {“live requests”: 9}  
2019-11-07T20:01:28.599Z ERROR piecestore upload rejected, too many requests {“live requests”: 9}  
2019-11-07T20:01:30.996Z ERROR piecestore upload rejected, too many requests {“live requests”: 8}  
2019-11-07T20:02:54.721Z ERROR piecestore upload rejected, too many requests {“live requests”: 8}  
2019-11-07T20:12:28.007Z ERROR piecestore upload rejected, too many requests {“live requests”: 8}  
2019-11-07T20:12:28.461Z ERROR piecestore upload rejected, too many requests {“live requests”: 8}

---

<div class="post-metadata">

**Author:** ![kuprov](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kuprov/32/68_2.png) [@kuprov](https://forum.storj.io/u/kuprov)\
**Post date:** [November 7, 2019, 8:29pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/3 "2019-11-07T20:29:37Z")

</div>

Had your storagenode updated yet? Mine is still v0.24.5

---

<div class="post-metadata">

**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\
**Post date:** [November 7, 2019, 8:33pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/4 "2019-11-07T20:33:04Z")

</div>

Sure, watchtower did it perfectly: `Node Version: v0.25.1`

---

<div class="post-metadata">

**Author:** ![kuprov](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kuprov/32/68_2.png) [@kuprov](https://forum.storj.io/u/kuprov)\
**Post date:** [November 7, 2019, 8:33pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/5 "2019-11-07T20:33:32Z")

</div>

crap. that means my watchtower hung up. ☹

---

<div class="post-metadata">

**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\
**Post date:** [November 7, 2019, 8:36pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/6 "2019-11-07T20:36:01Z")

</div>

Please do not force it, watchtower check it about every 6 hours. (if you using command from documentation)

---

<div class="post-metadata">

**Author:** ![heunland](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/heunland/32/6076_2.png) [@heunland](https://forum.storj.io/u/heunland)\
**Post date:** [November 7, 2019, 8:37pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/7 "2019-11-07T20:37:40Z")

</div>

That iz is not what it means. Watchtower will not immediately update all nodes on the network at once. This is intentional in order to avoid too many nodes going offline at once. Please just wait until it is your turn.

---

<div class="post-metadata">

**Author:** ![Enzo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/enzo/32/60_2.png) [@Enzo](https://forum.storj.io/u/Enzo)\
**Post date:** [November 7, 2019, 8:49pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/8 "2019-11-07T20:49:19Z")

</div>

My GUI dashboard stopped working after Update… Any Idea why???

---

<div class="post-metadata">

**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\
**Post date:** [November 7, 2019, 8:50pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/9 "2019-11-07T20:50:01Z")

</div>

My proposition: **CTRL+F5**

---

<div class="post-metadata">

**Author:** ![Enzo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/enzo/32/60_2.png) [@Enzo](https://forum.storj.io/u/Enzo)\
**Post date:** [November 7, 2019, 8:51pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/10 "2019-11-07T20:51:04Z")

</div>

Did not help on Internet explorer…

---

<div class="post-metadata">

**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\
**Post date:** [November 7, 2019, 8:52pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/11 "2019-11-07T20:52:02Z")

</div>

Try to open in Incognito mode or clear caches (would be better change it to modern browser)

---

<div class="post-metadata">

**Author:** ![Enzo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/enzo/32/60_2.png) [@Enzo](https://forum.storj.io/u/Enzo)\
**Post date:** [November 7, 2019, 8:55pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/12 "2019-11-07T20:55:28Z")

</div>

[quote=“littleskunk, post:1, topic:2517”]  
concurrency  
sorry ment edge, still not working though. do i need a difficulty of 36… I believe my token is signed, that means that you ran the authorize storagenode command right???

---

<div class="post-metadata">

**Author:** ![Enzo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/enzo/32/60_2.png) [@Enzo](https://forum.storj.io/u/Enzo)\
**Post date:** [November 7, 2019, 8:59pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/13 "2019-11-07T20:59:26Z")

</div>

This error is appearing in node log…  
2019-11-07T15:56:51.591-0500 ERROR server gRPC stream error response {“error”: “piecestore protocol: rpc error: code = Canceled desc = context canceled”, “errorVerbose”: "piecestore protocol: rpc error: code = Canceled desc = context canceled\n\[tstorj.io/storj/storagenode/piecestore.(\*Endpoint](http://tstorj.io/storj/storagenode/piecestore.(*Endpoint)).doUpload:297\n\[tstorj.io/storj/storagenode/piecestore.(\*Endpoint](http://tstorj.io/storj/storagenode/piecestore.(*Endpoint)).Upload:

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 7, 2019, 9:02pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/14 "2019-11-07T21:02:25Z")

</div>

You do not need other identity, you need the other browser, chrome or Firefox

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 7, 2019, 9:03pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/15 "2019-11-07T21:03:00Z")

</div>

> [@Error piercestore protocol: rpc error: code = canceled desc = context canceled](https://forum.storj.io/t/error-piercestore-protocol-rpc-error-code-canceled-desc-context-canceled/970):
>
> Hey all, I regularly get the error attached. Is it a problem? Here is the first line. [storj.io/storj/storagenode/piecestore.{\*Endpoint](http://storj.io/storj/storagenode/piecestore.%7B*Endpoint)).Upload:283

---

<div class="post-metadata">

**Author:** ![Enzo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/enzo/32/60_2.png) [@Enzo](https://forum.storj.io/u/Enzo)\
**Post date:** [November 7, 2019, 9:06pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/16 "2019-11-07T21:06:19Z")

</div>

Thank you, Chrome works!!!

---

<div class="post-metadata">

**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/5_5575768a8748004e209b776fc1b2916d.png) [@Vadim](https://forum.storj.io/u/Vadim)\
**Post date:** [November 8, 2019, 10:13pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/17 "2019-11-08T22:13:03Z")

</div>

after 0.25.1 may be erlier started much more often this error, is this something bad?  
2019-11-09T00:10:27.846+0200 ERROR server gRPC stream error response {“error”: “piecestore protocol: rpc error: code = Internal desc = transport: transport: the stream is done or WriteHeader was already called”, “errorVerbose”: “piecestore protocol: rpc error: code = Internal desc = transport: transport: the stream is done or WriteHeader was already called\n\[tstorj.io/storj/storagenode/piecestore.(\*Endpoint](http://tstorj.io/storj/storagenode/piecestore.(*Endpoint)).doUpload:384\n\[tstorj.io/storj/storagenode/piecestore.(\*Endpoint](http://tstorj.io/storj/storagenode/piecestore.(*Endpoint)).Upload:171\n\[tstorj.io/storj/pkg/pb.\_Piecestore\_Upload\_Handler:1070\n\tstorj.io/storj/pkg/server.(\*Server](http://tstorj.io/storj/pkg/pb._Piecestore_Upload_Handler:1070%5Cn%5Ctstorj.io/storj/pkg/server.(*Server)).logOnErrorStreamInterceptor:23\n\[tgoogle.golang.org/grpc.(\*Server](http://tgoogle.golang.org/grpc.(*Server)).processStreamingRPC:1127\n\[tgoogle.golang.org/grpc.(\*Server](http://tgoogle.golang.org/grpc.(*Server)).handleStream:1178\n\[tgoogle.golang.org/grpc.(\*Server](http://tgoogle.golang.org/grpc.(*Server)).serveStreams.func1.1:696”}

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 9, 2019, 12:33pm UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/18 "2019-11-09T12:33:00Z")

</div>

A post was merged into an existing topic: [ERROR contact:chore pingSatellites failed](https://forum.storj.io/t/error-contact-chore-pingsatellites-failed/2287/11)

---

<div class="post-metadata">

**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\
**Post date:** [November 9, 2019, 6:44am UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/19 "2019-11-09T06:44:38Z")

</div>

How about update [public road map](https://storjlabs.aha.io/published/01ee405b4bd8d14208c5256d70d73a38?page=4)? 🙂  
It stuck on v0.24.0

 ![image](https://storj-s3.bcdn.literatehosting.net/original/1X/c21f1c08c7a5171520e91bfbdc8d0dbb850c22f2.png)

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [November 10, 2019, 11:06am UTC](https://forum.storj.io/t/changelog-v0-25-1/2517/20 "2019-11-10T11:06:35Z")

</div>

2 posts were split to a new topic: [An existing connection was forcibly closed by the remote host](https://forum.storj.io/t/an-existing-connection-was-forcibly-closed-by-the-remote-host/2567)

[Next page](https://forum.storj.io/t/changelog-v0-25-1/2517.md?page=2)