Lost connection to MySQL server at reading initial communication packet system error 0

Question

I am getting error       Lost connection to MySQL server at  reading initial communication packet  system error  0    while I am going to connect my db   If I am using localhost everything is working fine  But when I am using my live IP address like below  it s getting error   mysql connect  202 131 xxx 106 xxxx    xxxx    xxxxx   or die mysql error

User · Answer

The problem for me was that DNS queries were blocked by the FW within the subnet  The solution was to disable DNS lookups within MySQL

User · Answer

For me the config file was found   etc mysql mysql conf d mysqld cnf  commenting out bind address did the trick   As we can see here   Instead of skip-networking the default is now to listen only on  localhost which is more compatible and is not less secure

User · Answer

I had identical problem  To fix it I just changed host from localhost 3306 to just localhost  So error may acour when You sepcify unproper port for connection  It s better to leave it default

User · Answer

I faced the same problem  I checked and tried to set AllowTcpForwarding Yes but it was missing in my sshd config so no help I didn t change sshd config or my cnf  Make sure the ssh hostname is NOT the same with the mysql hostname use localhost    In workbench  choose   to add new connection and set the following    connection method  standard TCP IP over SSH  SSH Hostname  192 168 0 50 22  replace remote SSH server IP and port optional    SSH Username  sshuser   You can set password or add at the prompt MYSQL Hostname  localhost or 127 0 0 1 MYSQL Server port 3306 You can set password or add at the prompt   Test connection  It should be successful then hit OK Viola

User · Answer

Firewalld blocks the IP address  so to give access  use these commands   firewall-cmd --permanent --zone trusted --add-source YOUR IP 32  firewall-cmd --permanent --zone trusted --add-port 3306 tcp  firewall-cmd  --reload

User · Answer

I just set up mysql on a windows box  I got the OP s error when trying to connect with the Navicat MySql client on the same box  I had to specify 127 0 0 1 as the host  and that got it   localhost  or the servers actual ip address both did not work

User · Answer

Limited disk space can cause to this error   Check your disk space     df -h   Try to increase the space if there are 100  used disks    In my case  I have Vagrant  8 0 1  box  Ubuntu 16 04  My mysql disk capacity was 10GB  I increased it to 20GB    sudo lvextend -L20G -r  dev mapper homestead--vg-mysql--master   Then restart mysql    sudo service mysql restart

User · Answer

1  Allow remote connect to MySQL  Edit file    gt sudo nano  etc mysql my cnf   Comment line    bind-address         127 0 0 1   Restart MySQL    gt sudo service mysql restart   2  Create user for remote connection    gt mysql -uroot -p  CREATE USER  developer   localhost  IDENTIFIED BY  dev password   CREATE USER  developer      IDENTIFIED BY  dev password    GRANT ALL ON     TO  developer   localhost   GRANT ALL ON     TO  developer         3  In my case I need to connect remotely from Windows to VirtualBox machine with Ubuntu  So I need to allow port 3306 in iptables    gt iptables -A INPUT -i eth0 -p tcp -m tcp --dport 3306 -j ACCEPT

User · Answer

Had this problem when setting up a new slave server  Found it was the slave server IP address was missing from the master server  etc hosts allow file  Added the IP address and it let me connect to the master server   Note that I use hosts allow and hosts deny to control access

User · Answer

This error occurred to me while trying to connect to the Google Cloud SQL using MySQL Workbench 6 3   After a little research I found that my IP address has been changed by the internet provider and he was not allowed in the Cloud SQL   I authorized it and went back to work

User · Answer

I had the same issue installing MySQL docker image then trying to connect from WSL2 MySQL client  As it was stated in the accepted answer that it should be a firewall issue  in my case this error was caused due to not allowing docker for windows to communicate to private network  I changed the settings on  quot Firewall  amp  network protection quot    quot allow an app through firewall quot    quot change settings quot   need administrator rights  and allowed  quot Docker desktop backend quot  to connect to private network

User · Answer

I had port 3306 in Docker container but in Dockerfile it was 33060  I edited the port in Docker container to 33060  Must have been added to the Dockerfile ENV MYSQL ROOT HOST 172 17 0 1

User · Answer

I am trying to connect my db docker container on Ubuntu 18 04  same problem    First check your device by run nmcli dev to check if device docker0 is connected   If it is not connected  try to restart docker service   sudo service docker restart

User · Answer

Open mysql configuration file named my cnf and try to find  bind-address   here replace the setting  127 0 0 1 OR localhost  with your live server ip  the ip you are using in mysql connect function   This will solve the problem definitely   Thanks

User · Answer

I tried make a telnet over remote server on port 3306  The error message is clear Host  x x x x  is blocked because of many connection errors  unblock with  mysqladmin flush-hosts Connection closed by foreign host  As root at server mysqladmin flush-hosts worked at all

User · Answer

I had the same error when using localhost  I restarted the MySQL service and it worked fine

User · Answer

If bind-address is not present in your configuration file and mysql is hosted on AWS instance  please check your security group  In ideal conditions  the inbound rules should accept all connection from port 3306 and outbound rule should respond back to all valid IPs

User · Answer

in my case  I had ALL  ALL in hosts deny   Changing this to ALL  PARANOID solved my problem when connecting over ssh

User · Answer

