Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

postgres data source with 2 databases cannot connect to other databases "SSL connection has been closed unexpectedly" #6762

Open
chrisgeno opened this issue Feb 9, 2024 · 0 comments

Comments

@chrisgeno
Copy link

Redash: 10.1.0 (2589bef) upgrade from the AWS EC2 AMI that runs 8

We have a production Postgres-15 instance running on render. We have redash set up against the primary database for reporting that works just fine. We've added a second database on that same pg instance that we need to create a redash connection for but on trying to connect we immediately get "SSL connection has been closed unexpectedly." The connection string is literally the same except for the database identifier. I can recreate this connection issue in psql if I run an old version of the psql client, but when I upgrade the psql client to -15 everything works fine. This issue seems to stem from an old psql client, or underlying libpq or old version of postgres client in Redash. I'm not sure how to find the versions of what redash is using to connect to postgres, but this appears to be a known issue with some clients: https://community.render.com/t/multiple-databases-ssl-connection-has-been-closed-unexpectedly/4249,

Any ideas on a way I can figure out what is going on here and update the underlying connection driver to postgres for Redash?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant