Troubleshooting

Common situations and how to solve them.

Docker not found or not running

You'll see a red warning in the bottom bar. Check that Docker is running and that your user can reach it:

docker info

If you get a permission error, add your user to the docker group and log in again.

The VPN doesn't connect

• Press Logs on the VPN page; the reason is usually in the last lines.
• Certificate not recognized: the app shows the certificate's fingerprint and asks. If you trust it, it is saved to the profile.
• FortiGate: the ppp_async kernel module must be loaded (sudo modprobe ppp_async).
• 2FA: if a code is asked, Ask for a code on every connect must be on in the profile.

"quickssh is locked" error

Records are encrypted with the master password. Open the interface and unlock it, run the command in a terminal and enter the password, or use the QUICKSSH_MASTER_PASSWORD variable in scripts.

"Set a master password first" when saving

A master password is required to store records on your own computer. The interface opens the window by itself; on the command line run quickssh vault set.

The database port doesn't open

• "could not listen on the port": another program is using that port. Change it with quickssh edit-ssh <name> --local-port <port>.
• The connection opens but drops right away: if the VPN on the route asks for a password or a code, it can't start by itself; start it by hand first.
• TLS name error: see Databases.

The session drops when idle

A VPN stops when idle and wakes on a new connection; an open connection counts as use. For VPNs that must stay up for a long time, raise the time or turn it off:

quickssh edit acme --idle-minutes 0

Ctrl+V doesn't page down in the terminal

Ctrl+V pastes in the terminal. In programs like nano, use Page Down for the next page. Ctrl+X is passed to the program.

Can't connect to the central server

quickssh server show

The command tells you whether the server can be reached and what your identity there is. Check with your admin that your key is registered on the server. If the OTP lock is on, unlock with quickssh unlock.

Looking at the log

The quickest way to understand what happened is the activity log:

quickssh log -n 30