I have an RDS instance that I was able to connect to remotely fine for months now. However, tonight I downsized the DB because we we're paying for a lot of unused CPU. After the change from m3.medium to the t2.small I can't connect to it anymore. I have terminal shortcuts setup so I can't be typoing it. I double checked the security groups and thats still applied and the host is the same and everything. I'm not sure what else to try. I just get:
ERROR 2003 (HY000): Can't connect to MySQL server on '<my-host>.us-east-1.rds.amazonaws.com' (60)
I encountered the same problem today. After upsizing the RDS instance, I am unable to connect to it using SSMS which I was able to do just a few hours earlier. It has suddenly stopped working on two PCs so I could not have accidentally changed some parameters. However the web server accessing the RDS within the VPC works fine
sorry for silly question: are you sure my-host didn't change after resizing? Given the error message, it's not credentials. So, it is either address, or security groups, or VPC-based networking.
Related
I am receiving a lot of error reports from my Django server throwing:
(2005, "Unknown MySQL server host 'my-address.us-east-1.rds.amazonaws.com' (0)").
The server has been connecting to this database for more than a year without any issue. But this morning I suddenly started to receive this error, even though I didn't do any changes to the code.
Furthermore, when I connect to my website, it actually loads data from the database fine.
Apparently there is a random chance that it won't manage to connect?
Any idea what can cause that and how to fix it?
I am on Amazon lightsail.
There is an active AWS DNS resolving incident in us-east-1 region. Seems like it will be mitigated soon.
https://status.aws.amazon.com/
UPDATE: The issue is now resolved as updated by AWS.
First thing first, I have checked almost all the answers related to this but couldn't find the cure to the problem.
To connect to RDS, I know that we need to set the inbound rules in the security group associated with the RDS instance to my machine's IP, which is already set.
Am just using a mysql client like sequel pro, specify the RDS endpoint, mention the username and pwd but everytime the connection could not be established.
There is no firewall as I am using my mobile internet by connecting my machine through hotspot.
One important thing that might be causing the issue could be the subnets that are associated with the default VPC on my RDS. I have 2 public subnets and 2 private subnets associated.
Also ran the command nc rds-host port, even that also timed-out.
Tried all troubleshooting steps but still not able to connect. Could somebody throw some light here. Stuck for a very long time.
This is the error:
Be sure that the address is correct and that you have the necessary privileges, or try increasing the connection timeout (currently 10 seconds).
MySQL said: Can't connect to MySQL server on 'abcdef.rds.amazonaws.com' (4)
I am running a db.t2.micro instance on AWS RDS. I used to be able to connect to it via MySQL workbench, but now I can't anymore. Nothing has changed though.
I even re-entered the end point, admin name and password, even though they we're the same still, but still cannot connect.
My elastic beanstalk application that relies on the DB however can still access it. So I suspected the public access had been changed, but that's still enabled too.
Any ideas how to fix this?
Here is the error I am getting:
http://pgrbristol.org.uk/rant/DBError.PNG
I have checked all the points.
Thanks for any help!
I have a Google Cloud SQL Instance that I have been using for some time now and connecting successfully from MySQL Workbench. However as of yesterday I can't connect using MySQL Workbench (or the command line on my laptop) and get the error:
ERROR 2003 (HY000): Can't connect to MySQL server on '207.xxx.xxx.xx' (10060)
I have done the following already:
Authorised my laptop's IP address (found using whatismyip.com) in the Google Console.
Assigned an IPv4 address to the database in the Google Console.
Created new users and passwords to see if it was a user issue. But that didn't help.
Restarted the instance, restarted my home network/laptop and got new IP addresses (and updated the authorised IP address accordingly).
Upgraded to the latest MySQL workbench 6.3 CE but still have the issue.
The database works as my app can connect to it and accesses the data, I just can't get a remote connection from my laptop.
I am new to this and am out of ideas on how to fix it. Any help would be greatly appreciated.
Thanks everyone for your help. After trying all of your suggestions I found a Google group and logged the issue. Google have responded to it as follows:
David Newgas: For now try connecting from a GCE instance (including cloud shell) or using a GCE instance to proxy connections from your laptop.
I have updated the dashboard with some more information (although it may take a while for you to see it due to caching)
To be clear, this issue will only be affecting first generation instances.
I did not have enough 'points' to comment, so I'll have my say here.
I am having about exactly the same issue. About 10 days ago I connected fine to the Cloud SQL instance, and synced my db up. Yesterday I was going to push some updates etc. But I could not connect, even though I have changed nothing in respect to the database connection, except for the given IPv4.
I figured the issue was with my Django project, based on the App Engine Skeleton, so I created an issue on that project.
https://github.com/GoogleCloudPlatform/appengine-django-skeleton/issues/16
Maybe/Hopefully some we get some information from there.
I had the same problem.
By pure luck I said "Let's try to connect with my local MySQL client while the gcloud command was saying
"Whitelisting your IP for incoming connection for 5 minutes..."
and (mysql local client) worked.
I have multiple hosts that connect with a database on an Amazon RDS server. The normal webservers have no trouble connecting with the database, but today I discovered that my development server couldn't connect.
The error I get is
'ERROR 2003 (HY000): Can't connect to MySQL server on
'endpoint.blabla.rds.amazonaws.com' (113)'
Trying to connect via my home laptop gives no problems. It's only the devserver.
When I initiate a connection from the devserver via nc, it gives 'No route to host'. As far as I know, I didn't change anything on the devserver. The databaseserver however has been resized last Thursday, but I'm not sure when the problems have started. I know that it still worked two weeks ago, that's all.
Anyone any experienced this before with Amazon RDS? I really don't know where to look at the moment. The VPC security groups haven't changed, and other servers with the same security groups on the same VPC have no trouble connecting to the database.
Ok it is solved after a couple of hours searching. There was a route in my route table that caused the trouble. I have no idea how it got there, but it is solved now, I can reach the server again. :)