Verified
Status Update
No update yet.
Comments
se...@integrait.co
I have the same error, my database is located in AWS and connection is established successfully from other SQL client.
ag...@gmail.com
I do have the same error too. I can remotely access my MySql db.
ke...@krussell.co.uk
Same error message. I am unable to connect to a 5.1.73 MySQL DB on my hosting provider from Apps Script, but can connect OK from a desktop MySQL client.
My host has confirmed that they are not seeing anything in their logs to indicate that the request is arriving from Google.
My host has confirmed that they are not seeing anything in their logs to indicate that the request is arriving from Google.
em...@unito.it
Same error with Cloud SQL - MySQL 8 using Jdbc.getCloudSqlConnection(...)
pa...@fazwaz.com
Is this actually the case that JDBC can't connect to MySQL above 5.7, and if so is it still the case now? Originally reported 2 years ago...
I have the same issue/error as OP, can't connect to MySQL 8.0.19
I have the same issue/error as OP, can't connect to MySQL 8.0.19
ma...@konux.de
This issue is about 8.0
5.7 works fine, we downgraded form 8.0 to have this working.
5.7 works fine, we downgraded form 8.0 to have this working.
hi...@gmail.com
Same error. A shame there's no clear information that apparently JDBC only works for MySQL 5.7.
mi...@jivrus.com
Yes, it took some time to really understand it is a bug in appscript. We ended up routing the request through our private interface in the cloud platform for our Database Browser add-on to query the database from Google Sheets.
The same goes for connecting to PostgreSQL, MongoDB, and other databases - just no support in appscript - had to implement private interface routing
The same goes for connecting to PostgreSQL, MongoDB, and other databases - just no support in appscript - had to implement private interface routing
mk...@gmail.com
Same error. Works with MySQL 5.7 and not with 8.0
an...@greyjuicelab.com
Same issue here :(
te...@glassfrogg.com
Same issue.
ke...@gmail.com
Is there any work around for this?
I'm seeing the same issue.
MySQL db (version 8) is up and running. I can connect to it with a few different clients, but not JDBC.This happened only after I upgraded from MySQL version 5.x.x
I'm seeing the same issue.
MySQL db (version 8) is up and running. I can connect to it with a few different clients, but not JDBC.This happened only after I upgraded from MySQL version 5.x.x
[Deleted User] <[Deleted User]>
Same issue here: it works with MySQL 5.7 but not with 8.0. A fix is definitely welcome!
db...@gmail.com
This issue represents the last hurdle to upgrade MySQL in our stack to 8.0. We've tried proxy-sql to no avail and now are considering writing an external tool because we won't be able to use app script to connect to our database.
gu...@gmail.com
I too need the next version
to...@gmail.com
?
cn...@gmail.com
I use MySQL 5.7 get the same error. It works using other type of connection. Any Solution?
ha...@gmail.com
Same issue!!! Lost several days searching for a solution... incredible from Google not to care about this... its not on their Googel Apps Script guide either!
ya...@gmail.com
mi...@google.com
Hello there!
I have reported this behaviour internally. Any updates about this will be communicated here.
Thank you.
az...@gmail.com
Please help us on this, looks like your JDBC for MySQL is pretty old, I even change in MySQL the default_authentication_plugin to mysql_native_password and left empty the sql_mode, nothing works
al...@gmail.com
?
al...@getabedsuite.com
Come on guys
al...@wt.com.mx
You can do it! You rocks!
wa...@sbctech.net
Waiting this to be fixed for years. Please do it asap
tg...@cameron.k12.wi.us
Finding more about the TLS handshake:
https://serverfault.com/questions/1054736/logging-tls-handshake-openssl-mysql-fatal-protocol-version-70
This comment may help you google dev:
> But I find it strange in that it only uses TLS 1.1 (i.e. not at least TLS 1.2) and only (a few) CBC ciphers. Because it has the TLS extension supported_versions which points to some newer TLS stack - which likely supports even TLS 1.3 but is deliberately configured to only use TLS 1.1 for some unknown reason. – Steffen Ullrich Feb 16 at 21:32
This comment may help you google dev:
> But I find it strange in that it only uses TLS 1.1 (i.e. not at least TLS 1.2) and only (a few) CBC ciphers. Because it has the TLS extension supported_versions which points to some newer TLS stack - which likely supports even TLS 1.3 but is deliberately configured to only use TLS 1.1 for some unknown reason. – Steffen Ullrich Feb 16 at 21:32
ha...@gmail.com
Desperate about this issue... it may be on MySQL side?? Im not sure anymore. It seems the authentication method on the new MySQL 8 is not automatically compatible, I have checked webpages below pointing to this and to a solution related to chaging a system variable, but it still doesnt work for me. Zapier doesnt work either with MySQL 8.
https://github.com/mysqljs/mysql/issues/2046#issuecomment-396039909
https://github.com/mysqljs/mysql/pull/1962
PLEASE someone post when they find a solution. Thanks!
PLEASE someone post when they find a solution. Thanks!
ha...@gmail.com
Quoting several users on the links I posted just above:
If the account is created using the mysql_native_password authentication plugin, the client will just fall back to the "traditional" process during the handshake, keeping compatibility, by default for any previously supported server version.
everything should still work if you use the mysql_native_password plugin.
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'YourRootPassword';
-- or
CREATE USER 'foo'@'%' IDENTIFIED WITH mysql_native_password BY 'bar';
Another one said:
In addition to what @ruiquelhas said, I also had to:
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
And then restart the server.
If you are using multiple MySQL users, ensure that you update all of them that are connecting from remote (ie, not localhost). In my case I also had to use '%' instead of 'localhost'.
Let us know here if it works for you. Im trying with these last additional hints from the last user...
If the account is created using the mysql_native_password authentication plugin, the client will just fall back to the "traditional" process during the handshake, keeping compatibility, by default for any previously supported server version.
everything should still work if you use the mysql_native_password plugin.
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'YourRootPassword';
-- or
CREATE USER 'foo'@'%' IDENTIFIED WITH mysql_native_password BY 'bar';
Another one said:
In addition to what @ruiquelhas said, I also had to:
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
And then restart the server.
If you are using multiple MySQL users, ensure that you update all of them that are connecting from remote (ie, not localhost). In my case I also had to use '%' instead of 'localhost'.
Let us know here if it works for you. Im trying with these last additional hints from the last user...
az...@gmail.com
I tried that and doesn't work, the problem is not with the authentication is with the mysql client version
ha...@gmail.com
doesnt work here either, you are right. still stuck.
li...@york.ac.uk
I'm now experiencing this issue after a DB upgrade to MySQL 8; the connector reports (via getMetadata to an older database) that it is mysql-connector-java-5.1.38-SNAPSHOT - that seems to be a version of (originally) 2015 vintage (11-30-15 - Version 5.1.38).
Can we please have a newer connector?
Can we please have a newer connector?
ca...@restauratiemetkwaliteit.be
What drives me nuts is that I pay for this service and we get
1. no support
2. no feedback on the bugs and their expected timeframe for a solution
3. no solution
I think this attitude is very similar to the attitude that killed IBM.
I'm not gonna call it arrogance but it is very similar.
I really wonder if MS and Amazon are also so customer-unfriendly in their approach.
I thought the Google Cloud Platform was working to recover marketshare from Azure and AWS but this is certainly not the way it will happen
So PLEASSSE Google, how clear can we be : get your act together and start communicating with your customers !!!
1. no support
2. no feedback on the bugs and their expected timeframe for a solution
3. no solution
I think this attitude is very similar to the attitude that killed IBM.
I'm not gonna call it arrogance but it is very similar.
I really wonder if MS and Amazon are also so customer-unfriendly in their approach.
I thought the Google Cloud Platform was working to recover marketshare from Azure and AWS but this is certainly not the way it will happen
So PLEASSSE Google, how clear can we be : get your act together and start communicating with your customers !!!
[Deleted User] <[Deleted User]>
Hey folks at google, its time to upgrade the jdbc connector. Please look into the issue asap. I am not gonna downgrade my mysql version because of this.
[Deleted User] <[Deleted User]>
Please look at this ASAP.
Thank you,
Thank you,
[Deleted User] <[Deleted User]>
Looks like it is updated. Can any one check and confirm.
tg...@cameron.k12.wi.us
No, still fails.
Still TLS handshake error from offering only tls 1.1 in client handshake.
Still TLS handshake error from offering only tls 1.1 in client handshake.
[Deleted User] <[Deleted User]>
I confirm that it is working for me.
[Deleted User] <[Deleted User]>
So it seems like it connects with RDS mysql 8.0+ instance but not with self hosted mysql instance.
ca...@restauratiemetkwaliteit.be
RDS?
ha...@gmail.com
Not working here. Can you describe how is it working??
Im using AWS RDS MySQL 8.0.21 and cannot connect with the following Google Apps Script code:
var conn = Jdbc.getConnection("jdbc:mysql://SERVERNAME.rds.amazonaws.com:3306/MYDATABASE ", "USERNAME", "PASSWORD");
Any tips would be appreciated.
Thanks
Im using AWS RDS MySQL 8.0.21 and cannot connect with the following Google Apps Script code:
var conn = Jdbc.getConnection("jdbc:mysql://
Any tips would be appreciated.
Thanks
[Deleted User] <[Deleted User]>
Not sure, how it is working for AWS RDS. I am debugging it, will let you know if there is any update.
[Deleted User] <[Deleted User]>
Hi, Please append useSSL=false on your connection string and the connection is working. Eg.
jdbc:mysql://*.*.*..*:3306/dbname?useSSL=false
I hope this helps for people who are struggling with the issue.
jdbc:mysql://*.*.*..*:3306/dbname?useSSL=false
I hope this helps for people who are struggling with the issue.
li...@york.ac.uk
I would suggest people think very carefully before specifying useSSL=false outside of debugging scenarios.
This disables transport encryption between your application and the database (i.e. data in-flight will be visible on the network). Generally that would only be acceptable over a controlled private subnet.
This disables transport encryption between your application and the database (i.e. data in-flight will be visible on the network). Generally that would only be acceptable over a controlled private subnet.
mi...@seekwell.io
Since Google seems to have no plans on support MySQL 8, you can try https://seekwell.io/ instead (we support MySQL 8 and we're deeply integrated with Google Sheets)
cc...@gmail.com
Another workaround is Integromat (https://www.integromat.com/en ). The MySQL connector is working for us, connecting to RDS MySQL 8.0.11
pa...@fazwaz.com
nobody wants your paid crap stfu
ma...@jrmendonca.com.br
Still not working.
ma...@jrmendonca.com.br
Same issue here.
It doesn't connect to mySQL 8
It doesn't connect to mySQL 8
ha...@gmail.com
Unfortunately still stuck with this issue... I did check Integromat.com and at least for basic volumes it is free and works well connecting my Sheets to MySQL 8!!
But how come we cannot use the free native Google Sheets JDBC?? Are we so few so no one really cares? MySQL 8 is out from Apr 2018!
If anyone finds a solution, please post here...
Thanks
PS: By the way, niyotail on a previous post mentioned the useSSL=false worked for him, but it did not for me. See my version of the engine and config in one of my previous posts in case it helps you to understand your situation too.
But how come we cannot use the free native Google Sheets JDBC?? Are we so few so no one really cares? MySQL 8 is out from Apr 2018!
If anyone finds a solution, please post here...
Thanks
PS: By the way, niyotail on a previous post mentioned the useSSL=false worked for him, but it did not for me. See my version of the engine and config in one of my previous posts in case it helps you to understand your situation too.
[Deleted User] <[Deleted User]>
I'm gonna guess that most have chosen to use a different system or program such as the aforementioned Seekwell in order to work around this. Unfortunately, some of us have managers that are telling us these options are not acceptable. It truly would be ideal if Apps Script would make the appropriate connection to MySQL 8.0 without any third party involvement.
ca...@restauratiemetkwaliteit.be
This is a real scandal.
Nothing gets fixed, nothing gets done
And at the same time Google wonders why it's loosing market share to Amazon WS or Microsoft Azure
How can you be so stupid Google and not fix critical bugs like these
You'll be a dinosaur in no time
Nothing gets fixed, nothing gets done
And at the same time Google wonders why it's loosing market share to Amazon WS or Microsoft Azure
How can you be so stupid Google and not fix critical bugs like these
You'll be a dinosaur in no time
li...@york.ac.uk
Just posting back to this thread, since the issue hasn't even been acknowledged yet, as it looks like the connector has eventually been updated - I now have the following reported from google script on querying the connector, and it now seems to connect to a MySQL 8.0 instance:
MySQL Connector Java mysql-connector-java-5.1.49 ( Revision: ad86f36e100e104cd926c6b81c8cab9565750116 )
MySQL Connector Java mysql-connector-java-5.1.49 ( Revision: ad86f36e100e104cd926c6b81c8cab9565750116 )
pa...@fazwaz.com
Cheers, thanks for the update! Working for our mysql8 instance now as well.
er...@g2g-online.nl
Thanks for the update! It's working over here as well now :).
ha...@gmail.com
great news. 2 years 10months to get it solved.
ha...@gmail.com
by the way, in the meantime I moved away completely from GoogeSheets to implement my solution so its not useful anymore for me, but great that it is finally solved!
mi...@google.com
This issue has been fixed and you shouldn't be experiencing this anymore.
Therefore, I'll proceed to close this. If you start encountering this again, please create a new issue.
Description
-----------------------------------------------------------------------------------------------------------------------------
A short description of the issue:
Cannot connect to MySql Database version 8.0
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
function doGet(e)
{
var conn = Jdbc.getConnection('jdbc:mysql://########:3306/exponential_db', 'testing', 'over');
}
######### = my server IP...
What steps will reproduce the problem?
1. create a google app script and run the code shown...
What is the expected output? What do you see instead? If you see error messages, please provide them.
When I run in debug/ deployed web app - it fails with :
"Failed to establish a database connection. Check connection string, username and password. "
Please provide any additional information below.
I have successfully been able to Telnet and also install a MySql App in Google Chrome - both access the database successfully without issue....