Prerequisites
- A Google Cloud account with a Cloud SQL instance
- A VexiData account
Connect Cloud SQL to VexiData
Enable Public IP on your instance
Your Cloud SQL instance must have a public IP address for VexiData to connect.
- Go to the Cloud SQL Console
- Click on your instance
- Go to Connections > Networking
- Under Public IP, make sure it’s enabled
- Copy the Public IP address from the instance overview page
Add VexiData to Authorized Networks
Cloud SQL blocks all external connections by default. You must add VexiData’s IP addresses as Authorized Networks.
- In your instance’s Connections > Networking tab
- Under Authorized networks, click Add a network
- Add each of VexiData’s IPs:
| Name | Network |
|---|---|
| VexiData 1 | 139.59.53.167/32 |
| VexiData 2 | 165.22.217.42/32 |
- Click Save
Authorized Networks are mandatory. Your connection will fail without this step.
Get your database credentials
- Go to the Users tab on your instance
- Note your username (default:
postgresfor PostgreSQL) - If you need to set or reset a password, click the user and choose Change password
| Parameter | PostgreSQL Example | MySQL / MariaDB Example | SQL Server Example |
|---|---|---|---|
| Host | Your instance’s Public IP | Same | Same |
| Port | 5432 | 3306 | 1433 |
| Database | postgres (default) | Your database name | Your database name |
| Username | postgres | Your username | sqlserver |
| Password | Your database password | Your database password | Your database password |
Add the connection in VexiData
- Go to Data Sources in VexiData
- Click PostgreSQL, MySQL, MariaDB, or SQL Server depending on your instance type
- Fill in the details:
| Field | Value |
|---|---|
| Display Name | A name to identify this connection (e.g., “Cloud SQL Production”) |
| Host | Your instance’s Public IP address |
| Port | 5432 (PostgreSQL), 3306 (MySQL / MariaDB), or 1433 (SQL Server) |
| Database | Your database name |
| Schema | public (PostgreSQL) or dbo (SQL Server) |
| Username | Your database username |
| Password | Your database password |
You do not need the Cloud SQL Auth Proxy to connect VexiData. The Auth Proxy is for applications that can’t use Authorized Networks — VexiData connects directly via Public IP.
Troubleshooting
Connection timed out
Connection timed out
- Verify VexiData’s IPs (
139.59.53.167/32and165.22.217.42/32) are listed in Authorized Networks - Check that Public IP is enabled on your instance
- Confirm the instance is running (not stopped)
Authentication failed
Authentication failed
- Verify your username and password. Reset the password from the Users tab if needed
- For PostgreSQL, the default user is
postgres. For MySQL and MariaDB, check the user you created during setup. For SQL Server, the default user issqlserver
No tables visible after connecting
No tables visible after connecting
- For PostgreSQL, confirm your tables are in the
publicschema. Update the Schema field in VexiData if they’re in a custom schema - Check that your database user has
SELECTpermissions on the tables