Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
This comment has been deleted
So after ages of trying, I decided to go back to a Serverpilot set up. Destroyed my droplet, recreated a basic Ubuntu one, then used Serverpilot to create the app and database. Same issue again, unable to access the database from Sequel Pro.
I cannot work out what is going wrong? In each case Ive attempted the commenting out the bind address, but again, nothing works.
When using ServerPilot, to access the database remotely through Sequel Pro you should use the Sequel Pro option to tunnel through SSH. If you need to instead open up MySQL publicly rather than using an SSH tunnel, you’ll need to both reconfigure the MySQL bind address and open up the firewall to expose MySQL. There’s a bit more info here:
https://serverpilot.io/community/articles/connect-to-mysql-remotely.html
anyone who uses serverpilot, please join to the unofficial slack discussion community hub, for sharing experiences about doing missing (premium) features in free plan 😉