PDA

View Full Version : remote mysql quit working



goochs
02-24-2009, 05:35 AM
First let me say that my renote access has been working like clockwork. Recently bluehost changed my box and f course I couldn't access the db anymore. After finally seeing the change I went to the server with the database and added the new box number as box524.bluehost.com
This didn't solve the problem I still get a 1045 error when trying to connect.
I can access this db from 2 other servers, one on bluehost and one on hostmonster with no problem at all. I haven't been able to get the help from bluehost but I robably haven't explaied it well or I keep hitting the wrong tech. They should I should add the ip address to the whitelist but don't have access to that via the configuration area plus I didn't do that wth the other servers.
Is the IP the shared one that is listed in cpanel?
Has anyone else had this problem?
Is it possible that bluehost needs to change something in the configuration to make it work remotely?

One other thing I noticed was event though they changed my box the last digits of he shared IP didn't change. I did notice that on te other sites that access the DB the last figits of the IP follow the box number??

This shut me down for a da for I had to duplicate dbs to the main site that quite working so they were local but this will create a bigger headache later.

cade
02-24-2009, 05:48 AM
Which database host are you connecting to? MySQL should be listening on the new box's main IP, but it won't listen on the IP from the old server that you were on (even though it exists on the server). You should be connecting to box524.bluehost.com (74.220.219.124), is that what you are doing?

goochs
02-24-2009, 06:36 AM
the box I want to connect to is box204.bluehost.com
that's where the db is located. On that server I opened remote msql and added box524.bluehost.com (server I want to connect from)
In dreamweaver on the site that is box524 I create a connection using

server: the domain of the db location
user: goochs_username
pass: password
db: goochs_somedb

That's when I get the error.

If I do the same from a different site on a differnet server with the sme login and its boxnumber added to the recieving site.. itflies right through.
I'm a little confused on the whitelist for I never had to add an IP address over the last 4 years up until this server change.

I just tried something else. I entered all wildcards ( meaning any server can connect ) and it connected with no problem.. Of course I deleted that so I am thinking it is an ip or resoving issue at bluehost??