Bobcares

MySQL Workbench error 61 – Solve it now

by | Feb 3, 2020

Trying to find a solution for ‘MySQL Workbench error 61’? Here’s how we fix it. 

MySQL Workbench is the best option to use when it comes to graphical management in MySQL.

At Bobcares, we often receive requests to fix MySQL errors as a part of our Server Management Services.

Today, let’s explore more on this error and see how our Support Engineers fix it.

 

What causes MySQL Workbench error 61 to show up?

This error normally pops up when trying to use MySQL Workbench and connect through an SSH tunnel. And the error shows up when the SSH connection doesn’t complete successfully.

This error can occur due to different reasons. This includes entering an improper hostname, entering an incorrect password while connecting to the database, default MySQL port is occupied by some other process in the server.

For instance, the error appears as below,

MySQL workbench error 61

 

How we fix this MySQL Workbench error 61?

We have now discussed the cause of this error. Let’s now see how efficiently our Support Engineers fix this error.

 

1. Host error

Recently, one of our customers experienced some trouble in connecting to MySQL Workbench.

He received the below error message,

Can't connect to MySQL server on '127.0.0.1' (61)

Our Support Engineers started to troubleshoot this error by checking the configuration file my.cnf.

We opened the /etc/mysql/my.cnf in a text editor and commented the bind-address parameter line. We updated the below code

bind-address = 127.0.0.1

to

#bind-address = 127.0.0.1

After this, the connection was successful.

 

2. Port conflict

In another case, one of our customers got the same error but the fix was a different one. Here, we checked that the bind-address was already commented and it was not a problem with the host.

So, we investigated further by checking the port of MySQL. We checked it by using the below command:

netstat -plunt | grep 3306

Here, the result was not with MySQL. The server had MySQL running on a different port. So, we simply changed the port of MySQL from 3306 to 3307 by adding the below line in my.cnf file

port = 3307

And then restarted the MySQL service using the command:

service mysql restart

Finally, this fixed the error.

 

3. Firewall restrictions

Likewise, firewall restrictions on MYSQL port can also be a reason for the MySQL Workbench error 61.

The connection will work only when MySQL is running and allow connections from remote IP addresses.  Thus, we always check local and external firewalls to make sure they’re allowing inbound connection at port 3306.

 

[Need any assistance with MySQL errors? – We’ll help you]

 

Conclusion

In short, the MySQL Workbench error 61 occurs when there are problems in completing the connection successfully. Today, we saw the causes like incorrect host settings, port conflicts, bad firewall, etc. and how our Support Engineers fix it.

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";

1 Comment

  1. Robert Fry

    Hey, thanks for the quick fix. I did notice a difference on the file and the path on Ubuntu 18.04 server. The path is /etc/mysql/mysql.conf.d/mysqld.cnf. The file is mysqld.cnf. All in all everything works great now. Thanks again.

    Reply

Submit a Comment

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

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

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
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

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

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

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