blocks|key|1363319|text|您可以从VM连接到Cloud，因为您使用的是代理。如果您想连接到Cloud，那么您可以在Cloud的connections选项卡中白名单上列出VM的IP地址，请参阅此文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1363320|entityMap|0|LINK|mutability|MUTABLE|url|https://cloud.google.com/sql/docs/mysql/connect-compute-engine#gce-connect-proxy|1|https://cloud.google.com/sql/docs/mysql/connect-compute-engine#gce-connect-ip^0|M|2|0|2B|2|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You're able to connect from your VM to Cloud SQL because you're using the <a href="https://cloud.google.com/sql/docs/mysql/connect-compute-engine#gce-connect-proxy" rel="nofollow noreferrer">proxy</a>. If you would like to connect to your Cloud SQL then you have whitelist the IP address of your VM in Cloud SQL's connections tab, please refer to this <a href="https://cloud.google.com/sql/docs/mysql/connect-compute-engine#gce-connect-ip" rel="nofollow noreferrer">documentation</a>.

blocks|key|1993961|text|这是预期的行为。私有IP只能从虚拟私有云(VPC)访问。为了使资源(例如GCE实例)连接起来，它还必须位于该VPC上。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1993962|有关如何将GCE实例添加到VPC的说明，请参阅此页面，有关私有IP的环境要求的更多信息，请参见此页面。|1993963|entityMap|0|LINK|mutability|MUTABLE|url|https://cloud.google.com/vpc/docs/vpc|1|https://cloud.google.com/compute/docs/ip-addresses/#networkaddresses|2|https://cloud.google.com/sql/docs/mysql/private-ip#environment_requirements^0|F|A|0|0|O|2|1|1C|2|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

This is expected behavior. Private IPs are only accessible from a <a href="https://cloud.google.com/vpc/docs/vpc" rel="nofollow noreferrer">Virtual Private Cloud (VPC)</a>. In order for a resource (such as a GCE instance) to connect, it must also be on that VPC.

See this <a href="https://cloud.google.com/compute/docs/ip-addresses/#networkaddresses" rel="nofollow noreferrer">page</a> for instructions on how to add a GCE instance to a VPC, and see this <a href="https://cloud.google.com/sql/docs/mysql/private-ip#environment_requirements" rel="nofollow noreferrer">page</a> for more on the environment requirements for Private IP.

blocks|key|549189|text|您可以连接到127.0.0.1但不能使用VM的私有IP地址连接的原因是代理没有监听私有IP地址。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|549190|Cloud代理侦听环回适配器的内部地址，即127.0.0.1。此地址仅存在于计算机中。|549191|entityMap^0|6|9|0|L|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

The reason that you can connect to <code>127.0.0.1</code> but you cannot connect using the VM's private IP address is that the Proxy is NOT listening on the private IP address. 

The Cloud SQL Proxy listens on the loopback adapter's internal address which is <code>127.0.0.1</code>. This address only exists inside the computer.

blocks|key|1994022|text|云代理默认使用127.0.0.1，其中它接受连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1994023|要配置另一个IP地址，必须在instances参数中设置它：|1994024|./cloud_sql_proxy+-instances=<myCloudSQLproject:myCloudSQLzone:mycloudsqlinstance>=tcp:<IP_Address>:<PORT>|code-block|syntax|javascript|1994025|就像这样：|1994026|./cloud_sql_proxy+-instances=project_xxx:us-central1:database_yyy=tcp:10.203.23.12:9090|1994027|此配置还允许从其他主机连接到此云代理。|1994028|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

The cloud proxy uses 127.0.0.1 by default, where it accepts connections.

To configure another IP Address, you have to set it in the instances parameter:

<pre class="lang-sh prettyprint-override"><code>./cloud_sql_proxy -instances=&lt;myCloudSQLproject:myCloudSQLzone:mycloudsqlinstance&gt;=tcp:&lt;IP_Address&gt;:&lt;PORT&gt;
</code></pre>

Something like this:

<pre><code>./cloud_sql_proxy -instances=project_xxx:us-central1:database_yyy=tcp:10.203.23.12:9090
</code></pre>

This configuration allows connecting to this cloud proxy from others hosts as well.

I am testing the following configuration.

<ul>
<li>Cloud SQL (tetsql-1) in Region X Zone A</li>
<li>A Compute Engine VM (TestVM-1) in the same Region X Zone A. OS is Centos 7</li>
<li>Compute Engine VM is running cloud SQL proxy on non default port (9090)</li>
</ul>

With the above configuration I am able to logon to testsql-1 from TestVM-1 with below command:

<pre><code> `mysql -h 127.0.0.1 --port 9090 -u testuser -D testDB -p`
</code></pre>

However I am not able use the internal IP of TestVM-1 in the above command. It gives an error.

Another observation is I am able to do <code>telnet 127.0.0.1 9090</code> but when I try <code>telnet &lt;VM -Internal-IP&gt; 9090</code> returns a connection refused error.

Does anyone know if this is expected behaviour? If this is expected, why is it so?

Is it possible to connect to Cloud SQL Proxy via Host Compute Engine VM's Internal or External IP?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在测试以下配置。X区A区的云SQL (tetsql-1)X区域A中同一区域的计算引擎VM (TestVM-1)。OS是Centos 7计算引擎VM正在非默认端口(9090)上运行云SQL代理。使用上面的配置，我可以使用以下命令从TestVM-1登录到testsql-1：  `mysql -h 127.0.0.1 -...

问是否可以通过主机计算引擎VM的内部或外部IP连接到Cloud代理？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以通过主机计算引擎VM的内部或外部IP连接到Cloud代理？EN