The problem on my case was MySQL being bind only to the lo on linux  in order to solve the problem i have edited the my cnf  found at  etc mysql my cnf  removing the line bind-address 127 0 0 1  this allows mysql to bind to any network interface

User · Answer

One more reason     I ran into an Ubuntu server where everything was customized and could not connect because of that same error   This setting was inside  etc ssh sshd config  PermitTunnel no   After turning into  PermitTunnel yes   I was able to connect remotely to my MySQL DB

User · Answer

The problem was quite stupid for me   I used to get the same issue on AWS EC2 Ubuntu machine  MariaDB is installed locally for the time being   so I tried to make SSH tunneling  and had the same issue  So I tried to ssh tunnel over terminal   ssh -L13306 127 0 0 1 3306 root ip address -i my private key pem   And it told me this      Please login as the user  ubuntu  rather than the user  root     I changed ssh user from root to ubuntu  just like my ssh config  and it connected just fine   So check your SSH connecting user   I oversaw this  so this too half an hour of my time  so I hope this will be useful for you

User · Answer

Someone here suggests that it might be a firewall problem      I have just had this problem and found it was my firewall  I use PCTools Firewall Plus and it wasn t allowing full access to MySQL  Once I changed that it was fine  Hope that helps    Could that be it   Also  someone here suggests that it might be because the MySQL server is bound to the loop-back IP  127 0 0 1   localhost  which effectively cuts you off from connecting from  outside    If this is the case  you need to upload the script to the webserver  which is probably also running the MySQL server  and keep your server host as  localhost

User · Answer

I have done below 3 steps then working for me   bind-address    quot YOUR MACHINE IP quot  in my cnf file at  etc my cnf  Restart service by command   service mysql restart  GRANT ALL PRIVILEGES ON yourDB   TO  username   YOUR APPLICATION IP  IDENTIFIED BY  YOUR PASSWORD  WITH GRANT OPTION

User · Answer

I ran into this exact same error when connecting from MySQL workbench   Here s how I fixed it   My  etc my cnf configuration file had the bind-address value set to the server s IP address   This had to be done to setup replication   Anyway  I solved it by doing two things    create a user that can be used to connect from the bind address in the my cnf file   e g    CREATE USER  username   bind-address  IDENTIFIED BY  password   GRANT ALL PRIVILEGES ON schemaname   TO  username   bind-address   FLUSH PRIVILEGES     change the MySQL hostname value in the connection details in MySQL workbench to match the bind-address

User · Answer

If you face this erorr connecting from remote  go to remote mysql option in cpanel and then add   in Host    wildcard is allowed

User · Answer

Ran into this same issue  Bind Address back and forth to no avail  Solution for me was flushing privileges    mysql gt  FLUSH PRIVILEGES

User · Answer

I had this problem connecting to my MySQL server via a proxy server  In my case it was working fine the week prior  and I didn t make any changes to my connection or server settings  On a hunch  I decided to SSH into the proxy server to see if it was still working  and as soon as I did I was prompted to update my UNIX password  because it had expired  Resetting the password allowed me to connect again via the proxy

User · Answer

I had this problem and it ended up being the prior sys admin changed the port MySQL was running on  MySQL Workbench was trying to connect to the default 3306 but the server was running on 20300

User · Answer

Database directory read-write permission also a problem i found  Just make sure your application is able to rw files on db location  Try chmod 777 for testing

User · Answer

The error means that it didn t receive a response from the port it expected to find the server on  The causes range from contacting the wrong machine  For one of a number of reasons  to the server not being on the expected port   Check which port your server is bound to in  etc mysql my cnf  Does that correspond to what is in your connect statement  If they match then try connecting with mysql from the server itself and from the command line of the machine where you are running the client  If it works form one place and not another then you may have a firewall   router configuration issue

User · Answer

For me setting bind-address   0 0 0 0 in mysql my cnf worked  It basically listens to all addresses  but still one port  then   And don t forget restart your server  systemctl restart mysql

User · Answer

In my case it was the university wifi blocking port 3306   I was able to connect by using a mobile hotspot   Change to a mobile hotspot or another network  and if it works there  then you know that original network is blocking port 3306   If you get the same error on more than 1 network  then you know it s specific to your machine

User · Answer

I just had the same problem  but in my case I solved it with     service mysqld start

User · Answer

When connecting to Mysql remotely  I got the error  I had this warning in  var log mysqld log    Warning  IP address  X X X X  could not be resolved  Temporary failure in name resolution   I just added this line to  etc hosts file   X X X X some name   Problem solved  Not using skip-name-resolve caused some errors in my local app when connecting to MySQL

User · Answer

I had a similar error  connecting to MYSQL on aws via MYSql Workbench   I used to connect fine before and all of a sudden it stopped working and just wouldn t work again   My connection was via SSH protected by keyfile   Turns out I was timing out  So I increased the SQL connection timeout to 30 secs  from default 10  and was good to go again  things to try  if you re in a similar setup    Can you ssh directly from terminal to the server  detects issues with key file permissions etc   Can you then through terminal connect to MySQL with the same user pwd using something like mysql -u  username  -p  database   This will check for user rights issues etc  if both of those work then your parameters are not the problem and maybe same timeout issue like me  except it never said timeout error  but rather asked to check for permissions etc

[php] Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Examples related to php

Examples related to mysql