Forum Discussion

Hike_N's avatar
Hike_N
Regular Visitor
10 years ago

DataSource.Error: MySQL: Host is blocked because of many connection errors

  I'm trying to connect to Power BI and receiving the following error.   DataSource.Error: MySQL: Host 'xxx.xx.xxx.xx' is blocked because of many connection errors; unblock with 'mysqladmin flush-...
Anonymous's avatar
Anonymous
Not applicable
9 years ago

I have contacted Microsoft Support about thsi issue and they said that they are aware of it, however they do not have a solution.

What we did internally is set up a periodic job to flush the hosts of the server automatically. Did not have any issues since.

Anonymous's avatar
Anonymous
Not applicable
9 years ago

Hi everybody,

I'm having the same problem that It's expose on this post: every few days my online reports give me this error when refresh.

I have some PowerBI online dashboards conected to a mysql db by Personal Gateway.

Any news about?

Thanks!

  • pbiuser31's avatar
    pbiuser31
    New Member
    9 years ago

    we're experiencing same issue using the On-premise data gateway when trying to sync from a local MySQL database.

     

    We used some 3rd party software to monitor the connections of the MySQL database and what we noticed is that every time the On-prem data gateway attempted a sync, it would log in correctly with the configured Power BI user, but also would make an unauthenticated user attempt.

     

    Because each unauthenticated user attempt counts towards the MySQL connection error, that's what will eventually cause MySQL to stop accepting any connection and give the error to FLUSH HOSTS.

     

    A dangerous and temporary fix is to change the max connection error flag on the MySQL database to 10,000... but this is far from ideal...

     

    • domaky's avatar
      domaky
      Regular Visitor
      8 years ago

      Hi all,

       

      I see the last entry is already a few months old. Did anybody find a fix for the problem? Because I encounter exactly the same issue when connecting to our (on premise) mysql database. And I agree : setting the max connection error flag to 10.000 is not a good solution. 

      So if you happen to know a better way to solve the problem, your help would be greatly appriciated.

       

      Thanks,

       

      Martin