How to Connect Your Google Cloud SQL MySQL Database to Indiequery

Last updated: November 21, 2025

Connect your Google Cloud SQL MySQL database to Indiequery to query and explore data through a web interface. No desktop apps, no command line. Just configure your Cloud SQL instance for public access and connect in minutes.

Get Your Google Cloud SQL Connection Details

Log into the Google Cloud Console at console.cloud.google.com and navigate to SQL in the left sidebar. Select your MySQL instance to open the instance details page.

On the Overview tab, you'll see your instance connection information:

  • Connection name - Format: project-id:region:instance-id
  • Public IP address - The static IPv4 address (only visible if public IP is enabled)
  • Default user - root
  • Database name - The database you created (check the Databases tab)

You'll need these details to connect from Indiequery.

Enable Public IP and Add Indiequery to Authorized Networks

Cloud SQL blocks all external connections by default. You must enable public IP and whitelist Indiequery's IP address.

Click the Connections tab on your instance page. Under Networking, enable the Public IP checkbox if it's not already checked. Your instance receives a static IPv4 address automatically.

Scroll to Authorized networks and click Add network:

  1. Name - Enter "Indiequery" or any descriptive label
  2. Network - Enter 91.98.141.61/32 (Indiequery's IP address in CIDR notation)
  3. Click Done, then click Save

The instance updates to allow connections from Indiequery. This takes a minute to apply.

Configure SSL/TLS Encryption

Google strongly recommends enforcing SSL for all public IP connections. On the Connections tab, scroll to Security and verify SSL mode.

ENCRYPTED_ONLY is recommended for Indiequery - this requires SSL/TLS but doesn't require client certificates. If your instance uses ALLOW_UNENCRYPTED_AND_ENCRYPTED (the default), connections work but are less secure.

To download the server CA certificate (optional, but recommended for verification):

  1. Click Manage server CA certificates
  2. Download the server-ca.pem file
  3. Keep this file for reference (Indiequery can verify SSL without needing to upload it)

Connect to Indiequery

Navigate to app.indiequery.com and click Add Database Connection. Enter your Cloud SQL connection details:

  1. Host - Your instance's public IP address (from the Overview tab)
  2. Port - Enter 3306
  3. Database - Your database name (check the Databases tab if unsure)
  4. Username - Enter root (or your custom user)
  5. Password - The password you set when creating the instance
  6. Keep "Require SSL" checked (Google recommends encrypted connections)
  7. Name your connection (e.g., "GCP Production")
  8. Click Add Connection

Indiequery tests the connection automatically. Once successful, you're ready to query your Cloud SQL database.

Reset Your Database Password

If you don't remember the root user password, you can reset it in the Google Cloud Console.

Go to your instance page and click the Users tab. Find the root user in the list and click the three-dot menu, then select Change password. Enter a new password and click OK.

Use the new password when connecting from Indiequery.

Cloud SQL Auth Proxy vs Direct Connection

Google offers two connection methods:

Cloud SQL Auth Proxy - A local proxy that runs on your machine, handles authentication automatically, and encrypts traffic. Designed for development and testing. Not suitable for external tools like Indiequery since the proxy runs locally.

Direct connection - Connect directly to the instance's public IP using standard MySQL protocol. This is what Indiequery uses. Requires authorized networks (IP whitelisting) and SSL configuration.

Always use direct connection for Indiequery. The Auth Proxy only works for applications running on your local machine or within Google Cloud.

Private IP vs Public IP

Cloud SQL instances can use private IP (VPC network only) or public IP (internet-accessible).

Private IP - Only accessible from resources within your Google Cloud VPC network. Not accessible from external tools like Indiequery unless you set up VPN or interconnect.

Public IP - Accessible from the internet with authorized networks configured. Required for Indiequery to connect.

If your instance only has private IP enabled, you must enable public IP in the Connections tab before Indiequery can connect.

Common Connection Issues

"Connection timed out" or "Connection refused"

Verify you enabled Public IP in the Connections tab. Check that Indiequery's IP (91.98.141.61/32) is listed in Authorized networks. Confirm your instance status shows Running (green checkmark). Wait a minute after adding the authorized network - changes take time to apply.

"SSL connection required"

If your instance uses ENCRYPTED_ONLY SSL mode, keep "Require SSL" checked in Indiequery. If you unchecked it, re-enable and try connecting again.

"Authentication failed"

Double-check your root user password. If you don't remember it, reset it via the Users tab in Cloud SQL. Verify you're using the correct username (default is root).

"Unknown database"

Check the Databases tab in your Cloud SQL instance to see the database name. You may have created custom databases during setup. Database names are case-sensitive.

"Host is not allowed to connect"

This error means your IP isn't authorized. Add 91.98.141.61/32 to authorized networks in the Connections tab. If you recently added it, wait a minute for changes to propagate.

Read Replicas

Cloud SQL supports read replicas for high availability and read scaling. Connect Indiequery to a read replica instead of your primary instance for safer querying.

In the Cloud SQL instances list, click Create read replica next to your primary instance. Choose the same region or a different region for geographic distribution. Once the replica is running, it gets its own public IP address.

Use the replica's public IP, add Indiequery to the replica's authorized networks, and connect using the same database credentials. Queries run against the replica don't impact your primary instance.

Next Steps

Once connected:

  • Browse tables and schemas in the schema explorer
  • Run SQL queries with autocomplete
  • Create charts and visualizations
  • Save queries for reuse
  • Build dashboards
  • Export results to CSV, JSON, or Markdown

Navigate to the query editor and start exploring your Google Cloud SQL data.

← Back to Hosting Integration