Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

AWS MySQL error 10060 – Can’t connect to MySQL server

by | Jun 2, 2021

Stuck with AWS MySQL error 10060? We can help you.

It is possible for a MySQL client to come across this error while trying to MySQL server over AWS cloud.

As part of our AWS Support Services, we assist our customers with several AWS queries.

Today, let us see how to fix the error “RDS: ERROR 2003 (HY000): Can’t connect to MySQL server (10060)”.

 

AWS MySQL error 10060

The error message MySQL server sends back is:

RDS: ERROR 2003 (HY000): Can’t connect to MySQL server (10060)”.

It states that the inbound/outbound traffic from the AWS instance is not reachable to the current host where we run the MySQL client.

So we need to register the public IP address in the RDS security groups to get access over the RDS MySQL instance.

 

Configure public IP address in security groups

Moving ahead let us see a few steps and screenshots to fix the error.

  1. First and foremost we need to find the public IP address for the host machine where we run mysql-client. If we use the Amazon EC2 instance we can find the public IP here:AWS MySQL error 10060
  2. Here, we go to the security groups and add the public IP address for inbound traffic:MySQL error 10060
  3. Then we add the same entry for outbound traffic by AWS services:outbond-traffic-RDS : ERROR 2003 (HY000): Can't connect to MySQL server (10060)
  4. Once done, we refresh the security groups and test the connection from any mysql-client.

For example, to test the connection we run the below command from any terminal where MySQL is configured:

mysql -h host-public-ip/DNS -P 3306 -u username -p password

Network ACLs

Network ACLs act as a firewall for resources in a specific subnet in a VPC. If we have ACLs, we ensure they have rules that allow all traffic to and from the DB instance.

 

Create a network ACL

We can create a custom network ACL. By default, a network ACL that we create blocks all traffic until we add rules.

  1. Initially, we open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
  2. In the navigation pane, we choose Network ACLs.
  3. Then we choose Create Network ACL.
  4. In the Create Network ACL dialog box, optionally name the network ACL, and select the ID of the VPC from the VPC list.
  5. Then we choose Yes > Create.

 

Add and delete rules from a network ACL

If we add or delete a rule from an ACL, any subnets that associate with it are subject to change. We don’t have to terminate and relaunch the instances in the subnet. The changes take effect after a short period.

On the other hand, if we use the Amazon EC2 API or a command-line tool, we can’t modify rules. Here, we can only add and delete rules.

With the Amazon VPC console, we can modify the entries for existing rules. On our behalf, the console removes the existing rule and adds a new rule.

In order to change a rule in the ACL, we must add a new rule with the new rule number, and then delete the original rule.

  • Add rules:
  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
  2. In the navigation pane, we choose Network ACLs.
  3. Then in the details pane, we choose either the Inbound Rules or Outbound Rules, then choose Edit.
  4. In Rule #, we enter a rule number (for example, 100). The rule number must not already be in use in the network ACL.
    Our Support Techs recommend leaving gaps between the rule numbers because it makes it easier to add a new rule without having to renumber the existing rules.
  5. We select a rule from the Type list. For example, to add a rule for HTTP, choose HTTP. To use a protocol, not on the list, we choose Custom Protocol Rule.
  6. In case of a custom protocol rule, select the protocol’s number and name from the Protocol list.
  7. Then in the Source or Destination field, we enter the CIDR range that the rule applies to.
  8. From the Allow/Deny list, we select ALLOW to allow traffic or DENY to deny traffic.
  9. In case we want to add another rule, we select Add another rule and repeat steps 4 to 9 as required.
  10. Once done, choose Save.
  • Delete a rule:
  1. We open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
  2. In the navigation pane, we choose Network ACLs and select the network ACL.
  3. In the details pane, select either the Inbound Rules or Outbound Rules tab, and then choose Edit.
  4. We can select Remove for the rule we want to delete, and then Save.

[Need help with any of the above? Feel free to contact us]

 

Conclusion

In short, we saw how our Support Techs go about AWS MySQL error 10060.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF