Work outward from the phone:

• Use Ping to confirm the port is even answering. It measures a real TCP connection, so a result means the service is up, not just the machine.
• If Ping times out, the server is unreachable from this network — a firewall, a VPN that isn’t connected, or a wrong address.
• If Ping succeeds but SSH fails, it’s authentication or host-key related, and the error text will say which.

On a home or office network, iOS may also need to grant local network access — check Settings › Chapar › Local Network.

Chapar pins each server’s key the first time you connect. If the key later changes, you get a warning — which usually means the server was rebuilt, but can also mean someone is intercepting the connection.

Only accept a changed key if you know why it changed. That pin is stored on this device alone and is deliberately never synced: it’s a judgement this device made, and copying it silently to your other devices would undermine the point.

iOS suspends backgrounded apps, and there’s no way around that. Two things help:

• tmux resume — one toggle per host wraps the session so it survives being suspended and picks up exactly where it was. The server needs tmux installed.
• Auto-reconnect handles ordinary network drops, but deliberately won’t retry after a clean exit or a rejected password.

In the device Keychain, marked device-only — not in iCloud, not in backups, and unavailable while the phone is locked.

Secure Enclave keys go one step further: they’re generated inside the hardware and can’t be exported at all, by Chapar or anything else. There’s no code path that could upload any of it.

No. Every AI feature runs on Apple’s on-device model. Your commands and your servers’ output never leave the phone — no cloud provider, no Chapar server (there isn’t one).

If the on-device model isn’t available on your device, the features fall back to Chapar’s own rules rather than quietly reaching for a network.

Only commands that are provably read-only. It proposes a plan, every command is checked against a strict allowlist, and anything that could change the server is shown to you but refused, not executed.

When it suggests a fix, that fix is yours to run — the agent never runs it for you.

Sync is off by default. When you turn it on it runs through your iCloud account — there’s no Chapar server involved.

Host definitions, snippets, runbooks and history sync. Passwords, private keys and host-key pins never do. Turn on end-to-end encryption and your secure notes are encrypted with a key held only in your iCloud Keychain, so iCloud stores nothing but ciphertext.

Please don’t. The scanner, nmap, packet capture and SNMP tools are for infrastructure you administer or have written permission to test. Scanning networks you don’t control is illegal in many jurisdictions.

Because they run on your server, not on the phone. iOS can’t send raw packets, so Chapar drives the real tools where they already live and renders the results natively.

Install the tool on that host and try again:

iOS decides when background work happens, and it’s unpredictable by design — it weighs battery, network and how you use the app.

Chapar is honest about this rather than pretending otherwise: every result is stamped with when it was actually taken, and nothing in the app implies continuous monitoring. A phone isn’t a monitoring system, and treating it like one would be worse than not offering the feature.