Report this

What is the reason for this report?

Private connection to Managed DB not working from within same region droplet.

Posted on October 14, 2019

I have a droplet in the same region as my managed DB, like DO suggested. I have added my IP and droplet to the Restricted Access section of the managed database. I can connect via public connection from my computer. If I try connecting from within the droplet using private credentials, no error message, just timeout. Is there a step I’m missing? I even disabled the droplet’s firewall thinking the port was being blocked.



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.

Hello,

Can you double check that your droplet is added/allowed in the Trusted source under the Trusted sources of manage database?

Let me know how it goes.

Hello @alexdo , yes I have double checked. I have even deleted the managed db and recreated it. I have also spun up a new droplet temporarily in the same region with just mysql/mariadb on it, and still cannot connect via private credentials, but public works.

@daveprezzo @alexdo I have the same problem with MySQL Managed DB Cluster With public connection everything works great, but when im trying switch into private connection have a timeout error:

PDOException: SQLSTATE[HY000] [2002] Connection timed out

The developer cloud

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

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.