Leaving trusted sources empty lets me connect to my db via the connection string with Standartd (TCP/IP). Trying to do so with Standard TCP/IP over ssh will cause everything to stop responding for a moment before returning to normal but test connection shows no pass or fail. When I add trusted sources (including the IP of my computer) I’m no longer able to connect to the db in any way through workbench. I’m not sure if there is something I’m missing (an IP that workbench would use that isn’t my computers or something). Just curious if anyone would have any insights, I’d prefer to use trusted sources but I also would love to use the workbench to query my tables
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.
Hey there 👋
Can you confirm if this is regarding the DigitalOcean managed MySQL database clusters? If so, then keep in mind that managed MySQL clusters do not come with SSH access.
When using trusted sources, it’s super important to make sure you’ve added the correct public IP address of your local machine. Can you make sure to double-check that it’s not changing if you’re on a dynamic IP (like most home networks)?
You can quickly verify this by running the following on your local machine:
Make sure that the IP address that you get is the one that you’ve added in the trusted sources list.
Let me know how it goes.
- Bobby