Common connection errors
When a connection test fails, STYD shows one of four plain messages. It does not repeat your database’s own error text, so what follows is what each message means and what to do.
The four messages
STYD could not reach your database
Nothing answered as expected: a wrong server address or port, a stopped server, or a network or firewall rule. If your server only accepts connections from approved addresses (firewall, security group or hosting provider rules), allow STYD’s addresses:
Nothing answered as expected: a wrong server address or port, a stopped server, or a network or firewall rule. If your server only accepts connections from approved addresses (firewall, security group or hosting provider rules), allow STYD’s addresses:
109.123.235.222 (IPv4) and 2407:3640:2324:5796::1 (IPv6). A name that goes through Cloudflare’s proxy cannot carry database connections: use a direct, DNS-only name or the server’s own address.The database refused the sign-in
The server answered and refused the user. Check the user name, the password and the database name, and that this user is allowed to connect from STYD’s addresses (for MySQL, the host part of the user).
The server answered and refused the user. Check the user name, the password and the database name, and that this user is allowed to connect from STYD’s addresses (for MySQL, the host part of the user).
The secure connection (TLS) to your database failed
Ask your database administrator to check that the server accepts secure (TLS) connections from outside its own network and allows them for this user, then test again. If it keeps failing, contact us.
Ask your database administrator to check that the server accepts secure (TLS) connections from outside its own network and allows them for this user, then test again. If it keeps failing, contact us.
This address is not allowed
Use the public address of your database.
Use the public address of your database.
localhost and private network addresses (for example 10.x, 192.168.x) are refused, and there is no SSH tunnel option. A custom, private installation can reach a database inside your own network: see Custom AI.Odoo connections show their own messages. The Odoo connection guide covers them, including the firewall rule for Odoo.
Duplicate connection
If a matching active connection already exists in the workspace, STYD warns you instead of creating a duplicate: use the existing connection. If the matching connection is archived, saving restores it with its history.
How to work through it
Re-check the server address, port, database, user, and password for typos.
Make sure the server address is a public one, not
localhost or a private network address.If the server restricts who can connect, allow both STYD addresses above.
If the name goes through Cloudflare’s proxy, use a DNS-only name or the server’s own address.
Test again, and see Troubleshooting if it still fails.