Forum Discussion
DataSource.Error: MySQL: Host is blocked because of many connection errors
Advocate IIHi,
Has anyone found decent solution for this problem? From a security perspective it isnt recommended to have too many max_conect_errors. The way around is to set up a scheduled task to flush, but again seems to be a patch then a fix. Any recommendations? Possibly a different more resilient gateway?
We're hitting the same issue with dataset refreshing from app.powerbi.com, through an on-premises gateway and into our MySQL database. We've increased the max_connection_errors and it doesn't help. It seems that Power BI sometimes insists on trying to connect without credentials and we get the "Unauthenticated User" connections on the MySQL side. We usually end up with 6 or more and then the dataset refresh fails. We'll try the on-demand refresh repeatedly and continue to see 1 or 2 authenticated connections with the correct credentials, and a smattering of "Unauthenticated User" connections as well. Again, the refresh fails.
Eventually, after attemping the on-demand refresh multiple times, we'll finally see ONLY authenticated connections on the MySQL side and no "Unauthenticated User" connections. Only then does the refresh completely successfully. And, just to clarify, this is with zero changes to our Power BI settings, Gateway, credentials, flushing of MySQL hosts, etc. It's stricly just retrying over and over until Power BI finally stops sending unauthenticated requests.
I definitely feel like this is an issue within PowerBI itself and it's causing us daily frustartion. Would appreciate any additional ideas. Someone mention turning on tracing. Is that done in Power BI desktop or via the cloud app?