AllowTcpForwarding

2024-11-24

actual solution

It turns out that the SSH Agent does not have access to the list of keys that the ssh command accesses by default. See Couldn't continue authentication for how to fix this.

2024-11-04

resolution

I was able to connect by giving BK access to my private key file, instead of using the SSH Agent. The Agent always worked before, but there are some indications that the current version of BK has a bug around that, so hopefully they'll fix it soonish. In the meantime, this will do.

problem

• I need to understand how ssh port forwarding works so I can get Beekeeper working on SamTheMachine.
• I think the first thing I need to understand is how to see if it's already active.
• This tells me that it's something you do on the remote host, not the local machine.
• ...but if that's the case, then it's not what's preventing Beekeeper from connecting -- because I can connect from another machine to the same db server via a tunnel configured the same way.
  • If it needs to be set up on the remote (which I don't think I ever did, for any of the machines I'm using), it's already been done.
  • So the problem must be a local config issue.
• ...but I need to determine for certain that it's not an issue with ssh tunneling, so I can be sure I'm not wasting my time exploring the vast desert plain of other options.
• Information in trouble-tickets on the Beekeeper Studio github repository suggest that it may be a problem with the current version of BK.

Links

• 2022-09-17 Enable SSH Port Forwarding with Examples