[GH-ISSUE #85] how to Access Local Server machine from Client machine #45

New issue

Open

opened 2026-05-05 10:58:30 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 10:58:30 -06:00

Owner

Originally created by @mihir893 on GitHub (Aug 30, 2018).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/85

I have implemented go-http-tunnel on my two local machines. one is as client & another one is as Server. I successfully configured server & client side both & don't get any error & on client side I get message : "level 1 action handshake addr <SERVER_IP:5223>" & on server side retrieve message of Client connected with my client Id , but now issue is How can i access my server machine from Client?. Please Guide me for that.

Below are screenshots of my server side configuration & Client Side Configuration respectively:

Server Side CLI screenshot :

Client Side CLI screenshot :

Below is code of my tunnel.yml file configured :

server_addr: 192.168.0.121:5223
tunnels:
mihir:
proto: http
addr: localhost:3001
host: mihir.mytunnel.com
ssh:
proto: tcp
addr: 192.168.0.5:22
remote_addr: 0.0.0.0:22

Originally created by @mihir893 on GitHub (Aug 30, 2018). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/85 I have implemented go-http-tunnel on my two local machines. one is as client & another one is as Server. I successfully configured server & client side both & don't get any error & on client side I get message : "level 1 action handshake addr <SERVER_IP:5223>" & on server side retrieve message of Client connected with my client Id , but now issue is How can i access my server machine from Client?. Please Guide me for that. Below are screenshots of my server side configuration & Client Side Configuration respectively: 1) Server Side CLI screenshot : ![server_screen_shot](https://user-images.githubusercontent.com/24749056/44867642-0730fe00-aca6-11e8-8b86-d4f1ea00b066.png) 2) Client Side CLI screenshot : ![untitled115](https://user-images.githubusercontent.com/24749056/44867663-1adc6480-aca6-11e8-889c-148ccebc3f1a.png) Below is code of my tunnel.yml file configured : --- server_addr: 192.168.0.121:5223 tunnels: mihir: proto: http addr: localhost:3001 host: mihir.mytunnel.com ssh: proto: tcp addr: 192.168.0.5:22 remote_addr: 0.0.0.0:22

gitea-mirror commented

2026-05-05 10:58:32 -06:00

Author

Owner

@bmcgonag commented on GitHub (Mar 31, 2019):

@mihir893 I think you may be misunderstanding the purpose here. This project allows you to host a tunneld server that will accept connections from a tunnel client. Then from another machine you bring up the web-address (ip address) of the server with the specific client information to access a server on the client machine.

For instance, I run a nodejs server on my development machine. I can hit it fine from within my own network for testing my application. However, I'm using geo-location services to track locations, so it's important for me to be able to test from outside my own network while driving around, and to have an https connection to my development machine running my nodejs server.

I use the tunneld server on digital ocean, and setup an A-record in DNS for the * (wildcard subdmain) for that server, so that any request to *..org will go to that server and the tunneld service.

depending on what subdomain name I request (the first part of the url) testserver..org, I have my development machine setup as a client with the tunnel service, and it registers itself with the server as that subdomain. So now, when I go to testserver..org on my phone, it opens my web application running on my development machine and allows me to test without having to setup my router to allow traffic through a specific port, and it also gives me the ability to have https using the certificates I created in the readme.

Hope this helps,

@bmcgonag commented on GitHub (Mar 31, 2019): @mihir893 I think you may be misunderstanding the purpose here. This project allows you to host a tunneld server that will accept connections from a tunnel client. Then from another machine you bring up the web-address (ip address) of the server with the specific client information to access a server on the client machine. For instance, I run a nodejs server on my development machine. I can hit it fine from within my own network for testing my application. However, I'm using geo-location services to track locations, so it's important for me to be able to test from outside my own network while driving around, and to have an https connection to my development machine running my nodejs server. I use the tunneld server on digital ocean, and setup an A-record in DNS for the * (wildcard subdmain) for that server, so that any request to *.<whatever domain you register>.org will go to that server and the tunneld service. depending on what subdomain name I request (the first part of the url) testserver.<whatever domain you register>.org, I have my development machine setup as a client with the tunnel service, and it registers itself with the server as that subdomain. So now, when I go to testserver.<whatever domain you register>.org on my phone, it opens my web application running on my development machine and allows me to test without having to setup my router to allow traffic through a specific port, and it also gives me the ability to have https using the certificates I created in the readme. Hope this helps,