Reaching the database

Nothing there

• “…doesn’t resolve.” Check the spelling of the host, or your VPN. Edit the host.
• “Nothing is listening on db.example.com:3306.” The host is up but no database answers on that port. If saferow finds one on another port on your Mac, it says so (“MySQL is running on 53306”) and offers Use port 53306. For a remote server, Connect through SSH is often the answer: most databases only listen on the server itself.
• “No answer from … after 15 s.” A firewall or VPN usually does this. Connect through SSH, check the host, or Try again.
• “This Mac has no route to …” Check your network or VPN.

Something answers, but not as expected

• “…closed the connection before anyone signed in.” The server hung up straight away. It may limit who can connect, or it may not be a database.
• “That port speaks PostgreSQL, not MySQL.” The engine is wrong for that port. Press Switch to PostgreSQL (or MySQL).
• “Something is listening on 6379, but it isn’t MySQL.” Another kind of server has that port. Edit the port.
• “MySQL on … doesn’t accept connections from this Mac’s address.” The server allows only some addresses (a MySQL host rule, or Postgres’s pg_hba.conf). Connect through SSH, so the connection comes from the server itself.
• “… has no free connections right now.” The server is at its connection limit. Try again shortly.
• “… is still starting up.” Try again in a moment.
• “This server doesn’t offer SSL.” The connection asks for SSL and the server has none. Turn SSL off if the network between you is trusted, or connect through SSH.

A SQLite file

• “There is no SQLite file at …” The file moved or was renamed. Choose the file.
• “That file isn’t a SQLite database saferow can open.” Choose the right file. saferow opens SQLite files read-only for reading, behind a guard that refuses writes.