[GH-ISSUE #132] ssh tunnel connection timeout #79

New issue

Closed

opened 2026-05-05 11:00:01 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented 2026-05-05 11:00:01 -06:00

Owner

Copy link

Originally created by @dipenpatel235 on GitHub (May 28, 2021).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/132

@mmatczuk
I want to ssh on system(172.16.209.145) from client using this tunnel solution tool.
so i am not able to do that.
getting timeout error.(attached screenshot of that)
added my architecture diagram screenshot and also i have added my tunnel.yml file content in that screenshot

i am trying to execute below command from client

ssh -p 2222 ubuntu@192.168.0.25

let me know what things are wrong so i can fix it.

Thanks

Originally created by @dipenpatel235 on GitHub (May 28, 2021). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/132 @mmatczuk I want to ssh on `system(172.16.209.145)` from `client` using this tunnel solution tool. so i am not able to do that. getting timeout error.(attached screenshot of that) added my architecture diagram screenshot and also i have added my `tunnel.yml` file content in that screenshot i am trying to execute below command from `client` ``` ssh -p 2222 ubuntu@192.168.0.25 ``` let me know what things are wrong so i can fix it.   Thanks

gitea-mirror closed this issue 2026-05-05 11:00:05 -06:00

gitea-mirror commented 2026-05-05 11:00:06 -06:00

Author

Owner

Copy link

@hons82 commented on GitHub (Jun 1, 2021):

Why 2222? Do u have that port open somewhere?

<!-- gh-comment-id:851808117 --> @hons82 commented on GitHub (Jun 1, 2021): Why 2222? Do u have that port open somewhere?

gitea-mirror commented 2026-05-05 11:00:07 -06:00

Author

Owner

Copy link

@dipenpatel235 commented on GitHub (Jun 1, 2021):

@hons82 2222 post because if i used 22 then its saying to me already in used.

<!-- gh-comment-id:851822528 --> @dipenpatel235 commented on GitHub (Jun 1, 2021): @hons82 2222 post because if i used 22 then its saying to me already in used.

gitea-mirror commented 2026-05-05 11:00:09 -06:00

Author

Owner

Copy link

@hons82 commented on GitHub (Jun 1, 2021):

From the message it looks like the port 2222 is not opened on that machine

<!-- gh-comment-id:851878255 --> @hons82 commented on GitHub (Jun 1, 2021): From the message it looks like the port 2222 is not opened on that machine

gitea-mirror commented 2026-05-05 11:00:11 -06:00

Author

Owner

Copy link

@dipenpatel235 commented on GitHub (Jun 1, 2021):

@hons82 can u tell me in which server i need to keep open that port (client, server ,or system as per above architecture diagram)?

<!-- gh-comment-id:851880046 --> @dipenpatel235 commented on GitHub (Jun 1, 2021): @hons82 can u tell me in which server i need to keep open that port (client, server ,or system as per above architecture diagram)?

gitea-mirror commented 2026-05-05 11:00:12 -06:00

Author

Owner

Copy link

@hons82 commented on GitHub (Jun 1, 2021):

Wait a sec. I think there is something wrong in this constellation.

• tunneld needs to run on a machine that is public available
• tunnel needs to run on a private machine, so a machine that you want to access from everywhere, but it is tecnically hidden by let's say a firewall
• In your configuration file addr needs to be some address under which you wanna call the client

Now you can access the machine where tunnel is running from outside by calling ssh <addr>.

Speaking in the words of your diagram you should be able to call ssh -p 2222 ubuntu@192.168.0.25 on the machine called system (or any other machine) to access the client, but not viceversa.

<!-- gh-comment-id:851908553 --> @hons82 commented on GitHub (Jun 1, 2021): Wait a sec. I think there is something wrong in this constellation. - tunneld needs to run on a machine that is public available - tunnel needs to run on a private machine, so a machine that you want to access from everywhere, but it is tecnically hidden by let's say a firewall - In your configuration file addr needs to be some address under which you wanna call the client Now you can access the machine where tunnel is running from outside by calling `ssh <addr>`. Speaking in the words of your diagram you should be able to call `ssh -p 2222 ubuntu@192.168.0.25` on the machine called system (or any other machine) to access the client, but not viceversa.

gitea-mirror commented 2026-05-05 11:00:13 -06:00

Author

Owner

Copy link

@dipenpatel235 commented on GitHub (Jun 1, 2021):

@hons82 i got your point and founded my mistake. so let me try it as per given by you and update you once testing done .

Thanks for your valuable time.

<!-- gh-comment-id:851923709 --> @dipenpatel235 commented on GitHub (Jun 1, 2021): @hons82 i got your point and founded my mistake. so let me try it as per given by you and update you once testing done . Thanks for your valuable time.

gitea-mirror commented 2026-05-05 11:00:14 -06:00

Author

Owner

Copy link

@dipenpatel235 commented on GitHub (Jun 5, 2021):

@hons82 its working fine.
thanks you so much for your help.

<!-- gh-comment-id:855180589 --> @dipenpatel235 commented on GitHub (Jun 5, 2021): @hons82 its working fine. thanks you so much for your help.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dependabot/go_modules/golang.org/x/net-0.38.0

revert-110-hotfix/dependency

mmt/websocket

mmt/old-websocket

2.1

v.2.0

v.1.2

v.1.1

v.1.0

Labels

Clear labels   

pull-request

Mirrored from GitHub Pull Request

No labels

pull-request

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/go-http-tunnel#79

No description provided.