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.
You can configure does in the GUI of the managed databases, before the DB was publicly available and you could configure to specify ip ranges or droplets/networks within DO, they launched a internal network only, not sure if they now have this as default. This configurations are available in the GUI of DO and you can look at what you have configured.
Hi there!
You should ensure that you add the DOKS cluster as a Trusted Source (In cloud: go to the cluster --> Settings --> Edit Trusted Sources)
After that you should be able to connect to your database.
Regards,
John Kwiatkoski Senior Developer Support Engineer
I seem to be having the same issue. I’m attempting to connect from my DOKS cluster to my DOPostgreSQL using the private network.
The error returned is the same as the original that was posted. The IP listed is the internal-ip for one of the nodes.
I can confirm that I have the cluster and the cluster added under Trusted sources.
Update: Not sure what the issue was but I created a new user view the DO GUI and logged in with that and it seems to be working now.