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-hosts'
Message=Host 'xxx.xx.xxx.xx' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
I'm using amazon rds. I did flush my hosts and even rebooted the rds instance.
Turn on Tracing by going to File | Options and settings | Options | Diagnostics and click Tracing checkbox. Generate the error and then click the smiley face icon to send a frown and include screen shot, trace logs, etc.
So in my opinion, the first thing before "unblock" is to analysis the failed connections, I don't know about MySQL but I think there should be any log feature indicating the failed connection details.
Do you connect to Amazon RDS via "getdata"->"database"->"MySQL" and and install a gateway? When saying refresh, if you schedule the refresh through a gateway, as per the bold part of the quoted, try to monitor the connections from the server where the gateway is hosted in your MySQL database. By the way, have you confirmed that the database credential is set up correctly? I doubt the invalid crendential keeps failing the connection to your RDS from gateway.
I'm having the same exact problem. The connection starts working again after I ask the admins to flush the hosts, but now it's happening once every few days (I'm sure the credentials are correct). I'll have them check out the logs, but maybe there is something on the Power BI side that I could do?
I'm connecting to hosted MySQL through Power BI desktop which works perfect, but publishing to Power BI on a scheduled refresh is nothing but a nightmare at the moment - having the same issue as below.
I asked the sys admins to increase the MySQL server connection threshold, so didn't have any problems ever since.
Make sure you have plenty of RAM and a powerful CPU on the server that has Enterprise gateway running. After I monitored resource usage, it was apparent that it was struggling with RAM, so that could be an option you could check.