Google cloud sql 在公司防火墙后面使用云sql代理-can';t连接到mysql实例

Google cloud sql 在公司防火墙后面使用云sql代理-can';t连接到mysql实例,google-cloud-sql,Google Cloud Sql,当我将http\U代理和https\U代理变量设置为正确的值时,我已经能够在公司防火墙后面使用google cloud sdk。看起来服务帐户的inital Oauth连接与这些代理变量集一起工作。但是,当我尝试使用mysql客户端连接到运行代理的机器时,到google mysql实例的连接失败 这是我对代理的命令,顺便说一句(已验证代理cmd/setup在不在公司防火墙后面的系统上工作): 错误看起来像 ... 拨打tcp 35.190.176.161:3307:connectex:连接尝试失

当我将http\U代理和https\U代理变量设置为正确的值时,我已经能够在公司防火墙后面使用google cloud sdk。看起来服务帐户的inital Oauth连接与这些代理变量集一起工作。但是,当我尝试使用mysql客户端连接到运行代理的机器时,到google mysql实例的连接失败

这是我对代理的命令,顺便说一句(已验证代理cmd/setup在不在公司防火墙后面的系统上工作):

错误看起来像 ... 拨打tcp 35.190.176.161:3307:connectex:连接尝试失败 由于关联方在一段时间后未作出适当回应,因此被撤销

同样,我已经验证了上述代理设置在不在公司防火墙后面的系统上工作,因此我想知道是否有必要配置云代理以使用http\u代理/https\u代理建立连接和通信


谢谢

MySQL有自己的协议,完全独立于HTTP,通常在端口3306上。虽然云SQL代理使用HTTP进行初始身份验证设置,但实际的SQL连接将此协议包装在端口3307的TLS中。不幸的是,没有办法通过HTTP代理运行MySQL协议。相反,您需要公司防火墙的例外情况

如果您只需要在命令行上访问云SQL,我建议您从Cloud Shell执行此操作,如中所述

如果您想构建一个更复杂的应用程序,从防火墙后面访问云SQL,那么可以构建一个公开HTTP API的GAE应用程序。然后,您可以通过代理使用该API,GAE应用程序可以连接到云SQL

cloud_sql_proxy -instances=api-project-1054727403053:us-east1:mysql-google-v1=tcp:3306 -credential_file=c:\tools\myeditor.json

2017/09/14 09:39:29 using credential file for authentication; email=myeditor@api
-project-1054727403053.iam.gserviceaccount.com
2017/09/14 09:39:29 Listening on 127.0.0.1:3306 for api-project-1054727403053:us
-east1:mysql-google-v1
2017/09/14 09:39:29 Ready for new connections
2017/09/14 09:39:34 New connection for "api-project-1054727403053:us-east1:mysql
-google-v1"
2017/09/14 09:39:57 couldn't connect to "api-project-1054727403053:us-east1:mysq
l-google-v1": dial tcp 35.190.176.161:3307: connectex: A connection attempt fail
ed because the connected party did not properly respond after a period of time,
or established connection failed because connected host has failed to respond.
2017/09/14 09:39:58 New connection for "api-project-1054727403053:us-east1:mysql
-google-v1"
2017/09/14 09:40:19 Throttling refreshCfg(api-project-1054727403053:us-east1:mys
ql-google-v1): it was only called 43.386s ago
2017/09/14 09:40:40 couldn't connect to "api-project-1054727403053:us-east1:mysq
l-google-v1": dial tcp 35.190.176.161:3307: connectex: A connection attempt fail
ed because the connected party did not properly respond after a period of time,
or established connection failed because connected host has failed to respond.
2017/09/14 09:40:41 New connection for "api-project-1054727403053:us-east1:mysql
-google-v1"
2017/09/14 09:41:23 couldn't connect to "api-project-1054727403053:us-east1:mysq
l-google-v1": dial tcp 35.190.176.161:3307: connectex: A connection attempt fail
ed because the connected party did not properly respond after a period of time,
or established connection failed because connected host has failed to respond.