• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Cannot connect to DB Remotely

melifetaji

New Pleskian
Server operating system version
debian-11-bullseye-v20231212
Plesk version and microupdate number
Free Trial (probably Latest)
Basically cannot connect to my db from my local computer.

The database is on localhost:3306 on the server, remote connections are allowed.

What I've done:
1. Turned off the Firewall completely (didn't work)
2. Restarted MySQL and MariaDB services
3. Adjusted the config file to bind 0.0.0.0
4. I have a user with FULL ACCESS
 
How can I manually add a firewall port rule from Plesk Dashboard?

I did this from terminal but it didnt help:
  1. sudo iptables -A INPUT -p tcp --dport 3306 -i your_interface -j ACCEPT
 
- Which database server and which version are you using? E.g. for MariaDB 10.6 and newer you'd omit the bind-address line altogether while for previous versions it should be "bind-address = ::".
- Does your datacenter have a firewall in front of your server that you can configure in your data center's control panel?
 
Thank you Peter, you are a hero :)

The problem was Google Cloud Firewall, totally forgot to configure firewall there.
 
Back
Top