Lots of things to say here:
First: you didn't state what OS this is all being done on (specifically the server side -- I don't care about the client). My spidey sense tells me probably Windows, but you need to disclose this.
Secondly: MySQL Workbench is not MySQL Server. Workbench is intended to help you create SQL queries and do "DBA-like things" -- it is not the actual MySQL server itself. This may be your entire problem. I don't know.
Thirdly: don't let anyone tell you "is it a MySQL credentials thing? Maybe your username is wrong" -- the error clearly shows that you cannot establish a TCP connection to
http://www.wikidirt.org:3306. Wrong credentials result in a different error.
Fourthly: if you're absolutely certain you've installed and run MySQL server, then the troubleshooting process for this is remarkably easy:
1. Make sure
http://www.wikidirt.org resolves to the correct IP address of the server. If it doesn't, you need to talk to whoever manages the DNS for the wikidirt.org domain -- that's probably you, or your hosting provider.
2. Make sure mysqld is running on the
http://www.wikidirt.org server. On UNIX/Linux there's probably an rc.d, init.d, init (Upstart), or systemd script for this -- ask your hosting provider (esp. if CPanel is involved). On Windows there's probably a service for this (see
sc query).
3. If so, make sure it's listening on port 3306, bound to either INADDR_ANY (any IP address, e.g. * or 0.0.0.0) or to the IP address known as
http://www.wikidirt.org. Common tools for this on UNIX/Linux are
netstat (
netstat -nl or
netstat -an | grep 3306),
sockstat, or
ss. Common tools for this on Windows are
netstat -anb (you get to manually sift through output; Microsoft didn't provide output in such a way that FINDSTR works with it). Here's an example entry on Windows XP, showing that Skype.exe is listening on TCP port 65483. Windows Vista onward may have this formatted differently:
Code:
TCP 0.0.0.0:65483 0.0.0.0:0 LISTENING 6088
[Skype.exe]
4. The
http://www.wikidirt.org server uses a firewall and doesn't allow inbound connections to TCP port 3306. Now, let's talk about this in length, because it absolutely deserves mentioning: if
http://www.wikidirt.org is a server somewhere on the Internet, and you're trying to connect to it's mysqld directly from, say, some software on your desktop:
you do not want to be opening up TCP port 3306 on the server to the Internet. I repeat: DO NOT DO THIS. Just don't. Don't let MySQL's support of SSL make you think it's a good idea either. Just don't do it. I cannot stress this enough.
So in this case, you might be asking: how do you end up getting a desktop client to connect to mysqld running on a server somewhere? The answer is: SSH port forward / tunnel. You do not need a VPN for this (do not let anyone tell you otherwise). The configuration depends on whether or not
http://www.wikidirt.org is a UNIX/Linux machine; there are SSH servers for Windows but I have basically no experience with them. All you need is something like PuTTY for this. Here's an example:
http://howto.ccs.neu.edu/howto/windows/ ... ith-putty/The only difference compared to that screenshot is for Source port pick 3306, and for Destination pick 127.0.0.1:3306 (trust me! This actually refers to the server side of things, believe it or not).
You can also refer to this, which is the same thing just with different port numbers (you don't have to use 49900 -- that guy just picked an arbitrary port number to bind to locally, while using 3306 locally is perfectly OK):
http://katsande.com/ssh-port-forwarding ... sing-puttyWhat this will do: when SSH'ing to the server, it'll open up a local listening TCP socket on your workstation -- listening on TCP port 3306 -- and any packets going to port 3306 on your local machine will go "through" the SSH tunnel (fully encrypted) over to the server. On the server side, the SSH server is simultaneously tying that connection to 127.0.0.1 (itself) TCP port 3306, which is the mysqld server.
Then, on the MySQL client side (Workbench, etc.), you connect to 127.0.0.1:3306 (really).
Just remember that you'll only be able to connect to mysqld when that PuTTY session is up, and if you have utilities using the SSH tunnel and you close PuTTY, well, I'd rather not talk about what happens (sometimes PuTTY WILL close, other times it'll hang/get "stuck" until the clients close their connections, other times it'll close out fully and the clients will break with a socket error. It just varies. PuTTY's behaviour isn't consistent here and don't worry about it -- just remember connection is only up if PuTTY is running first!)
Let me know where I can send a bill for my time. ;-)
And I cannot help past this point. If you need assistance, talk to your hosting provider! That's what you pay them for!