Hello, this works perfekt for me. But when i restart my qnap it wont connect correctly to zerotier. In ZeroTier Central the qnap will be signed as online but i cannot ping to the device.
When i leave and join again, i got an error on join like: 500 join {}
Sorry i can’t look at it now i never had this problem with restart
also i cant look for it because i scaled down, because of the energy cost here in Europe
maybe it’s the last Qnap update from last month , if you see that you are online local and remote
it’s perhaps firewall rules or upnp
anyway its the same docker container as the use on synology
i hope this will help you
Hi that has with the QVPN pakage this installs the tun/tap driver
i think it has something todo with the update to 5.0.1 here is also some one who has the same problem
The mapped directory cannot use the original path ($HOME/docker/zerotier-one). After investigation, it was found that this path mapping does not exist after NAS restarts. The image cannot read the previous configuration after startup, which causes ZeroTier not to connect automatically.
docker exec zerotier-one ls -al /var/lib/zerotier-one
This command shows that the configuration directory is empty.
After NAS restarts, it is necessary to manually restart the CONTAINER in order to connect to the original network ID settings. By using the modified command above, there is no need for manual operation after NAS restarts; the container can connect to the original network ID automatically.
Hi! Newbie here!
I run the above commands on my Qnap. The status of Zerotier is ONLINE. Also I configured my NAS as subnet router in managed routes section on Zerotier central.
The problem is that I have no access outside of my local network. I disabled the QuFirewall with no luck.
Maybe the problem has to do with the local routing in my Qnap.