# Release preparation v1.63

**URL:** <https://forum.storj.io/t/release-preparation-v1-63/19558>\
**Category:** Product Discussions\
**Created:** [September 2, 2022, 11:36am UTC](https://forum.storj.io/t/release-preparation-v1-63/19558 "2022-09-02T11:36:33Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 17, 2022, 7:30am UTC](https://forum.storj.io/t/release-preparation-v1-63/19558/5 "2022-09-17T07:30:32Z")

</div>

> [@Andrii](#):
>
> [7e71986](https://github.com/storj/storj/commit/7e71986) storagenode: accept HTTP calls on public port, listening for monitoring requests

I’ve been having a look at this and it looks like my three oldest nodes all say they’re not healthy…

```auto
{
  "Statuses": null,
  "Help": "To access Storagenode services, please use DRPC protocol!",
  "AllHealthy": false
}

```

My guess is this is because they still have the stefan-benten satellite in their db’s and can’t connect to it anymore for obvious reasons. Newer nodes that never dealt with that satellite do say they’re all healthy.

Ps. we also still see an error in the log every time we refresh the dashboard. It seems the software still doesn’t deal great with a satellite disappearing.

---

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