Node Remote

If you are looking for support on the NodeRemote app for controlling your ALL STAR node then please view the below guide. If you are using ASL3, then also refer to the lower image and information.

IMPORTANT

Before going any further you can also try a super easy to use script by G1LRO, which can be found here: https://github.com/G1LRO/node-remote-setup

Most issues are related to the manager.conf file has not been configured correctly. Below is a snippet which shows a working manager.conf file. Pay attention to the webenable, port, enabled, bindaddr and your admin/secret settings.

Issues with astdb.txt not found, are addressed at the bottom of this page. However, Android users should not see any issues with this if using the latest version of the app. iOS app will be updated soon to eliminate any astdb.txt errors.

You MUST reboot your node after changing the manager.conf file.

ASL3 Users Read Here

A big thank you to Colin, ZL2FL for bringing this to my attention, but ASL3 users will need to add a firewall entry within the new networking/firewall dashboard within ASL3. If you are using the default 5038 port, then this need to be added like in the below image.

ASTDB.TXT Not Found (ASL3 Only)

This will show on the app when the app cannot locate the astdb.txt file on the node. ASL3 does not automatically download this and MUST be enabled.

However, ASL3 still does not store the astdb.txt file in the location “Node Remote” expects, so you must follow these steps.

ASL3 will now keep the astdb.txt file updated automatically.

ASTDB.TXT Not Found (additional step if using Trixie)

Thank to Jim K8COP for passing this on. Please note, I have not tested this personally as none of my nodes use Trixie.