Closed Adesanya-Toba closed 2 months ago
Hi all, any thoughts on this, as I think it might be a small thing I'm missing?
As I said, it works when I use my local machine (i.e., laptop running the local proxy) as the source device but fails when I use the AWS console as the source device.
Hey @Adesanya-Toba thanks for opening this issue. I was able to quickly reproduce the same error you are seeing. Do you know if this happening as a result of a recent update? (if you used a previous version of the localproxy, was it working before?)
Hi @RogerZhongAWS, thanks for checking this out. No, I haven't tested earlier versions of the local proxy.
@Adesanya-Toba , In a recent update, we actually added a new CLI option that the user needs to pass when connecting the localproxy to tunnel clients that only support older versions of the protocol. Because the console uses an older version of the protocol (V1) you will need to pass in --destination-client-type V1
into your localproxy run command (or add it within your config)
I also realize that the existing documentation may be a little confusing to understand, will take a moment to fix that.
Oh, alright. Thanks, I'll give this a spin and feedback.
Hi @RogerZhongAWS, yeah that did the trick! 🎉
Any plans to update the local proxy protocol on the console though?
Can't answer that yet by myself, will need to consult with various people internally.
Describe the bug After starting the local proxy on my destination device, I attempt to open an SSH connection to the device using the username and password field from the AWS console. This results in an error in the local proxy running on the destination device, causing the device to disconnect.
To Reproduce
Expected behavior
Actual behavior
Logs
AWS Console Screenshot Error appears as soon as I click connect from the Cosole.
Console connection fails (
Connect
button is greyed out) and requires a token rotation.Environment (please complete the following information):
Additional context NOTE: I am able to successfully connect when using the local proxy on my machine as the source device! The failure only happens when I try to connect via the AWS console.
I pulled the latest Debian base image and built the local proxy inside Docker for my platform. I ran it with the binary image and obtained the same error.