Error retrieving list of networks on this controller: HTTPError: Response code 404

[hamsterchat]

Until a couple of days ago, ztncui was working correctly, but now I have this error when I try to access the network list and no device is connected.
Im using debian 12.

[GreatMichaelLee]

becuase you have upgraded to zerotier 1.16 and then this ztnui is no longer compatible, need ask the developers here to upgrade along with the potential API changes. Currently just donwgrade to 1.14

[key-networks]

@hamsterchat what version of zerotier-one are you running?

[key-networks]

Also, how are you running ztncui - as a Debian package or from the Node source?

[GreatMichaelLee]

@hamsterchat what version of zerotier-one are you running?

I have the same issue with him, I am running zerotier 1.16(by system auto apt upgraded) check the snapshot below, I've been running this enviroment for years until recent days I encounter the problem same to above , and I checked the only change is the zerotier upgraded. that's why I say so above. thanks.@key-networks,

and the UI display:

[key-networks]

Thanks for your feedback @GreatMichaelLee

Please check the permissions on authtoken.secret:

ls -l /var/lib/zerotier-one/authtoken.secret

If you see this:

-rw------- 1 zerotier-one zerotier-one ...

Then:

sudo chmod 640 /var/lib/zerotier-one/authtoken.secret
ls -l /var/lib/zerotier-one/authtoken.secret

and you should see:

-rw-r----- 1 zerotier-one zerotier-one ...

Make sure that the user ztncui is in the group zerotier-one:

grep ztncui /etc/group
grep zerotier /etc/group

You should see something like:

zerotier-one:x:995:ztncui

Then:

sudo systemctl restart zerotier-one
sudo systemctl restart ztncui

[key-networks]

This is the other option: https://github.com/key-networks/ztncui?tab=readme-ov-file#make-a-env-file

[GreatMichaelLee]

This is the other option: https://github.com/key-networks/ztncui?tab=readme-ov-file#make-a-env-file

no, I just tried downgrade to 1.14.2, everyting back. it is aboviously there are something changed in zerotier 1.16 that no more working smoothly with current ztncui version indeed, you can try by youself if possible. and I said, I didn't touch any file accessing privlillges things. nothing to do with the enviroment issue. thanks.

[key-networks]

I have tested zerotier-one 1.16.0 and can confirm that there is a problem, even after setting the permissions on authtoken.secret to 640. So, the answer is not to upgrade to zerotier-one 1.16 at this stage.

[key-networks]

See https://github.com/zerotier/ZeroTierOne/blob/dev/RELEASE-NOTES.md
"Default binary builds no longer contain the controller."

[key-networks]

You can downgrade like this:

apt-cache madison zerotier-one
apt-get install zerotier-one=1.14.2

Don't forget to set the permissions on authtoken.secret as per above.

[GreatMichaelLee]

See https://github.com/zerotier/ZeroTierOne/blob/dev/RELEASE-NOTES.md "Default binary builds no longer contain the controller."

Oooops, official builds remove the controller....so does that mean I need pay money to use controller license and do the private builds later on...? :(

The core (node/ and include/) and the service (service/ and osdep/) are now under the Mozilla Public License (MPL).
The network controller (controller/) is now under a commercial source-available license.
Use make ZT_NONFREE=1 to build non-MPL components.
Building with ZT_NONFREE=1 changes the license of the resulting executable to a proprietary commercial license vs. MPL.

[key-networks]

Oooops, official builds remove the controller....so does that mean I need pay money to use controller license and do the private builds later on...? :(

That's the impression I get for using 1.16 onwards. Otherwise, stick to 1.14.2 for the free version.

[hamsterchat]

@hamsterchat what version of zerotier-one are you running?

1.14.2

[hamsterchat]

Also, how are you running ztncui - as a Debian package or from the Node source?

Debian package