From Termius to Termix
Migrating my SSH hosts from a subscription-based commercial client to a self-hosted server on my NAS — including digging into an App Store app's encrypted database to get the data out.
The problem
For years I’ve kept the routes to my machines — servers, Raspberries, the NAS, the telescope — inside Termius, an SSH client with paid sync. It works well, but my hosts, and the credentials to reach them, live on someone else’s servers, behind a subscription. I wanted the same convenience (Mac, PC, phone, always in sync) with the data in my own house: Termix, an open-source, self-hostable SSH manager, running on the NAS.
The plan
A Termix server in a container on the Synology NAS, not exposed to the internet: at home it’s reached over the LAN, away from home only through the WireGuard VPN. The clients are the desktop apps (Mac and Windows) and the phone, all synced with the server. Astro- photography adds a special case: out in the countryside there’s no internet, so the desktop app has to work on its own and catch up when it’s back online. That’s why the telescope’s Raspberry appears twice — “home” and “field” — with different addresses.
The hard part: getting Termius to talk
Termius offers no clean export. The route was to pull out the app’s local, encrypted database, decrypt it with Termius’ own binary, then convert it to Termix’s import format with a small script. Three non-obvious obstacles:
- The App Store build runs in a sandbox: it can only read and write inside its own container. Decrypting from outside just errors out; it only works if the working files and temp folder sit inside the app’s container. The export script sets itself up there and cleans up at the end.
- The schema has changed: the open-source export tool I used found zero hosts on Termius version 10, because the data is now split across separate databases (hosts, SSH configs, identities, groups). The converter redoes the join by hand, and also handles identities that are linked only through a separate table.
- Empty passwords aren’t empty: where Termius had no saved password, the tool “decrypts” an empty string and leaves the ciphertext lying around, which looks like a real password. The converter recognises it by its shape and treats it as “no password” — 6 hosts still needed a manual fix.
One more quirk: for records left half-synced, Termius keeps two versions of the same password, a local one and one from the last sync. The local one was the right one.
An unhelpful sync error
After upgrading the server to 2.9.0, the desktop app, still on 2.8.0, refused to sync with a generic 404: the new version changed the sync protocol. The server and every client therefore need the same version, updated together. One extra trap: the installers for the two versions have the same file name, and differ only in the download address.
Cleanup
The export file contains plaintext passwords, so it’s securely wiped (rm -P, which
overwrites it) as soon as the import is done, and the script itself deletes the decrypted
temp files even on failure. None of it ever goes into git.
Status
Completed on 8 October 2026. All 22 SSH hosts are in Termix and working — the duplicate is gone — with the desktop apps for Mac and Windows in standalone mode plus sync, and the phone app going through the VPN. The telescope Raspberry has its two entries, “home” and “field”, with their final addresses, plus a backup SSH client on the phone for out in the countryside. Termix’s data folder — database, encryption keys and certificates — is in the NAS backup, verified. A few Telnet hosts were left out on purpose. Only one thing remains, and it isn’t technical: keep Termius running in parallel for a few more weeks, then cancel the subscription.
Stack
Node.js · zsh · SSH · Docker · Synology Container Manager · WireGuard