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
Details:
I have seen a lot of results about this connection error, for example in #1240. The two main issues people have been running into are:
Enabling TCP Forwarding
Certain RSA key types need to be accepted on the server
I believe I am having a different problem. I was previously using an Ubuntu client to connect to an Ubuntu server. Now I'm using a Debian client to connect to the same server and am unable to establish the tunnel within Beekeeper.
Version Information [might be relevant to your issue]
Operating System: Debian 12, freshly downloaded/installed last night
App Version [help -> about]: 4.1.13, downloaded from github and installed last night
Database type and version [eg Posgresql 9.3]: MariaDB Ver 15.1 Distrib 10.1.37-MariaDB, for Linux (x86_64) using readline 5.1
Client key types: ed25519 (old and new keys)
I have passwordless ssh keys installed and working
Beekeeper says that it has found the SSH agent
I can create a working tunnel manually (ssh -L10000:localhost:3306 servername) and connect to it directly
Using a manual tunnel confirms that the database credentials are correct
Debug Console: error watch null mysql tunnel.ts:49 tunnel/ GOT TUNNEL PORT 10000 tunnel.ts:57 tunnel config: {fromPort: 10000, toPort: 3306, toHost: 'localhost'} ConnectionInterface.vue?8c7e:81 error watch Error: Database Connection Error: SSH Tunnel Connection Error: All configured authentication methods failed at ov (client.ts:285:11) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async b.test (index.ts:321:69) mysql
Additionally, this looks like it could be related to mscdex/ssh2#352 however as mentioned above, I had a working tunnel under Ubuntu, I reinstalled with Debian and generated new ed25519 keys, now the new connection won't open.
I'm stumped. The best guess I have is that Beekeeper is incorrectly reporting a SSH agent, the agent isn't seeing the key, or that this is another compatibility issue with the SSH library used. For now I'll have to rely on manually creating SSH tunnels. If there are any other logs that can help I'd be happy to provide them. Any suggestions welcome, thanks!
The text was updated successfully, but these errors were encountered:
Details:
I have seen a lot of results about this connection error, for example in #1240. The two main issues people have been running into are:
I believe I am having a different problem. I was previously using an Ubuntu client to connect to an Ubuntu server. Now I'm using a Debian client to connect to the same server and am unable to establish the tunnel within Beekeeper.
Version Information [might be relevant to your issue]
Operating System: Debian 12, freshly downloaded/installed last night
App Version [help -> about]: 4.1.13, downloaded from github and installed last night
Database type and version [eg Posgresql 9.3]: MariaDB Ver 15.1 Distrib 10.1.37-MariaDB, for Linux (x86_64) using readline 5.1
ssh -L10000:localhost:3306 servername
) and connect to it directlyDebug Console:
error watch null mysql tunnel.ts:49 tunnel/ GOT TUNNEL PORT 10000 tunnel.ts:57 tunnel config: {fromPort: 10000, toPort: 3306, toHost: 'localhost'} ConnectionInterface.vue?8c7e:81 error watch Error: Database Connection Error: SSH Tunnel Connection Error: All configured authentication methods failed at ov (client.ts:285:11) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async b.test (index.ts:321:69) mysql
Additionally, this looks like it could be related to mscdex/ssh2#352 however as mentioned above, I had a working tunnel under Ubuntu, I reinstalled with Debian and generated new ed25519 keys, now the new connection won't open.
I'm stumped. The best guess I have is that Beekeeper is incorrectly reporting a SSH agent, the agent isn't seeing the key, or that this is another compatibility issue with the SSH library used. For now I'll have to rely on manually creating SSH tunnels. If there are any other logs that can help I'd be happy to provide them. Any suggestions welcome, thanks!
The text was updated successfully, but these errors were encountered: