2 years ago
Our services currently using internal URLs to access to databases services. However, when we attempt to connect to these services using tools like Mongo Compass or Redis Insight, we're encountering difficulties. This issue seems to be specific to our development environment, as connections are successful in our production environment.
8 Replies
2 years ago
UPDATE: Our production environment starts with the same problem
2 years ago
Hey thanks for the new thread and details @nathanmejia. To be clear, are you trying to connect your DBs to Compass/Insight using the internal address or the public one?
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
We are using the public one
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
What error do you see when trying to connect? I have used Compass with no problem in the past, but haven't heard of Insight.
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Both database exposes a Timeout error using the public url
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
I just tested both Compass and Insight and both worked without issue for me.
Are you able to connect to either of them via a shell in your terminal? I don't think this has anything to do with Compass or Insight, and maybe there is some issue for you connecting to the TCP Proxy addresses.
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Thanks for you responses, it was an issue in our side, we solved, thanks
Status changed to Awaiting Railway Response Railway • over 1 year ago
Status changed to Awaiting User Response Railway • over 1 year ago
10 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 months ago