Sunday, January 21, 2018

[google-cloud-sql-discuss] Re: Cannot connect from cli

For the community visibility, currently Cloud SQL 2nd gen instances do not whitelist IPv6 (public) address associated with the client when using: 'gcloud sql connect'. There is a feature request submitted to support this. 



On Tuesday, January 16, 2018 at 12:47:16 PM UTC-5, Alessandro Tagliapietra wrote:
The IAM user has Project > Editor permissions (legacy?), if I remove that the error changes to forbidden. Instance has IPV4 address, if I whitelist my ip I can connect using regular postgresql tools.

On Tuesday, January 16, 2018 at 9:40:05 AM UTC-8, Pia Chamberlain wrote:
A couple of things to check-- when you say your IAM account has Editor permission, is that the legacy Project > Editor permission, or the Cloud SQL Editor permission? The former does indeed include the cloudsql.instances.connect permission, but the latter does not. Also, your instance must have an IPv4 address for this command to work.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/214ec831-e9c8-4505-92a4-78dc7b6e9db1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment