Bobcares

Plesk Allow Remote MySQL Connection | A Simple Guide

by | Oct 11, 2022

In this article, we will provide the instructions to allow remote MySQL connection in Plesk (for Windows and Linux). At Bobcares, with our Plesk Hosting Support Services, we can handle your Plesk issues.

How to allow remote MySQL connection in Plesk?

In Plesk, we need to establish a new user just for the remote MySQL connection. Since the admin will not have remote access by default. Let’s go through the steps:

  1. Firstly, use SSH or RDP to connect to the server.
  2. Then navigate to Plesk >> Subscriptions >> example.com >> Databases >> User Management >> example_db_user;
  3. Also, confirm Access control option is set to “Allow remote connections from any host” or to “Allow remote connections from.”
  4. SSH/RDP into a Plesk server. Start any text editor to access the MySQL configuration file. The following address is where we can find this file.

    For Linux: /etc/my.cnf(CentOS/RHEL), /etc/mysql/my.cnf(Debian/Ubuntu).

    For Windows: %plesk_dir%Databases\MySQL\my.ini.

  5. Now modify the bind-address parameter.
    bind-address = 0.0.0.0
  6. Ensure the MySQL configuration file does not define the skip-networking parameter.
  7. Verify that the bind-address directive is present in the /etc/mysql/mariadb.conf.d/50-server.cnf. Make sure it is pointing to 0.0.0.0. And not the loop-back address if it is specified.
  8. Now restart the MySQL server.

    For Linux: # service mariadb restart(CentOS/RHEL), # service mysql restart(Debian/Ubuntu).

    For Windows: Start Plesk Services Monitor >> select MySQLX or MariaDBX (where X is a version) >> click Restart.

  9. Finally, log in from the remote server to confirm connectivity. Use MySQL Workbench or the CLI to run the following command:
     # mysql -u"example_db_user" -p"password" -h"example.com"
    
    
    
    plesk allow remote mysql connection
    
    
    

Check the firewall settings if you are unable to connect to a remote MySQL server in Plesk. Check to see if a firewall is blocking access to the MySQL port:

  1. Firstly, log in to Plesk.
  2. Then install the Plesk Firewall extension.
  3. Activate Firewall Rules Management. Go to Tools and Settings >> Firewall >> Enable Firewall Rules Management.
  4. On the new window, click Enable button.

[Need further assistance with the issue? Get in touch with us.]

Conclusion

The article provides a brief guide from our Support team on how to allow remote MySQL connection in Plesk. It includes steps for both Windows and Linux platforms.

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

0 Comments

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