Set up issues with Zimacube Pro

Hi all,

this is my first post, and I couldn’t really find a similar topic, so please be kind :slight_smile:

I’ve been having issues with my Zimacube Pro. I bought 6 HDDs for it, connected it to my Mac Studio via Thunderbolt AND the ethernet port using the CAT6 cable included. When I boot up the Zima client, it says no devices found. I’ve tried using one instead of both, restarting both the computer and the NAS and nothing is working.

I checked their online doc and it said the client will always prioritize a direct line connection over a LAN, yet it doesn’t seem to even look for it over thunderbolt. Am I missing something?

Does anyone have any insight on how to solve this?

Have you checked this video?

And could you please record your screen using the client and upload it here for us to locate the issue?

Hi Giorgio,

Attached is a video of the issue. I show in the video that the Mac Studio recognizes the device, and that the Zima web client sees that the device is connected via TB4. Yet, I cannot get the client to actively connect over TB4, it just goes straight to LAN.

Hi, I watched your video. Are there any VPNs, proxies running on your machine? Also attach the log file of Zima Client here.

You can find the log file here:

  • macOS

    • ~/Library/Logs/Zima/main.log
  • Windows

    • %AppData%\Zima\logs\main.log

Look forward to your feedback.

Hi there, I dont use a VPN, but I use iCloud Private Relay, not sure if that affects anything, however.

I also dont see a log folder in the library.

It seems you are using an old version of ZimaOS.

Please update to the latest version for both ZimaOS and Zima Client.

These links might be helpful:

  1. You can update ZimaOS in the settings panel, and you can also do it manually: Update offline | Zimaspace Docs

  2. The latest Client: https://find.zimaspace.com

hi Giorgio,

I followed the instructions to the T and this is what I get when trying to install.

Sorry, this is a known issue: your current version is too old.

Please update to 1.2.5 first, and then update to the latest version. This should work.

Finally works! Thank you Giorgio!

1 Like