Ads were blocked — no problem. But keep in mind that developing HeidiSQL,
user support and hosting takes time and money. You may want to
send a donation instead.
I want to make my own private server for World of Warcraft but I’ve got an issue on connecting with HeidiSQL. I keep getting this error:
SQL Error: can’t connect to MySQL server on ‘localhost’ (10061)
For as long as I know I’m not making any problems.
IP: localhost
User: root
Password: ascent
and I also start MySQL.bat before using HeidiSQL.
I’d really appreciate if someone could help me.
by the way I installed the HeidiSQL 4.0 from:
http://www.heidisql.com/download.php
I’ve only installed one thing, the «installer» part on the site. I hope that isn’t the problem.
Right, that is definitely not the problem
The problem is, your local MySQL server is not responding, I guess it is not runnin at all. See taskmanager and watch for mysqld.exe .
yes that one is on with around 200kb memory. Just don’t get it. I was looking for the solution for hours and didn’t understand what was wrong 
I hope you or anyone else knows a solution
ok i see a problem now. It says I don’t have a service called MySQL. Where can i download or install the service?
ah still doesn’t work. Found a service but still the same error.
ok this is the thing:
i’m following this tutorial:
http://www.youtube.com/watch?v=1y5KtoQqMrc
At 3:30 he starts to login on HeidiSQL.
When he connects he enters the server. At that point I don’t enter the server, but I get the error instead. Maybe this will get you an idea?
Aha now I found the solution :p
man what a stupid program.
I needed to FIRST run the service and THEN run the MySQL.bat.
Well thank you for your help anywaysat least someone answers my questions after all 
Don’t know what your mysql.bat should do, but it’s not some standard method to get MySQL running. Normally you start the server and then you can connect via any client like HeidiSQL.
darn smiled too fast. now it doesn’t work anymore. what server are you talking about?
when i open mysql.bat it says that mysql is running. i’m not used to such a things like mysql. I only play games
Well no problem to play games. That should not stop you from getting into MySQL or?
I meant the MySQL server. Try to do this:
— Start -> run -> cmd.exe
— Type this into the black DOS box:
mysql -hlocalhost -uroot -hascent<Enter>
— Post here what error you get
uh my computer can’t recognize mysql.
i get the same error as if i would write «asdfasfadsf» (some random letters)
well i wrote «mysql -hlocalhost -uroot -hascent» hope that was correct.
i guess mysql.bat is the server because it’s in the folder called Server, but he does not load completely. It says:
Please close this command only for Shutdown.
MySQL is running, don’t close this window.
Somehow before when i «found the solution» it showed more than the 2 lines.
Although this post is years old, just in case someone else is getting this error, as I recently did:
I unchecked the «compressed client/server protocol» checkbox and was able to connect. Not sure if that was the problem or not, because now I can check it and still log in fine, but that’s all I recall changing. Although I also logged into SSH using putty and tried «mysql -uUSER_NAME -p» to test the connection between when it wasn’t working and when it was, so that may have changed something as well.
It is alright now. I have a Norton antivirus from 2005 and it blocked most of the things I wanted to start. When I figured that out I turned off Norton and all worked fine. I have heard of other people also having issues with old Norton versions on recent computers. So if anyone still has got an old Norton antivirus, just delete it, download an other free antivirus and your worries are gone 
hi..I am getting the same error altough i tried the following
— Start -> run -> cmd.exe
mysql -hlocalhost -uroot -hascent
after this I am getting «It is not recognised as internal or exteral command, operable program or batch file»
Please help
Thanks
Man, this is of course because your mysql.exe is not located in your path environment. Just add the path and it should run. Additionally, you have two «-h» parameters which cannot be correct as h means «Host». I guess «ascent» is your password — if so that must be prefixed by «-p», not «-h»:
c:\Program Files\MySQL Server XYZ\bin\mysql.exe -hlocalhost -uroot -pascent
Apart from that, you should NEVER post any password in a public forum — that’s totally dumb.
Thanks for the prompt response…what I posted above was the information as per your earlier post posted on 09 Jan 10..so I am not sharing my detailsI fixed the problem by reinstalling the whole thing again saving my data files..I guess some thing was missing…now its working..Thanks for you help
I figured of the problem for those who are trying to make a WoW Private Server…
This NEEDS to be open while you are using it…
Go to Corruption Productions BlizzPack/Server/MySQL.exe (Or Windows Batch File)
As long as you have that open… Your SQL should work…
If it doesn’t Message me on Youtube because I’m leaving this forum and I’m not coming back…
Youtube Username: Yournothawt
i get the same error i restart the server
bet it steel not working 
ERROR 2005 (HY000): Unknown MySQL server host ‘ascent’ (11001)
Please login to leave a reply, or register at first.
This page uses cookies to show you non-personalized advertising and server usage statistic diagrams.
I have a Raspberry Pi (first model) I use as a server. I followed a tutorial and installed Apache2, MySQL, Phpmyadmin etc.
I have also set up a ddns for my home network to be able to connect to it wherever I am, and of course forwarded the necessary ports.
At first everything worked wonders.
- I could connect to the database using phpmyadmin by navigating to
adress/phpmyadminfrom any network. - I could also use HeidiSQL to connect to the database, again from any network.
The MySQL version I had at this time was v5.5. I wanted a feature available on v5.6 but this version was not available on my RPi (ARMv61). Instead it seemed like MariaDB should do the trick. So I updated to MariaDB using the command:
sudo aptitude install mariadb-server
Now I am not able to connect through HeidiSQL anymore, Phpmyadmin still works though from any network just like previously. Trying to connect with HeidiSQL I get the output (no matter what username/password i try):
Can’t connect to MySQL server on ‘adress’ (10061)’
mysql -V gives output:
mysql Ver 15.1 Distrib 10.0.27-MariaDB, for debian-linux-gnueabihf (armv7l) using readline 5.2
My RPi info is
Linux redface 4.4.26+ #915 Thu Oct 20 17:02:14 BST 2016 armv6l GNU/Linux
The user privileges are available in the image below
How can I connect to the database again using HeidiSQL? Have I missed something with the user privileges?
With phpmyadmin I use the username root
Обновлено
Вопрос:
У меня есть малина Pi (первая модель), которую я использую в качестве сервера. Я последовал за учебником и установил Apache2, MySQL, Phpmyadmin и т.д.
Я также создал ddns для своей домашней сети, чтобы иметь возможность подключаться к нему, где бы я ни был, и, конечно же, перенаправлял необходимые порты.
Сначала все делало чудеса.
- Я мог подключиться к базе данных с помощью phpmyadmin, перейдя по
adress/phpmyadminиз любой сети. - Я также могу использовать HeidiSQL для подключения к базе данных, снова из любой сети.
Версия MySQL, которую я имел в это время, была v5.5. Мне нужна функция, доступная на v5.6, но эта версия не была доступна на моем RPi (ARMv61). Вместо этого казалось, что MariaDB должен сделать трюк. Поэтому я обновился до MariaDB, используя команду:
sudo aptitude install mariadb-server
Теперь я больше не могу подключиться через HeidiSQL, Phpmyadmin все еще работает, хотя и из любой сети, как и раньше. Попытка связаться с HeidiSQL. Я получаю вывод (независимо от того, какое имя пользователя и пароль я пытаюсь):
Не удается подключиться к серверу MySQL на ‘адрес’ (10061) ‘
mysql -V дает результат:
mysql Ver 15.1 Распространение 10.0.27-MariaDB для debian-linux-gnueabihf (armv7l) с использованием readline 5.2
Моя информация RPi
Linux redface 4.4. 26+ # 915 Чт окт 20 17:02:14 BST 2016 armv6l GNU/Linux
Пользовательские привилегии доступны на изображении ниже
Как подключиться к базе данных снова с помощью HeidiSQL? Я пропустил что-то с привилегиями пользователя?
С phpmyadmin я использую имя пользователя root
Лучший ответ:
Эта конкретная ошибка касается не разрешений.
Код (10061) 10061 (10061) – WSAECONNREFUSED – код ошибки сокета Windows для Connection refused, не путать с “access denied”.
Отклонение соединения обычно означает, что служба не прослушивает целевой IP-адрес и порт. MariaDB не прослушивает 0.0.0.0:3306.
mysql -V сообщает только установленную версию клиента – он ничего не говорит о сервере MariaDB.
Доступ к phpMyAdmin не говорит вам ничего, потому что с ним вы не разговариваете с сервером базы данных удаленно – вы разговариваете с вашим веб-сервером удаленно, а ваш веб-сервер запускает код, который ведет переговоры с базой данных локально из одного и того же компьютера и часто использует другой механизм доступа к серверу, который не является TCP/IP.
Проверьте файл конфигурации для прокомментированного bind_address=0.0.0.0 или аналогичного.
https://mariadb.com/kb/en/mariadb/configuring-mariadb-for-remote-client-access/
After creating a new mySQL server within an Ubuntu guest OS running on VirtualBox, (how is that for a mouthful?) I wanted to connect to the server with HeidiSQL, my toolbox of choice when dealing with basic SQL operations. I expect that I would have the same problems attempting to connect with similar client software, such as mySQL Workbench or PHPmyAdmin.
The symptoms of the problem showed up in an error message, generated by HeidiSQL:
Connect Error (2003) Can‘t connect to MySQL server on ‘192.168.219.107‘ (10061)
So, more or less in order, I did the following:
1. Create a mySQL user with an identical name and password as the Ubuntu user account. To connect to mySQL, you need to have two valid accounts: a.) a valid Linux user account, and b.) a valid mySQL user account. On Ubuntu, these need to be same….because you only get one chance to pass through a name and password when logging into a server from HeidiSQL. This is done by logging into the mySQL client on the Ubuntu box, and performing the following:
GRANT ALL PRIVILEGES ON *.* TO ‘username‘@’localhost’ IDENTIFIED BY ‘password‘ WITH GRANT OPTION;
GRANT ALL PRIVILEGES ON *.* TO ‘username‘@’%’ IDENTIFIED BY ‘password‘ WITH GRANT OPTION;
Exit the mySQL client, and then reload the grant tables, using the mySQL root user and password
mysqladmin -u root -prootpassword reload
Note that the both the user names and password are case-sensitive, and the mySQL user’s name and password must be identical to the ubuntu user’s name and password for Heidi to be able to log in.
2. In VirtualBox, be sure that the network settings for your network card are for a bridged adapter. What this does is it makes the VM act like another machine on your current network. The VirtualBox default is to create its own network and subnet which are inaccessible from the host machine. (but see note #1 below)
3. Once you’ve taken care of the above items, restart the VM, and log in at the console. You need to edit the mySQL configuration file to reflect the new IP address of the VM. Log into the VM. Usually the opening screen will show the current IP address, in the line:
IP address for eth0: 192.168.219.107.
If you miss it or need to find it again, just run
ifconfig | grep “inet addr”
This will probably show at least two lines. The first one is the current IP address.
inet addr: 192168.219.107 Bcast:192.168.219.255 Mask:255.255.2550
inet addr: 128.0.0.1 Mask 255.0.0.0
Now that you know the address, you can add it to mySQL configuration file:
sudo nano /etc/mysql/my.cnf
Scroll down in this file until you find an entry for the bind address. This will look something like:
bind-address = 127.0.0.1
Change this so it it listens on the address of your VM. I just comment out the bind-address line, and add the new line:
#bind-address = 127.0.0.1
bind-address = 192.168.219.107
Restart the machine.
sudo shutdown -r now
This reloads everything, including the mySQL daemon so that it listens on the new IP address.
That’s it. You should be able to log in with Heidi now.
Notes:
1. You could probably leave the default networking setting in place, (it is NAT), and the VM will be assigned a NAT address along the lines of 10.0.2.15. You’d still probably want to edit the mySQL file to reflect this address, and you might also want to make sure that you forward the mySQL port 3306. I just haven’t tested this, so that I can’t vouch that it will work.
2. Of course, in a production situation, you’ll want to choose a fixed IP address for the network address. This might involve your main router and firewall, so you may need to discuss this with the sys admins.
Anyway, now that I’ve actually got this thing running…I’ve got to get back to mySQL!
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
charles-001 opened this issue
Jul 11, 2019
· 16 comments
Comments
Steps to reproduce this issue
- Configure HeidiSQL to use MySQL SSH tunnel
- Use PuTTY v0.71
- Receive error «Can’t connect to MySQL server on ‘127.0.0.1’ (10061)
Current behavior
HeidiSQL doesn’t work with PuTTY v0.71. I spent a good amount of time troubleshooting this issue because my company is moving towards an SSH solution and I had to figure out what the root issue was. Other previous versions of PuTTY work with HeidiSQL.
Also, this isn’t directly related but setting plink.exe timeout makes the entire connection take that much time regardless if it connects before specified timeout.
Expected behavior
It should connect
Possible solution
Not sure what the root issue here is. Seems like HeidiSQL isn’t correctly communicating with plink because of a change in v0.71.
Environment
- HeidiSQL version:
10.2.0.5621 - Database system and version:
5.7.22 - Operating system:
Windows 10
charles-001
changed the title
MySQL SSH Tunnel Issue
MySQL SSH Tunnel Issue — plink v0.71 incompatibility
Jul 11, 2019
Please post the plink command line from the log panel here, of course with anonymized credentials. For me, plink 0.71 works good. My command line looks like this one:
C:\Software\plink.exe -ssh myuser@myhost -P 22 -i «C:\Users\becker.ssh\mykey.ppk» -N -L 3307:127.0.0.1:3306
Connecting to $server via Percona (SSH tunnel), username $db_user, using password: Yes …
SSL parameters successfully set.
Attempt to create plink.exe process, waiting 6s for response …
C:\Program Files\PuTTY\plink.exe -ssh $ssh_user@$ssh_server -P 22 -i «D:\Users\Desktop\key.ppk» -N -L 3306:$database_server:3306
PLink: Using username «$ssh_user»
Can’t connect to MySQL server on ‘127.0.0.1’ (10061)
Closing plink.exe process #12384 …
I do not see «PLink: Using username «$ssh_user»» in the log panel when connecting with PLink v0.70 FYI
That «Using username…» is just a new output in the new plink version, should not matter.
Did you notice your local SSH tunnel port is set to 3306? The one in front of $database_server. You should try 3307 in the «SSH tunne» tab, at least if you have a local MySQL/MariaDB server installed.
I’ve tried numerous ports. Heidi will increment the port by 1 if it’s in-use anyway from what I’ve noticed.
Can you please open a command prompt and fire that plink command by hand, to see what happens? And afterwards try to connect with Heidi on 127.0.0.1 / 3306.
It works fine if done manually by command prompt.
And Heidi does not say «Can’t connect to MySQL server on ‘127.0.0.1’» with that plink in a command prompt?
If so, please check via taskmgr if the plink.exe process runs when you try again with Heidi’s built-in plink setup.
Whenever I ran plink via command prompt, it creates the tunnel. Here’s the verbose log output:
We claim version: SSH-2.0-PuTTY_Release_0.71
Remote version: SSH-2.0-SSHD-CORE-1.7.0
Using SSH protocol version 2
No GSSAPI security context available
Doing ECDH key exchange with curve nistp256 and hash SHA-256 (unaccelerated)
Host key fingerprint is:
ssh-rsa 2048 $hash
Initialised AES-256 SDCTR (AES-NI accelerated) outbound encryption
Initialised HMAC-SHA-256 (unaccelerated) outbound MAC algorithm
Initialised AES-256 SDCTR (AES-NI accelerated) inbound encryption
Initialised HMAC-SHA-256 (unaccelerated) inbound MAC algorithm
Reading key file «D:\Users\Desktop\key.ppk»
Using username «sdfsfsdf@server».
Offered public key
Offer of public key accepted
Authenticating with public key «imported-openssh-key»
Sent public key signature
Access granted
Local port 3306 forwarding to $db_server:3306
I can then connect with Heidi on 127.0.0.1:3306 with no issue:
Opening connection to $db_server :3306 for forwarding from 127.0.0.1:51774
Forwarded port closed
Any update on this, @ansgarbecker? Would like to be able to use latest PuTTY version.
No changes here yet.
But could you please verify this is still an issue with the latest build — 5621 is a bit old already.
Also, your plink output is different from mine — mine starts with a «Looking up host …» line. That may be due to you using a key which I don’t. Is that the original plink.exe from https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html ?
Ah and please activate «Debug messages» in Preferences > Logging before you try to connect. So we probably get some more details.
So.. after upgrading to to 10.2.0.5599, I no longer have connection issues. That’s strange if it works when you didn’t change anything specifically for it. I’ll have others test and see if it works for them as well.
Thanks!
Ok, 5599 is the 10.2 release, but older than 5621 (the one you reported above), so there may be now other things not working for you.
Would be nice if you once again update, but to the latest build, through Help > Check for updates.
I’m now on 10.2.0.5678 and it still works. Will need to confirm w/ other people to see if it works for them as well.
Didn’t expect that, but.. cool
So I guess I can close this.
Thanks for your feedback!
