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

[DivaVocals]

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.

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.

Yeah.. I kinda figured that.. Thanks for confirming this.. I don't plan to let them off the hook..

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.

It's starting to look that way..

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).

Yes SQLyog does have this option.. I jut don't know how to use it..

Here is the original page from siteground.

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

Hope it helps.
lruskauff

Along with the repeated canned responses, Siteground keeps quoting this USELESS "help" page.. My issue isn't rooted in an incorrect setup on my end otherwise I would be getting a different message..

[DivaVocals]

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).

Gotta love Google.. Figured how to use the tunnel connection with SQLyog.. Connected and working..

Just for grins and giggles, before I tried the tunnel connection, since I am in Vegas, I tried whitelisting the hotel's wi-fi IP address (their ISP is not Time Warner or Cox) SAME F***ing result!!!!

Did I mention how much I DESPISE Siteground????


Anyway thanks to EVERYONE who chimed in..

[DrByte]

In the purest sense, connecting via https with the tunnel is more secure than doing it directly over unencrypted port 3306.
So, as long as the site you're connecting to has an SSL cert the tunnel is a smarter idea.

[DivaVocals]

In the purest sense, connecting via https with the tunnel is more secure than doing it directly over unencrypted port 3306.
So, as long as the site you're connecting to has an SSL cert the tunnel is a smarter idea.

Thanks DrByte for the input and advice..After nearly a week of bull$h!t, I can finally can move forward...

[DivaVocals]

Wanted to post a follow-up on this.. I went back to Siteground yesterday and nearly VERBATIM quoted DrByte's response along with repeating for the support team my settings and what I had done thus far to troubleshoot.. THAT finally got someone to kick things up to a supervisor. This is the response I got today:

I have contacted our system administrators who were able to resolve the case with the remote connection to the MySQL service. They have re-added the IP addresses in the allowed list and now the connection should be completed successfully.

Also we tested to add another IP and then removed it without any issues. Could you please check the results and let us know in case there are still issues.

And NOW the original issue is resolved (though I was able to move forward by connecting using HTTPS tunneling)

Thanks again to everyone who responded..