You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am able to connect to this same database with both TablePlus and DBeaver, but not Jailer for some reason. I've triple verified the correct JDBC url format, host, username, and password.
This probably isn't specific to AWS; I'm guessing I'd have the same issue with any cloud provider. It's worth noting that I am on a company VPN in order to access the database, but again TablePlus and DBeaver handle that just fine (and I assume it's not an issue with Jailer and VPNs specifically).
Steps to Reproduce the Issue
Add a remote database connection pointing to an AWS-hosted Postgres instance and try to test the connection.
Expected Behavior
I'd expect Jailer to be able to connect to databases like TablePlus and DBeaver.
Actual Behavior
It doesn't seem to work no matter what I try; I always get the same socket timeout exception.
Description of the Issue
I am able to connect to this same database with both TablePlus and DBeaver, but not Jailer for some reason. I've triple verified the correct JDBC url format, host, username, and password.
This probably isn't specific to AWS; I'm guessing I'd have the same issue with any cloud provider. It's worth noting that I am on a company VPN in order to access the database, but again TablePlus and DBeaver handle that just fine (and I assume it's not an issue with Jailer and VPNs specifically).
Steps to Reproduce the Issue
Add a remote database connection pointing to an AWS-hosted Postgres instance and try to test the connection.
Expected Behavior
I'd expect Jailer to be able to connect to databases like TablePlus and DBeaver.
Actual Behavior
It doesn't seem to work no matter what I try; I always get the same socket timeout exception.
Debug Information
Jailer version: 12.3
Driver:
lib/postgresql-42.2.16.jar
The text was updated successfully, but these errors were encountered: