Quote Originally Posted by DrByte View Post
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..

Quote Originally Posted by DrByte View Post
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..

Quote Originally Posted by DrByte View Post
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..

Quote Originally Posted by lruskauff View Post
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..