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

how to ssh to a client through boring proxy? #7

Open
techiezia opened this issue Mar 29, 2021 · 11 comments
Open

how to ssh to a client through boring proxy? #7

techiezia opened this issue Mar 29, 2021 · 11 comments

Comments

@techiezia
Copy link

how to ssh to a client through boring proxy?

@anderspitman I want to ssh to a server on with private IP. can we use boringproxy to make it possible?

If so then what are the steps involved.

Thanks!

@luke2m
Copy link
Contributor

luke2m commented Mar 31, 2021

@techiezia Do you have boringproxy set up? If so, just add a tunnel on port 22.

@techiezia
Copy link
Author

1
2
3
4

@luke2m my boringproxy working fine for http server but when i tunnel my ssh, it got created but when i try to access it i'm getting [email protected]: Permission denied (publickey,password)
i have attached the screenshot for reference

@luke2m
Copy link
Contributor

luke2m commented Mar 31, 2021

It looks like you are inputting your password incorrectly.

@techiezia
Copy link
Author

@luke2m No I'm inputting a valid password. If I'm doing ssh on a local lan the same password is working.

@luke2m
Copy link
Contributor

luke2m commented Mar 31, 2021

Hmm, it’s working for me. Could you try passwordless authentication?

@anderspitman
Copy link
Member

If I understand correctly what you're trying to accomplish, everything looks good except you need to use the correct tunnel port when connecting over SSH:

ssh -p 35269 ubuntu.thenextnerd.com

By default you'll get a random port when you create the tunnel, but you can also choose the port by setting Tunnel Port.

@anderspitman
Copy link
Member

Basically the commands you ran are trying to SSH into the machine running boringproxy server, not the machine you're tunneling to.

This is one of those classic situations with tunneling where it's really hard to keep straight what is what.

@techiezia
Copy link
Author

techiezia commented Mar 31, 2021

hi @anderspitman thanks for your reply.

Now when i'm using proper port i'm getting this response.

image

@anderspitman
Copy link
Member

I don't have any more guesses about what might be wrong. It certainly could be a bug in boringproxy, but as they say, "it works on my machine". My suggestion would be to try running something simpler than SSH. Maybe an HTTP server or even netcat. Make sure it's even getting through to the port. If so then there's probably something wrong with your SSH setup. Try SSHing in from a machine on the same network and see if that gives you any clues.

@techiezia
Copy link
Author

@anderspitman thanks for your suggestions...

  • HTTP server with my boringproxy server is working fine.
  • SSHing form the same network is woking fine.

Only SSH through boringproxy is not woking...

@anderspitman
Copy link
Member

Shoot, sorry it's still not working. I'll leave this issue open. Maybe another developer will run into the same problem and have time to find the root cause.

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

3 participants