"Cannot connect to MySQL server on 'Webserver IP" (10061)"

Hello,

I made a Ubuntu Web-Server and installed mariadb on it. Now i wanted to create a database table with heidisql. I added my server IP but i get the messag: "Cannot connect to MySQL server on 'Webserver IP" (10061)"

Firewall block ?

i am not sure. both of my computers, 100% of my connections are now doing this, while mysql workbench connected fine. connections that have been working for the past many months.

I get a similar error when connecting to localhost in HeidiSQL without first connecting in MySQL Workbench.

If you connect in Workbench first, can you then connect in HeidiSQL?

Note that this happens, for me, every time I reboot.

ah forgot about this: follow up time - for me, it was caused by hyper-v. when you enable it, it makes new virtual network adaptors, and then for some unholy reason it also makes virtual duplicates of all the ones you already have. heidisql was unable to navigate this dumpster fire to choose the correct interface, while mysql workbench was. once i right click disabled all the hyper-v interfaces in Network Connections, heidisql worked again.

heidi probably legit needs an interface selector since workbench was able to figure out which one actually works.

(im using it in ssh tunnel mode in this case. the ssh part worked. but either the local port forward was bound to a bad adapter or heidi was looking at the wrong one. it doesnt tell me much to know exactly how it went wrong, only that it was.)

Bob, this solved my problem too, thanks. Seems like an easy for for Heidi to rectify, no?

I'm curious: hyper-v creates multiple network interfaces on the same ip address? Or does it create interfaces for different ip's? HeidiSQL connection then points to an ip or to a hostname?

Bob, this solved my problem too, thanks. Seems like an easy for for Heidi to rectify, no?

i suspect no, because i figured it out because i found some other obscure networking problem. i suspect the only way to take care of it is to spend the time to actually setup hyper-v properly, which nobody does XD

(probably not easy i mean, its likely MySQL Workbench works by pure luck, considering the rest of the app is so bad it works by pure luck. the simple solution would be adding an interface dropdown on each connection i imagine.)

I don't have Hyper-V enabled yet it happens for me. Having said that, I'm 99% sure I updated Heidi last week & that, after a reboot over the weekend, I managed to connect in Heidi without Workbench being open - so it may be resolved, or could be coincidence or I could be mistaken on either point. I will likely restart my laptop over the next few days so will keep an eye on it and post the result here.

you are stuck in a network interface hellscape though? i think thats what did it for us. for example, a long time ago we were trying to play a game that only had LAN for multiplayer, trying all sorts of insane vpn things, had a super hard time getting it to work. eventually we figured out that in the windows network interface properties panel there is some metric value that more or less gets used by windows as a priority, where i think the lowest metric was like the interface it tried first when an app just asks for a connection without specifying what adaptor. once the wlan adaptor we had was the first pick the game worked.

i was suspecting that heidisql might be in that same boat. maybe workbench tries all the adaptors and keeps the first one that works, and heidi just tries the first and dies, im not sure.

It could be - but I am primarily a developer and know little-to-nothing about networks / hardware etc.. I know we've added exceptions to the firewall for Age of Empires 2 but that's the only time I've tampered with firewall settings. It is a work laptop with (in my opinion) far too much security (they've even disabled the sleep function so we can't go anywhere without shutting everything down) so there could be something forced on us by the company / IT team that has been preventing this from working.