• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue How to whitelist IP address in New plesk 18.0.6

exploremalaysia

New Pleskian
Hello, I want to know how can we whitelist an IP address in the new plesk, as i couldn't see the option called IP address banning in the new Plesk, Since i want to connect my website database to remote. It's not connecting it
 
Hi,

Please share a screenshot of the entire Plesk interface when visiting Tools & Settings.
 
First off, you've exposed your DB details in the code screenshot. Please make sure you change the password for the explore database username.

You don't have Fail2Ban installed. The whitelisting in Fail2Ban is only to prevent blocking of the IP address in any of the configured jails. However, there isn't a jail for database connections.

In your case, your database port 3306 is most likely blocked or the database service is not listening on all interfaces.

In the firewall configuration, what do you have at MySQL server:
1736412193729.png

As for the listening part, I have this output, meaning it's listening on all interfaces:
Bash:
# ss -natpl | grep 3306
LISTEN 0      90                0.0.0.0:3306       0.0.0.0:*    users:(("mariadbd",pid=1202232,fd=67))                                                                                                                                   
LISTEN 0      90                   [::]:3306          [::]:*    users:(("mariadbd",pid=1202232,fd=68))
 
First off, you've exposed your DB details in the code screenshot. Please make sure you change the password for the explore database username.

You don't have Fail2Ban installed. The whitelisting in Fail2Ban is only to prevent blocking of the IP address in any of the configured jails. However, there isn't a jail for database connections.

In your case, your database port 3306 is most likely blocked or the database service is not listening on all interfaces.

In the firewall configuration, what do you have at MySQL server:
View attachment 27709

As for the listening part, I have this output, meaning it's listening on all interfaces:
Bash:
# ss -natpl | grep 3306
LISTEN 0      90                0.0.0.0:3306       0.0.0.0:*    users:(("mariadbd",pid=1202232,fd=67))                                                                                                                                  
LISTEN 0      90                   [::]:3306          [::]:*    users:(("mariadbd",pid=1202232,fd=68))
Hello,

please check the screenshot of the firewall ,
 
It's not blocked in the firewall. Is the MySQL service listening on all interfaces?
 
Back
Top