Solved Redash connect to an external DB - Do I need to open ports?
-
Hi,
I'm currently trying to connect to a remote Sql Server DB on port 1433 (the default). I've had this port opened for my cloudron servers IP, but I still can't connect successfully.Do I need to add port 1433 in some configuration somewhere to open this port for redash/sql server?
Thanks
Mark -
Since that is an outgoing connection, you should not need to adjust the firewall or such on your Cloudron. Do you have any logs on the Sql Server side to see if your redash instance attempts to login or gets blocked or so?
-
While the initial request will be outgoing, the db will respond on port 1433 as well won't it?
I can probably get help to get the logs, but it's a third party who manages the db so I'd prefer to rule out the obvious before I go down that path.
So is there something I need to configure to open up 1433 for redash?
-
Generally being able to expose new ports and forward those to the app's docker container needs a package update. But I would be surprised if that external database would indeed connect on its own to the app.
Since you mention the initial connection from the app to the db, does this work as expected?
-
Thanks Nebulon. I'll follow up with the team administering the db tomorrow. Using the nc command directly from the server running cloudron, I'm not getting an acknowledgement. So i'm hoping it's an issue at their end.
-
@markjames said in Redash connect to an external DB - Do I need to open ports?:
While the initial request will be outgoing, the db will respond on port 1433 as well won't it?
This is a bit technical but the DB will respond to the port from which the request was made. This is usually a dynamic TCP port that the Cloudron app opened. The firewall has special rule to allow all incoming packets if it's an "established" connection. This is the reason why an outsider can connect to a port as long as it was cloudron that initiated the conversation first.
