# Node offline internal error

**URL:** <https://forum.storj.io/t/node-offline-internal-error/2118>\
**Category:** troubleshooting\
**Tags:** unraid\
**Created:** [October 7, 2019, 3:25pm UTC](https://forum.storj.io/t/node-offline-internal-error/2118 "2019-10-07T15:25:16Z")\
**Posts on this page:** 1\
**Showing post:** 21

<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:** [October 8, 2019, 8:53pm UTC](https://forum.storj.io/t/node-offline-internal-error/2118/21 "2019-10-08T20:53:11Z")

</div>

This check with counting the sign sections is enough at the moment.  
But I have to agree, it would be nice to check it against the public key.  
Maybe more effective to integrate this check to the SNO board:

> [@Node Dashboard (UI/UX Feedback)](https://forum.storj.io/t/node-dashboard-ui-ux-feedback/1975/35):
>
> Thought of something else. Now that the online offline indicator is a bit slow to update it would be really nice if the dashboard could show whether the external address and port are addressable from the outside and whether the identity is signed correctly. This would catch 99% of user errors during setup or later updates. I don’t think it’s necessary to show these elements when everything is fine, but adding an error when one of the two isn’t correct would help a lot.

---

_[View the full topic](https://forum.storj.io/t/node-offline-internal-error/2118)._