Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !
WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure. Join the pilot program today!
Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
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.
I think you also need to grant access to a user in the right way. By default a database user created through Plesk is user@localhost and trying to login from a remote location would be rejected because they are not connecting from localhost.
So I think you need to GRANT xxx TO 'user'@'ipaddress' identified by 'password' for the database in question (or something like that --- I don't remember the syntax exactly).
xxx could be ALL but that's a security risk. You should limit it to what's needed rather than ALL. Using @'ipaddress' limits the connection to the static IP where the remote connection is coming from. I think you can also use a domain instead of an IP, and therefore control the IP via a DNS entry. You may also be able to grant to user rather than user@ but it would be more sensible to limit it to an IP if possible, even if your fireall only allows access to port 3306 from their static IP. Every extra level of security you add helps!
Have a look at the GRANT syntax to see what you can do. Like I say I can't remember the exact options off-hand.
In addition to what has already been said, check your /etc/my.cnf file and make sure that skip-networking isn't in there. If it is, comment it out (#) and restart MySQL.