Help
Everything you need to get SSHush working. If something isn't covered here, get in touch or post in GitHub Discussions.
// adding a server
Tap the + button on the Servers tab. SSHush will ask for your server's hostname or IP address, SSH port (default 22), username, and credentials - either a password or an SSH private key.
SSHush connects immediately to verify the details and retrieve the host key fingerprint. You'll be shown the fingerprint and asked to accept it before the server is saved. On subsequent connections, SSHush verifies the fingerprint matches - if it doesn't, you'll be warned before connecting.
Credentials are stored in your device's Keychain and sync across your devices via iCloud Keychain. They are never sent to SSHush's servers.
// how metrics work
SSHush connects to your server over SSH and reads directly from /proc and /sys - the same sources the kernel uses internally. No agent is installed, nothing is changed on your server, and there is no ongoing resource usage when SSHush is not actively polling.
Metrics collected include CPU usage and per-core breakdown, active memory and swap, disk usage across all mount points, network interface throughput, disk I/O rates, load average, CPU temperature where sensors are available, and system uptime.
The polling interval is configurable per server. The default is 10 seconds.
Metrics work over any connection - local network, VPN, Tailscale, or public internet. The server does not need to be publicly reachable for metrics to work.
// alerts
Alerts are a paid feature at $2 per server per month. When you enable alerts for a server, SSHush's monitoring infrastructure polls it directly from three regions - New York, Amsterdam, and Singapore - and sends a push notification when a threshold is breached and sustained.
To configure alert rules, tap Configure Alerts on a server card. You can set thresholds for CPU, memory, swap, disk, load average, temperature, latency, and server reachability. Each rule has a configurable check frequency and consecutive breach count before firing.
Alerts require iCloud - SSHush uses your iCloud identity to associate alerts with your account. If iCloud is unavailable, metrics continue to work but alerts are disabled.
Important: push notification alerts require your server's SSH port to be reachable from the internet. SSHush's monitoring backend connects directly to your server to check metrics. If the port is firewalled, alerts cannot fire.
// firewall configuration
SSHush's monitoring backend connects to your servers from three fixed IP addresses - one per region.
The current IP addresses are listed at sshush.app/firewall-ips. These IPs will not change without advance notice. You can also find a link to this page in the app under Settings → Security.
// troubleshooting
Server shows as offline. Check that the host, port, and credentials are correct. If you're on a different network than usual, check whether the server is reachable from your current connection. Tap the card to retry.
Metrics are not updating. SSHush polls on the configured interval. If the server goes offline mid-session, SSHush will show the last known metrics and attempt to reconnect automatically when you return to the app.
Alerts are not firing. Check that your server's SSH port is reachable from the internet - this is required for the monitoring backend to poll it. Check the status page to confirm the monitoring infrastructure is healthy. If both look correct, check that the alert rule threshold is set appropriately for your server's normal load.
Push notifications not arriving. Check that notifications are enabled for SSHush in iOS Settings. Check the status page for any known issues. If a condition clears before the notification is delivered, the alert will show as resolved in the Alerts tab.
Temperature not showing. CPU temperature requires hardware sensors to be exposed via /sys/class/thermal or /sys/class/hwmon. Virtualised environments (DigitalOcean, AWS, GCP, and most VPS providers) do not expose sensors - temperature will not appear on these servers.
// containers
SSHush is not suitable for monitoring containerised environments such as Docker or LXC. Metrics are read from the host kernel and reflect host-level resources, not container allocation. This means CPU and memory figures will show the host totals rather than what the container is actually using, which is misleading and not useful for container monitoring.
SSHush is designed for bare metal servers, VMs, and VPS instances where the metrics reflect the actual resources available to your workload.
Still stuck? Contact us or post in GitHub Discussions. We're two people - you'll get a real answer.