GCE cannot access private SQL

Question

I tried to access from GCE instance to Cloud SQL instance, which is private and having private service connection.

following private services access docs, I setup VPC and FW, and create SQL and GCE in same VPC. https://cloud.google.com/vpc/docs/configure-private-services-access

but in GCE, ping to SQL instance, nor sql connection didn't work.

create VPC

gcloud compute networks create test-custom-vpc --subnet-mode=custom --bgp-routing-mode=global --mtu=1460

create subnet

gcloud compute networks subnets create vpc-sb-1 --network=test-custom-vpc --range=10.100.0.0/16 --region=asia-northeast1

create IP range for private service connection

gcloud compute addresses create vpc-peering-range --global --purpose=VPC_PEERING
--addresses=192.168.0.0 --prefix-length=16 --description=description --network=test-custom-vpc

create VPC peering for SQL

gcloud services vpc-peerings connect --service=servicenetworking.googleapis.com --ranges=vpc-peering-range --network=test-custom-vpc --project=my-project

create mySQL in VPC

gcloud --project=my-project beta sql instances create vpc-sql-1 --network=test-custom-vpc --no-assign-ip

create GCE instance in VPC

gcloud compute instances create vm-in-sb-1 --subnet vpc-sb-1 --zone asia-northeast1-b

create FW rule, so far allow all IP/protocol

gcloud compute firewall-rules create allow-all --network test-custom-vpc --direction ingress --action allow --rules all

Then, I would access VM with ssh and check connection between VM & SQL

gcloud sql instances list NAME DATABASE_VERSION LOCATION TIER PRIMARY_ADDRESS PRIVATE_ADDRESS STATUS vpc-sql-1 MYSQL_5_7 us-central1-b db-n1-standard-1 - 192.168.0.3 RUNNABLE

-> SQL private IP is 192.168.0.3

ssh login

gcloud beta compute ssh --zone "asia-northeast1-b" "vm-in-sb-1" --project "my-project"

check connection

ping 192.168.0.3

no response

~~psql -h 192.168.0.3 -U postgres~~

mysql --host=192.168.0.3 --user=root --password

psql: could not connect to server: Connection timed out Is the server running on host "192.168.0.3" and accepting TCP/IP connections on port 5432?

I have no idea what configuration is wrong

JM Gelilio · Accepted Answer · 2021-02-19 09:21:58Z

1

I replicated your case, all configuration are working well but please note, using the command below in step #5 will create a Cloud SQL instance for Mysql not for Postgres:

gcloud --project=my-project beta sql instances create vpc-sql-1 --network=test-custom-vpc --no-assign-ip

If you want to create a Cloud SQL instance for Postgres use the command below:

gcloud --project=my-project beta sql instances create vpc-sql-1 --database-version=POSTGRES_12 --cpu=2 --memory=7680MB --network=test-custom-vpc --no-assign-ip

The problem is you are connecting to Cloud SQL for Mysql using Postgres database client. To proper connect use the following example:

for Mysql example:

mysql --host=192.168.0.3 --user=root --password

for Postgres example:

psql -h 192.168.0.3 -U postgres

edited Feb 19, 2021 at 9:21

answered Feb 19, 2021 at 7:08

JM Gelilio

3,8061 gold badge15 silver badges25 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Ryo Over a year ago

Thank you for your reply. the command psql -h 192.168.0.3 -U postgres was not correct. I tried mysql --host=192.168.0.3 --user=root --password but still failed

Ryo Over a year ago

sorry for my confusing update. Before I must have got error even if I had use mySQL or postgressSQL, but now, I cloud connect mysql. I don't know the reason, but possibly I might select different SQL. Thank you so much

Collectives™ on Stack Overflow

GCE cannot access private SQL

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related