Remote MySQL Access Error--STUMPED--HELP!!!

[DivaVocals]

I use SQLYog Enterprise 64 to manage many of my MySQL tasks.. I have NEVER had any issues using this tool with any host until now.. Client is hosted with SiteGround. When I initially took a backup of the client's site, I grabbed a copy of the DB using remote SQL as usual.. Now that I need to make some final changes to the live site in preparation for pushing my changes to the live site, I am unable to connect to the database using remote SQL.

When I try to connect to a remote MySQL database from my mySQL client software, I get “ERROR 1130: Host is not allowed to connect to this MySQL server”

The error I am getting appears to imply that something on Siteground's end needs to be modified.. Found this article which seems on point.. http://www.thegeekstuff.com/2010/08/...nt-connection/

There are no leading spaces in any part of the authentication (user name, password, host name).. I've tried connecting on four different PCs in my house using both my own ISP and my next door neighbors ISP. I even tried from my neighbor's PC.. The result is the same..

Finally I tried pinging the host name and am unable to ping the host name I am using to connect.. Siteground however maintains that the issue is local to my PC..

I could use some help here because I am stumped..

[lruskauff]

The last paragraph is what I was referencing.

[RodG]

When I try to connect to a remote MySQL database from my mySQL client software, I get “ERROR 1130: Host is not allowed to connect to this MySQL server”

This is good. It means that you have two way communication with the server. It's not network or firewall related.

The error I am getting appears to imply that something on Siteground's end needs to be modified

Correct. By default most SQL servers are set to deny remote access.

There are no leading spaces in any part of the authentication (user name, password, host name).. I've tried connecting on four different PCs in my house using both my own ISP and my next door neighbors ISP. I even tried from my neighbor's PC.. The result is the same..

Finally I tried pinging the host name and am unable to ping the host name I am using to connect.. Siteground however maintains that the issue is local to my PC..

I could use some help here because I am stumped..

Ping is not a very good diagnostics tool (by default). Telnet port 3306 would be a better tool to use, but even this will only provide what we already know from the error message - Specifically, it isn't a network/firewall issue (else you'd not get a response from the server at all).

The error message is also hinting at what is wrong - The *host* doing the connecting isn't allowed to access the server.
This needs to be resolved before even thinking about possible username/password issues. They will create a different error message.

SO.... you need to log into the cPanel, find the tab for 'Remote SQL access', select the database, and enter *your* hostname or IP address in the host/ip allowed field. This can be tricky of you don't have a static IP address, in which case feel free to use the '*' wildcard (to allow any host from anywhere). This will remove one layer of security, but a valid username/password is still needed before access to your database is possible.

Cheers
RodG

[DivaVocals]

Ping is not a very good diagnostics tool (by default). Telnet port 3306 would be a better tool to use, but even this will only provide what we already know from the error message - Specifically, it isn't a network/firewall issue (else you'd not get a response from the server at all).

Siteground suggested telnet, but I cannot execute telenet from my windows machine.. Hence the reason I tried pinging the host..

SO.... you need to log into the cPanel, find the tab for 'Remote SQL access', select the database, and enter *your* hostname or IP address in the host/ip allowed field. This can be tricky of you don't have a static IP address, in which case feel free to use the '*' wildcard (to allow any host from anywhere). This will remove one layer of security, but a valid username/password is still needed before access to your database is possible.

Hey Rod thanks for weighing in.. I didn't explicitly state it, but I did this before even attempting to try and access the DB using SQLYog..

[DivaVocals]

okay figured out why telnet didn't work.. (had to enable it..) Here's the result (host IP address has been obscured)

GHost 'xxx.xxx.xx.xxx' is not allowed to connect to this MySQL server

Connection to host lost.

C:\>

[DivaVocals]

The last paragraph is what I was referencing.

??????????????????????????????????????????/

[DivaVocals]

Latest from Siteground:

The IP address XXX.XXX.XX.XXX is the MySQL server IP address. You need to connect to it from your local IP address XX.XXX.XX.XX which is already added to the Remote MySQL Access list.

With that, they closed the ticket..

I still cannot access.. Help...

[DrByte]

Sounds like SiteGround (or at least the 1st-level tech who responded) isn't interested in fixing their server-side problem that "suddenly popped up" after working fine previously. I suspect some automated software upgrade broke things and the support staff don't even know that it happened let alone have any idea how to fix it.

Latest from Siteground:

The IP address XXX.XXX.XX.XXX is the MySQL server IP address. You need to connect to it from your local IP address XX.XXX.XX.XX which is already added to the Remote MySQL Access list.

With that, they closed the ticket..

Whoever sent you that message looked directly at the fact that the IP address is already added and thus you should be able to connect, but completely ignored that you said it's still not letting you. Wrong support tech ... need someone who knows more (or cares more).

I'd suggest re-opening the ticket and asking a 3rd-level support tech to respond ... or their boss.


In the meantime, direct remote access on port 3306 might not be an option for that server, at least until they get enough complaints to actually truly investigate rather than give you canned responses.
So, does SQLyog still have a "tunnel" connection option where you put a .php script on the server and connect to that over https instead of directly to port 3306?

As long as they don't see that .php script as malicious (some hosts auto-quarantine files they "think" might be risky even though they're harmless).

[lruskauff]

??????????????????????????????????????????/

Sorry, I had originally quoted some help from Siteground and didn't realize that when I added the one line, it deleted the rest. Basically it said what Ron had said, if your customer has a GoGeek site (what ever they call that level, Geek something), to go to CPANEL and set.....which you already did.

AS for Siteground support, I had been with them until quite recently. The best way to get help is to keep bugging them. Every time they close a ticket reopen it and throw another question at them, even if you just reword the last. This time you can quote Dr.Byte. Eventually they pass the question up the ladder and you get someone who knows what to do.

[lruskauff]

??????????????????????????????????????????/

Here is the original page from siteground.

If you have problems accessing your database at your web hosting account remotely please make sure that:

You are using the correct MySQL hostname – it should be yourdomain.com or your server's name;
You are using the correct MySQL database / username / password. You can check this tutorial for more information on how to create them;
Don't forget to specify your MySQL username and database with the prefix yourusername_ in front of its given name. For example, your cPanel username is user and you have named your database joomla. In this case you have to refer to your database as user_joomla;
You have allowed the remote host to access your database. This can be done from your cPanel > Remote MySQL.
You are connecting to the TCP port 3306.

A common mistake is to try accessing your databases using the main cPanel login. This will not work and you have to use the MySQL user instead.

Important (only for accounts hosted on GoGeek servers): In order to complete the PCI compliance requirements the remote MySQL connection to the GoGeek servers' primary IP is blocked. Still, to establish a remote MySQL connection to a database hosted on a GoGeek server use the server's secondary IP (ns2.servername.biz). It will be listed in the corresponding Remote MySQL page. Alternatively, it can be found in the Customer Area -> My Account section -> Manage.

It was "GoGeek" that I was refering to. I don't know if you tried to use the secondary IP?

Hope it helps.
lruskauff