# Create NodeRed login for Ihost

**URL:** <https://forum.ewelink.cc/t/create-nodered-login-for-ihost/23439>\
**Category:** eWeLink CUBE\
**Created:** [October 25, 2023, 12:53pm UTC](https://forum.ewelink.cc/t/create-nodered-login-for-ihost/23439 "2023-10-25T12:53:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![csongor.varga](https://avatars.discourse-cdn.com/v4/letter/c/ea666f/32.png) [@csongor.varga](https://forum.ewelink.cc/u/csongor.varga)\
**Post date:** [October 26, 2023, 5:39am UTC](https://forum.ewelink.cc/t/create-nodered-login-for-ihost/23439/3 "2023-10-26T05:39:12Z")

</div>

> [@eerke](#):
>
> etty sure my Home Assistant Node Red also doesn’t need a password either. Was planning on locking both but never got round to

You need to install the File Manager plugin ([read here](https://forum.ewelink.cc/t/add-on-guide-volume-management-filebrowser-add-on/18254)) and that will give you access to the file system. With that you can edit the settings.js on the iHost.

And check this [article](https://nodered.org/docs/user-guide/runtime/securing-node-red#editor--admin-api-security) on how to configure access to the Node-Red editor. That should fix your problem.

As the guide suggestes you can run `node-red admin hash-pw` to generate the hash for the password, but I have no idea how you can run that on the iHost.

Also keep in mind that after all these changes the editor is still accessed via unsecure http communication. Therefore I would not open up the port and make it accessible via the internet.

---

_[View the full topic](https://forum.ewelink.cc/t/create-nodered-login-for-ihost/23439)._
