# Changelog v0.21.1

**URL:** <https://forum.storj.io/t/changelog-v0-21-1/1787>\
**Category:** STORJLINGS\
**Created:** [September 19, 2019, 3:44pm UTC](https://forum.storj.io/t/changelog-v0-21-1/1787 "2019-09-19T15:44:06Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [September 19, 2019, 4:17pm UTC](https://forum.storj.io/t/changelog-v0-21-1/1787/4 "2019-09-19T16:17:23Z")

</div>

I feel like this time I have to write a bit more about the changes.

**Audit failures:**  
We believe that we have identified the root cause. I can’t go into the details as long as the issues is not fixed. This release contains part 1 of the fix and as soon as part 1 is working we can go on and deploy part 2. If we are lucky that might be possible today. In this special case I don’t want to deploy part 2 on a Friday and I am not sure if we will have time for it around the town hall next week. I will try my best.

**Kademlia removal:**  
You can read the full story here: [Design Draft: Removing Kademlia](https://forum.storj.io/t/design-draft-removing-kademlia/1038)  
As a side effect you might see that the last\_contact value on the CLI dashboard is not updated frequently. Especially on unvetted nodes.

**Vetting process:**  
Audit 2.0 is now live. Again you can read the full story here: [Design Draft: Auditing 2.0](https://forum.storj.io/t/design-draft-auditing-2-0/1040/2)  
My expectation is that you don’t get any audits for the next 24 hours. (While I write that down I notice that I should create a bug for that. The first iteration should start on startup.) Anyway. Every 24h the satellite will go through all pointers and for each storage node select 3 of them. If you have only 3 pieces you still have a high chance to get an audit. The 3 slots are not fixed and we might change that value any time.

**Storage node dashboard:**  
Just webbrowser [http://127.0.0.1:14002](http://127.0.0.1:14002) don’t forget to add `-p 127.0.0.1:14002:14002` to your docker run command or the port will be closed. I will open a new thread for the dashboard and you can write down your feedback there.  
If you are not running docker than I am sorry to say that we don’t support that. Take a look at the changelog and you should find the steps you need to execute 😉

---

_[View the full topic](https://forum.storj.io/t/changelog-v0-21-1/1787)._
