I'm trying connect de MYSQL plugin (zapier) in my RDS Database (aws), but zapier return a error message: "authentication failed: Could not connect with **** and provided password. The response we got from the server is included below for debugging purposes. 255"
I cant find a solution for this error code.
My user, host and password are correct. And the IP 18.104.22.168/32 are enabled in my Security Group. In other integration products, the plugin works.
Best answer by DanversView original
@pedropsb - Before we dive in more into your issue, would you be able to reconnect your app in your My Apps? Please let us know what the outcome was and we’ll go from there. Thanks!
I'm tried again, but the result can't change: "
authentication failed: Could not connect with ***** and provided password. The response we got from the server is included below for debugging purposes. 255"
@pedropsb - Our support team will be with you shortly about the error. Please watch for their outreach in your inbox. Thanks!
In this case, the issue was the version of MySQL being used. Here’s what our Support Team had to say:
Right now, it would only be possible for Zapier to connect with a database running an earlier version of MySQL. We do have a feature request open to add compatibility with later versions, let us know if you’d like to be added to that feature request!
Can you please also add me to the feature request as well. I am also struggling with the same.
Guys, this feature is important for us as well. Please, add us to this feature request.
We've been using Zapier for quite a long time. We upgraded our database to MySQL v8.0 and we lost a bunch of our automations performed using ZAPIER.
Does anyone know any workaround?
@Maaz and @Tiago, from Cloudia.com.br!
I’ve gone and added you to the feature request, so you’ll receive an email notification when this has been implemented.
Yes please add me to the list as well. support for mysql 8+ is critical to our organization.
We have the same issue,
would be great if you add us as well.
Our engine version is: 8.0.20
I’m stuck currently and looking at ways to integrate with 8
@Siggi! Thanks for your message, I’ve added you to the feature request as well.
I’ve added you to the list of affected users. I don’t have an ETA on when this will be added, I’m sorry about that.
add me too please
@MyVirtuaLab and @Franck&Sydney - You’ve been added to the report list. Thanks!
The only zaps we are using rely on MySQL connectivity. When we were forced to upgrade a few days ago for security reasons everything stopped working. Now I’m going to have to turn off my plan unless there is some kind of workaround for this.
Has there been an update on this feature?We need this as well.
Welcome to the Community,
I’ve added you to the list of affected users. We’ll be in touch by email as soon as it’s resolved.
I don’t have an update on when this will be added but in the meantime, there is a workaround a user shared with us that you may find useful:
"We've set up a workaround for the integration using an SQL proxy, so this issue no longer has the highest priority. It would still help a lot if it were resolved so we can ditch the proxy again.
Our database is configured with "defaultauthenticationplugin=mysqlnativepassword" to ensure backward compatibility, so the connection issue cannot be caused by the authentication protocol itself. I suspect it is caused by the queries it performs after login (it selects @@txisolation which has been removed in MySQL 8.0). Remapping it via our proxy did the trick"
Please do let us know if that helps! :)