saferowThe SSH server
- “…doesn’t resolve.” The name isn’t known to this Mac. Check the name in
~/.ssh/config, or connect your VPN. Edit the SSH host to change it. - “Nothing answers SSH on … port 22.” The server is reachable but nothing listens on that port. Check the port with your provider; Edit the SSH port.
- “No answer from … over SSH after 15 s.” A firewall or VPN usually does this: the packets go nowhere. Connect the VPN, or check the server’s firewall, then Try again.
- “This Mac has no route to …” Check your network or VPN.
- “saferow couldn’t run ssh on this Mac.” saferow uses the ssh that comes with macOS. Run
ssh -Vin Terminal to see whether it works there.
In every case, Open in Terminal runs the same ssh command in Terminal, so you can see what it says there.
The tunnel
“ssh couldn’t open the local end of the tunnel.” saferow forwards a free local port to the database through ssh. This message usually means the port was taken at that moment: Try again.
“SSH works, but nothing answers on port 3306 on that server.” The tunnel opened, but the database isn’t listening where saferow looked. saferow looks at the server’s listening ports and says when it finds the database on another one, such as “MySQL is listening on 3307”; press Use port 3307. A database in Docker on the server is often published on a different port, or only inside Docker’s network.