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.

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.

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, however you will still need to periodically perform step 4 so that the astdb.txt file is updated in the location “Node Remote” looks at.

Creating a startup script so that the command is ran on every reboot will stop the need to manually copy the file periodically.