A Linux user wanted remote access to ZimaOS without a native ZimaClient desktop application. An IceWhale team member explained that the ZimaOS remote network is based on ZeroTier, so a Linux computer can join the device network directly and then use the ZimaOS virtual address as if it were on the same LAN.
This solves IP connectivity, but it is not identical to ZimaClient. ZimaClient also provides discovery, connection selection, file-manager shortcuts, backup, and other integrated workflows.
Get the Network ID from ZimaOS
Open Settings, switch to Network, and copy the device Network ID. The current Network ID guide shows the exact interface location.
Do not substitute the device LAN IP for the Network ID. The ID joins the overlay network; the virtual IP assigned after joining is what you use to reach the server.
Join from the Official ZeroTier Linux Client
Install ZeroTier using ZeroTier’s current platform instructions. After its service is running, the thread used:
sudo zerotier-cli join <ZIMAOS_NETWORK_ID>Replace the placeholder with the exact ID copied from your own ZimaOS. Confirm the network shows an authorized or online state before testing the dashboard. Do not publish your network identifiers, device addresses, or access screenshots unnecessarily.
Use the Virtual Address for ZimaOS and Apps
Once joined, identify the ZimaOS address assigned on that virtual network. Open the dashboard at that address and include the app’s published host port when required. A service that works on the LAN but not over ZeroTier may be bound only to a specific interface or blocked by a host firewall.
The current ZimaOS remote-access guide describes the integrated client path. Manual ZeroTier is a Linux workaround documented by the community thread, not a feature-for-feature ZimaClient replacement.
Choose File Access Separately
Joining the network creates connectivity; it does not automatically mount files. After the link works, connect to a ZimaOS SMB share with the server’s virtual IP and your ZimaOS credentials. Avoid exposing SMB directly through router port forwarding.
Why the Other Suggestions Need More Planning
The thread also mentioned Tailscale, WireGuard, reverse proxies, dynamic DNS, and Cloudflare Tunnel. Those can be valid architectures, but they have different trust, routing, authentication, and public-exposure models. A reverse proxy is appropriate for selected web apps, not as a generic replacement for private SMB access.
Linux Remote-Access Checklist
- Confirm remote access is enabled in ZimaOS.
- Verify ZeroTier service health on Linux.
- Confirm the correct Network ID was joined.
- Use the assigned virtual IP, not the Network ID, in the browser.
- Test the ZimaOS dashboard before testing individual app ports.
- Keep a local-LAN recovery path before changing network settings.
ZimaOS Linux Remote Access FAQ
Is there a current native ZimaClient desktop app for Linux?
The current official download guide lists Windows and macOS desktop clients, not Linux.
Does ZeroTier alone provide the ZimaClient file interface?
No. It provides the private network path; file mounts and application access are configured separately.
Should SMB be forwarded on the public router?
No. Reach it through the private overlay network instead of exposing SMB publicly.
