Troubleshooting
Resolve common connection, editor, and data-editing issues.
“Server does not support SSL, but SSL was required”
If this is your local development server, enable Allow plaintext on localhost in connection settings. For a remote server, configure valid TLS and keep verified TLS enabled. If you deliberately use a public demonstration server without TLS, choose Use Plaintext… and confirm the warning for that host. Credentials, SQL and results will be unencrypted. Knowhere never falls back to plaintext automatically.
Connection refused or timed out
Check that PostgreSQL is running, the hostname and port are correct, and the server accepts your client address. With Docker, use the host's published port. A local mapping to a nondefault port is not reachable at 5432 unless that is the published port. Check your firewall and PostgreSQL authentication rules.
Certificate validation failed
Use the DNS hostname included in the server certificate. Check expiry and the selected CA bundle. If the CA file changed, import the current PEM bundle again; Knowhere keeps a copy rather than following changes to the original file. Do not send a private key to support.
No table or column suggestions
Connect to the intended database, refresh schema objects, and try Control–Space. Check the SQL assistance status at the bottom of the window. Use Query → Restart SQL Assistance if necessary. Your role may not be able to see every object. SQL suggestions and diagnostics do not grant database permissions.
An edit cannot be saved
Check field validation, PostgreSQL constraints, table identity, and write protection. Another client may have changed the original row. Review the conflict rather than retrying an overwrite blindly. A failed transaction must be rolled back before continuing.
Disconnected during a write
The server may have committed even if the response never reached your Mac. Inspect the actual row state before attempting the change again. Reconnect preserves local context and locks writes again; it does not automatically replay SQL or save a draft.
Missing performance statistics or index tools
pg_stat_statements and HypoPG are optional PostgreSQL extensions. Availability and visibility depend on the server configuration and your role. Ordinary table browsing and SQL editing do not require them.
A diagram is too dense
Choose one schema, search for a table, enable Key columns only, or focus a selected table. Use Fit and scroll/zoom. Read exact mappings in the relationship list when paths overlap.
Still stuck? Contact support with sanitized reproduction steps and version information.