Aliaksei

Hello, @micush. Currently, another packaging format is out of scope for ZeroUI. It's hard to create all the necessary scripts to pack the application in the CI in all the...

@wongsyrone, thanks for pointing! This one is also affected.

Currently, I'm still thinking for the proper migrations solution for ZeroUI: https://github.com/dec0dOS/zero-ui/issues/75

Thanks for reporting the problem. Seems to be ZeroTier Team made some [breaking changes](https://github.com/zerotier/ZeroTierOne/releases/tag/1.12.0) to the controller behavior. You should stay on the latest supported ZeroTier version for the controller...

The issue on ZeroTierOne repo to track the problem: https://github.com/zerotier/ZeroTierOne/issues/2108

Fixed in 1.12.1 _Originally posted by @glimberg in https://github.com/zerotier/ZeroTierOne/issues/2108#issuecomment-1694020567_

It was fixed in https://github.com/zerotier/ZeroTierOne/pull/2115, waiting for [1.12.2 release](https://github.com/zerotier/ZeroTierOne/milestone/5?closed=1)

@KevinRoebert you should wait for 1.12.2 release or downgrade ZeroTier on the controller to [supported version](https://github.com/dec0dOS/zero-ui/blob/main/docker-compose.yml#L5).

> You basically need to revert one line in `backend/routes/member.js` to get rid of the compatibility fix introduced to handle 1.12.0, now that the compatibility is back to what it...

I couldn't replicate the issue with 1.12.2. My apologies, it turns out I was actually testing 1.12.1 at the time. Could someone please verify the problem with their setup using...