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

Test Connection: Socket timeout when connecting to remote PostgreSQL database hosted on AWS #89

Closed
Nezteb opened this issue Apr 28, 2022 · 3 comments

Comments

@Nezteb
Copy link

Nezteb commented Apr 28, 2022

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).

Screen Shot 2022-04-28 at 2 02 18 PM

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

@Wisser
Copy link
Owner

Wisser commented Apr 28, 2022

Maybe the driver is not compatible with the DBMS? Do you also use postgresql-42.2.16.jar for TablePlus and DBeaver?

@Wisser
Copy link
Owner

Wisser commented Apr 28, 2022

It could also be that you can only access the VPN via the system proxy. To use this, modify the file "jailerGUI.sh", line 34 to:

java -Xmx1200M -Djava.net.useSystemProxies=true -Djava.util.Arrays.useLegacyMergeSort=true -cp $CP net.sf.jailer.ui.ExtractionModelFrame "$@"

@Nezteb
Copy link
Author

Nezteb commented Apr 28, 2022

I'm an idiot and had a tiny typo (a lowercase "L" instead of an uppercase "i"), so disregard this entire issue. 🤦‍♂️

@Nezteb Nezteb closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants