01
Check your connection
Your host must be awake and reachable over SSH. Away from home, connect your VPN if your host requires one.
Cavreno support
Help with connections, terminal sessions, and the tools you use through Cavreno.
Email support01
Your host must be awake and reachable over SSH. Away from home, connect your VPN if your host requires one.
02
Check the saved host, username, container, and tmux socket. Different environments have separate sessions.
03
The message helps identify whether a connection, host key, authentication, or remote tool needs attention.
Common questions
Check that the host is awake, SSH is enabled, and its address, port, and username are correct. If it is on a private network, connect your phone to that network or your VPN first. Test the same SSH account from another computer.
Confirm the new fingerprint directly with your server administrator or through a trusted connection. Once you have verified the change, edit the host in Cavreno and explicitly forget the saved host key before reconnecting.
Check that you are using the same host, username, container, and tmux socket as your existing session. If tmux is installed outside the login environment’s PATH, set its absolute executable path in the host settings.
Your remote tmux processes can continue while the host stays running. iOS may suspend the SSH connection; Cavreno reconnects when you return. Check Agent notifications for the available notification setup and its delivery status.
Recognition depends on the agent executable and how it was launched. Confirm that it is running in tmux on the selected host or container. For supported integrations, open the host’s Agent integrations to check its installation and compatibility status.
Open Settings → Voice input to choose the transcription options. Allow microphone and speech-recognition access when prompted. If you previously denied access, review Cavreno’s permissions in iOS Settings. You can edit the transcript before sending it.
Report an issue
Write to [email protected] for help, feedback, or a feature request.
Keep passwords, private keys, access tokens, and private project content out of your report. Review screenshots and logs before attaching them.