The 2024 source solution required more manual work than current ZimaOS. A community user installed the ZeroTier iOS app, discovered the Zima device's 10.x virtual address from another computer, enabled ZeroTier on the iPhone, and then connected through iOS Files or Readdle Documents.
That historical workaround should not be the default recommendation today. Current ZimaOS ships an official ZimaClient for iOS, and IceWhale's current Get Started documentation says mobile ZimaClient can discover the device, manage it, sync files, and establish remote access after the first successful connection.
The 2024 Method Used the ZeroTier iOS App Directly
The source user was unsure whether ZimaOS Remote Login was based on ZeroTier. A responder said they had successfully connected by installing ZeroTier One on iOS, joining the relevant network, and then accessing the ZimaCube through its 10.x virtual address.
They also reported a client-specific difference: the Cube appeared read-only in iOS Files but was writable in Readdle Documents. That is one person's 2024 app behavior, not a permanent ZimaOS filesystem limitation.
Current ZimaClient Supports iPhone and iPad Directly
Current IceWhale Get Started documentation says ZimaClient is available for iOS and Android as well as desktop platforms. The mobile client can monitor system status, manage apps, sync files, and connect remotely.
Use the current mobile ZimaClient setup instead of manually discovering a virtual 10.x address.
The First Successful Connection Establishes Remote Access
Current ZimaOS documentation says the initial ZimaClient connection saves the device relationship and configures the remote-access channel. After that, the client can reconnect outside the home LAN.
If Remote Access has been disabled in ZimaOS Settings, the remote client will not connect until it is enabled again.
Current Remote Access Is Encrypted and Peer-to-Peer
IceWhale describes the remote channel as encrypted P2P communication established automatically between ZimaClient and ZimaOS rather than a conventional public dashboard port.
Use the current ZimaOS remote-access model for the present architecture.
ZeroTier Still Exists Under the Connection Architecture
Current ZimaClient troubleshooting explains that IceWhale uses its own network controller on the Zima device while ZeroTier public discovery infrastructure helps peers find one another. IceWhale says neither it nor ZeroTier has administrative control over the user's virtual network.
This explains why the 2024 manual ZeroTier workaround was directionally related to the current architecture even though users no longer need to manage the mobile ZeroTier app manually for ordinary ZimaClient access.
Keep the ZimaOS Network ID Private
Current ZimaOS exposes a Network ID under Settings > Network. IceWhale warns that leaking this ID can expose shared folders and provides a reset function that invalidates existing connections and shares.
See the current Network ID security behavior before sharing connection information publicly.
Use ZimaClient for Normal Mobile File Access
Current iOS ZimaClient now provides a mobile file experience rather than requiring the user to mount a remote SMB share manually inside Apple's Files app. That is usually the simplest route for browsing and transferring NAS data remotely.
If a specific workflow still needs SMB/SFTP in another iOS app, first establish the secure network path, then configure the file protocol separately.
iPhone Remote Access FAQ
Do current iPhone users need to install ZeroTier One manually?
Not for the normal ZimaClient workflow. Current ZimaClient handles the remote connection directly.
Was manual ZeroTier confirmed working in the 2024 source?
Yes. One user connected to the Zima virtual address from iOS after enabling ZeroTier.
Does Remote Access require port forwarding?
Current IceWhale documentation describes the ZimaClient path as encrypted P2P remote access without normal router port forwarding.
