can't remotely access any Cloud SQL Gen 1 server!

[Rob]

I've never had a problem like this before.

For some unknown reason I can't remotely access my cloud SQL instances today. Gen 1 v5.6

The servers are still up and serving app engine requests.

MySQL Workbench gives a "SSL connection error: unknown error number"

What can I try?

[Vadim Berezniker]

I think I remember seeing a Stackoverflow post about this (can't find a link at the moment). 

Try updating your Workbench version.

--
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-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/78d3dfa9-6ba3-4513-b017-b950b1efe5fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rob]

Yep, that fixed it. Strange. Apparently after the win 10 creators update last night, something about workbench connecting to cloud sql stopped working. Especially strange since workbench connected fine to other GCE instances accessible via SSL, just cloud SQL was not. 

On Friday, April 14, 2017 at 1:06:31 PM UTC-4, Vadim Berezniker wrote:

I think I remember seeing a Stackoverflow post about this (can't find a link at the moment). 

Try updating your Workbench version.

On Fri, Apr 14, 2017 at 10:04 AM Rob <rober...@parasql.com> wrote:

I've never had a problem like this before.

For some unknown reason I can't remotely access my cloud SQL instances today. Gen 1 v5.6

The servers are still up and serving app engine requests.

MySQL Workbench gives a "SSL connection error: unknown error number"

What can I try?

--
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+unsub...@googlegroups.com.

[Vadim Berezniker]

Cloud SQL instances could have different SSL settings which could be a triggering a bug in MySQL workbench or elsewhere. 

Since upgrading MySQL workbench version fixes the problem, it may not be worth the effort figuring it exactly why the old version of workbench is failing.

On Fri, Apr 14, 2017 at 10:52 AM Rob <rober...@parasql.com> wrote:

Yep, that fixed it. Strange. Apparently after the win 10 creators update last night, something about workbench connecting to cloud sql stopped working. Especially strange since workbench connected fine to other GCE instances accessible via SSL, just cloud SQL was not. 

On Friday, April 14, 2017 at 1:06:31 PM UTC-4, Vadim Berezniker wrote:

I think I remember seeing a Stackoverflow post about this (can't find a link at the moment). 

Try updating your Workbench version.

On Fri, Apr 14, 2017 at 10:04 AM Rob <rober...@parasql.com> wrote:

I've never had a problem like this before.

For some unknown reason I can't remotely access my cloud SQL instances today. Gen 1 v5.6

The servers are still up and serving app engine requests.

MySQL Workbench gives a "SSL connection error: unknown error number"

What can I try?

--
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-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/78d3dfa9-6ba3-4513-b017-b950b1efe5fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

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-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/7b26a18d-e4ad-4945-b70a-baeb691d908b%40googlegroups.com.