CekTerm

Support

Questions, bug reports and feature requests all go to the same place: [email protected]. Including the version number from Settings → About → Version makes it much faster to help.

What you need

Getting started

  1. Tap + on the Hosts tab and enter the address, port and username.
  2. Pick an authentication method: import a private key, generate one on the device, or use a password.
  3. Save, tap the host, then create a session. The app runs tmux new-session the first time and attaches to it afterwards.
  4. Leave the app whenever you like. The session keeps running on the host.

Known limitations

RSA keys do not work on modern servers

The SSH library only implements ssh-rsa (SHA-1 signatures), which OpenSSH 8.8 and later removed from the default PubkeyAcceptedAlgorithms. The app warns you when you import an RSA key. Use Ed25519.

ECDSA private keys cannot be imported

Key parsing covers Ed25519 and RSA only. The app can generate ECDSA keys on the device, but cannot import an existing one.

No background polling or completion notifications

The app does not connect while backgrounded, so it cannot notify you the moment a job finishes. The job itself is unaffected — it is running in tmux on your host.

Not a full SFTP browser or port forwarder

File upload is there because getting a file onto the host is the thing that most often blocks you. Browsing and port forwarding are better done from a desktop client.

Troubleshooting

SymptomLikely cause
Authentication fails with a key that works elsewhere It is probably an RSA key — see above. Try a password or an Ed25519 key.
Connects, then reports that tmux was not found tmux is not installed, or not on PATH. Set an absolute path in Edit host → tmux binary, e.g. /opt/homebrew/bin/tmux.
Host key mismatch warning The host's key changed since your first connection. If that was expected (server rebuilt), use Forget this host's key in the host menu. If not, do not continue.
Metrics tab shows nothing The host has no /proc — macOS and BSD do not. Metrics are Linux-only.

Privacy

No account, and nothing you type ever reaches us. The app does send basic usage statistics — install date, interface language, launch time, app version — which Settings → Privacy → “Send usage statistics” switches off, and it shows occasional ads supplied by Google AdMob. Keys stay in the iOS Keychain and never leave the device. Full details in the privacy policy.

技術支援

問題回報、建議都寄到同一個地方: [email protected]。 附上設定 → 關於應用 → 版本的版本號,處理起來會快很多。

需要準備什麼

怎麼開始

  1. 在「主機」分頁按 +,填入位址、連接埠與使用者名稱。
  2. 選認證方式:匯入私鑰、在裝置上產生一把,或用密碼。
  3. 儲存後點進主機、建立 session。第一次會執行 tmux new-session, 之後都是 attach 回同一個。
  4. 隨時可以離開 App,session 在主機上繼續跑。

已知限制

RSA 私鑰在現代伺服器上不能用

SSH 函式庫只實作 ssh-rsa(SHA-1 簽章),而 OpenSSH 8.8 之後已把它從預設的 PubkeyAcceptedAlgorithms 移除。匯入 RSA 金鑰時 App 會警告。請改用 Ed25519。

不支援匯入 ECDSA 私鑰

金鑰解析只涵蓋 Ed25519 與 RSA。App 可以在裝置上產生 ECDSA 金鑰, 但無法匯入既有的。

沒有背景輪詢與完成通知

App 在背景時不連線,所以不會在任務完成的當下通知你。任務本身不受影響—— 它跑在你主機的 tmux 裡。

不是完整的 SFTP 瀏覽器,也不做埠轉發

會有檔案上傳,是因為「東西送不進去」最常卡住人。瀏覽檔案與埠轉發用桌面客戶端更順手。

疑難排解

症狀可能原因
金鑰在別的地方能用,這裡認證失敗 多半是 RSA 金鑰,見上方。改用密碼或 Ed25519。
連上了,但說找不到 tmux 沒安裝,或不在 PATH 上。到編輯主機 → tmux 執行檔 填絕對路徑,例如 /opt/homebrew/bin/tmux
出現主機金鑰不符的警告 這台主機的金鑰跟你第一次連線時不一樣了。若是預期中的(重建過伺服器), 用主機選單的「忘記這台主機的金鑰」。若不是,不要繼續連。
監控分頁什麼都沒有 那台主機沒有 /proc——macOS 與 BSD 都沒有。監控只支援 Linux。

隱私

沒有帳號,你打的東西不會傳到我們這裡。App 會傳送基本使用統計——安裝日期、介面語系、 開啟時間、App 版本——用設定 → 隱私 →「傳送使用統計」可以關掉;另外會顯示 Google AdMob 提供的廣告。金鑰留在 iOS Keychain,不會離開裝置。 完整說明見隱私政策