Need help?

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

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

Cloud SQL Proxy error – An attempt was made to access a socket

by | Apr 14, 2021

Wondering how to fix Cloud SQL Proxy error – An attempt was made to access a socket? We can help you.

Recently, one of our customers came across this error while trying to use Cloud SQL Proxy to configure access to Google Cloud SQL in Windows using the command:

cloud_sql_proxy.exe -dir=/cloudsql -instances=my-project:us-central1:sql-instance=tcp:3306 mysql -u –host

At Bobcares, we frequently receive such requests as part of our Google Cloud Platform Support services.

Today, let us see how to fix this error.


Cloud SQL Proxy error – An attempt was made to access a socket

Accessing your Cloud SQL instance using the Cloud SQL proxy offers the following advantages:

  • Secure connections: The Cloud SQL proxy automatically encrypts traffic to and from the database using TLS 1.2 with a 128-bit AES cipher; SSL certificates are used to verify client and server identities.
  • Easier connection management: The Cloud SQL proxy handles authentication with Cloud SQL, removing the need to provide static IP addresses.

The error message is as follows:

listen tcp bind: An attempt was made to access a socket in a way forbidden by its access permissions.

The major causes of this error are:

  1. The SQL Server engages the 3306 port locally. Therefore, we cannot bind to it while it is running.
  2. Another process might use Port 3306.


How to solve the error?

Moving ahead, let us see an effective way our Support Techs employ in order to solve this error.

  • Initially, we stop the SQL Server to bind the CloudSQL Proxy to it.

In case we have Windows 10, we go to Task Manager -> Services -> MySQL57. We have to right-click and stop the task.

Once done, we try and run the same command again. Successful output will be as follows:

Listening on for <instance-name>

The same procedure is applicable to the postgresql process also.

  • Specify a different port, in case another process uses 3306.

For instance,

  • On Windows cmd or Google SDK shell, we use the below command:
cloud_sql_proxy.cmd -instances=<INSTANCE_CONNECTION_NAME>=tcp:3306 -credential_file=<PATH_TO_KEY_FILE>

Make sure to declare cloud_sql_proxy.cmd as environment variable, where:

  1. INSTANCE_CONNECTION_NAME = my-project:us-central1:sql-instance
  2. PATH_TO_KEY_FILE = create a service account in IAM panel and save the json file copy its path and paste it here.

If this does not work, we try connecting to TCP 3307.

[Failed with the resolution? We’d be happy to further assist you]



In short, we saw how our Support Techs resolve the Cloud SQL Proxy error in an effective way.


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.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

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


Privacy Preference Center


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]


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


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


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.