-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
SSH Tunneling doesn't work #51
Comments
interesting. Let me investigate. |
I just tried with a MariaDB server and happens the same. After switching between several databases, they tables did show up... Maybe a loading/latency issue? |
I can't even get tunneling to work at all? Just says it cant connect. Same config works flawless for SequelPro and SQLPro.. This is for MySQL connecting to Amazon RDS through a SSH tunnel. |
If I had to guess, I'd say a lot of these issues are stemming from things like not supporting jump hosts, which could be resolved by taking the users ssh config file into consideration? |
Same issue here, trying to connect to MySQL. It connects (always on SECOND try btw, not first) and then shows no tables or dbs |
Yeah the tunneling code is a little flaky right now. Running queries through the tunnel isn't great. I haven't spent much time on that code, but I'm prioritizing the connection bugs. |
me too. @ssuess |
For me, the error is |
My next milestone is to revamp the SSH and SSL libraries. Sorry this isn't working right :-( |
Can you all test this build? https://github.com/beekeeper-studio/beekeeper-studio/actions/runs/106301681 You should be able to download the assets for your OS and install as usual |
This build seems to fix my connection and db listing problems. Thanks! |
Using MySQL getting;
Works flawlessly without SSH tunnel. Also I can SSH fine outside beekeeper (including mysql-workbench) |
What platform, key type are you using? Eg windows, pem |
considering pem (a public key format) is never going to work... I am using a private key generated via defaults of Ubuntu 20.04
Installed clean from instructions after the issue #40 I raised with snap and you closed as being due to a snap restriction and i solved it by not using snap, so not really resolving the issue but closed anyway.. My conclusion is Beekeeper for Linux is a toy/alpha tool used for localhost and not ready for enterprise/production use - maybe other platforms, perhaps more familiar to the devs, work in real world scenarios. |
Hey @chrisdlangton, So sorry you're frustrated with the app :-(. Beekeeper Studio is definitely early -- we only announce it on April 20th. SSH tunneling is something we adapted from an earlier library, and yes it is the most broken part of the product right now. I have some servers that I use for testing SSH, but not all combos of dbs and configs are covered. It's a bit of a cat and mouse game. I'm trying to determine what folks are trying to use for their SSH connection configs. For example - private keys generated from putty have been causing issues, and because I don't have docs for SSH tunnels yet I've had to field several informal questions about private/public keys, hence me dropping PEM as a suggestion :-). Follow up Questions
Thanks for your help |
@rathboma To give the project benefit of doubt the key pair was generated fresh, and the public key was added to authorized_keys of a digital ocean docker droplet. My production use case is EC2 Amazon Linux 2 (centos) as a temporary/breakglass bastion to access RDS/Aurora. I tried various databases so versions, but the isolated test on the droplet was a container image version: '3.6'
x-defaults: &defaults
restart: unless-stopped
logging:
options:
max-size: "10m"
max-file: "3"
mysql:
<<: *defaults
image: mysql:5.7@sha256:ba2eda1bf1249bd7e7160fa6c446d03b3261f75d3de91bc2125967d39db1525c
container_name: mysql
volumes:
- /mnt/volume_sgp1_02/mysql_data:/var/lib/mysql
command: '--max_allowed_packet=65011712 --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci --max-connections=1024 --skip-show-database --skip-grant-tables'
expose:
- 3306
environment:
- MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
- MYSQL_DATABASE=${MYSQL_DATABASE}
- MYSQL_USER=${MYSQL_USER}
- MYSQL_PASSWORD=${MYSQL_PASSWORD} and the tunnel uses ssh config for simplicity;
Replace host and user. Not using SSL for the isolated test (yet), but RDS/Aurora does. The mysql IP address is usually a |
Ok, so just to be clear, looks like your set-up is:
Quick Question:You're using I'd thought |
Yes, happy to explain what The flow; Besides this Digital Ocean droplet isolated test, there is the EC2 > RDS which is technically a totally different setup but in terms of an ssh tunnel it is almost identical, just replace 172.x.x.x with the RDS dns record (after ensuring the EC2 host you ssh to can resolve that RDS dns record) |
Thanks, I'll test this today |
This is working in my latest build. I used the same docker-compose config as you, sshing onto a GCP box and then connecting to mysql on I have a few things to tidy up but my goal is to push out a new release this week with the fixes. |
@rathboma amazing! |
When using a postgres database with an ssh tunnel, beekeeper shows that the database has no tables.
The text was updated successfully, but these errors were encountered: