Go HTTP tunnel is a reverse tunnel based on HTTP/2. It enables you to share your localhost when you don't have a public IP.
Features:
Common use cases:
Build the latest version.
$ go get -u github.com/mmatczuk/go-http-tunnel/cmd/...
Alternatively download the latest release.
There are two executables:
tunneld - the tunnel server, to be run on publicly available host like AWS or GCEtunnel - the tunnel client, to be run on your local machine or in your private networkTo get help on the command parameters run tunneld -h or tunnel -h.
Tunnel requires TLS certificates for both client and server.
$ openssl req -x509 -nodes -newkey rsa:2048 -sha256 -keyout client.key -out client.crt
$ openssl req -x509 -nodes -newkey rsa:2048 -sha256 -keyout server.key -out server.crt
Run client:
tunnel binary.tunnel directory in your project directoryclient.key, client.crt to .tunneltunnel.yml in .tunnel$ tunnel -config ./tunnel/tunnel.yml start-all
Run server:
tunneld binary.tunneld directoryserver.key, server.crt to .tunneld$ tunneld -tlsCrt .tunneld/server.crt -tlsKey .tunneld/server.key
This will run HTTP server on port 80 and HTTPS (HTTP/2) server on port 443. If you want to use HTTPS it's recommended to get a properly signed certificate to avoid security warnings.
The tunnel client tunnel requires configuration file, by default it will try reading tunnel.yml in your current working directory. If you want to specify other file use -config flag.
Sample configuration that exposes:
localhost:8080 as webui.my-tunnel-host.comlooks like this
server_addr: SERVER_IP:5223
tunnels:
webui:
proto: http
addr: localhost:8080
auth: user:password
host: webui.my-tunnel-host.com
ssh:
proto: tcp
addr: 192.168.0.5:22
remote_addr: 0.0.0.0:22
Configuration options:
server_addr: server TCP address, i.e. 54.12.12.45:5223tls_crt: path to client TLS certificate, default: client.crt in the config file directorytls_key: path to client TLS certificate key, default: client.key in the config file directoryroot_ca: path to trusted root certificate authority pool file, if empty any server certificate is acceptedtunnels / [name]proto: tunnel protocol, http or tcpaddr: forward traffic to this local port number or network address, for proto=http this can be full URL i.e. https://machine/sub/path/?plus=params, supports URL schemes http and httpsauth: (proto=http) (optional) basic authentication credentials to enforce on tunneled requests, format user:passwordhost: (proto=http) hostname to request (requires reserved name and DNS CNAME)remote_addr: (proto=tcp) bind the remote TCP addressbackoffinterval: how long client would wait before redialing the server if connection was lost, exponential backoff initial interval, default: 500msmultiplier: interval multiplier if reconnect failed, default: 1.5max_interval: maximal time client would wait before redialing the server, default: 1mmax_time: maximal time client would try to reconnect to the server if connection was lost, set 0 to never stop trying, default: 15mClient opens a TLS connection to a server. Server accepts connections from known clients only, client is recognised by it's TLS certificate ID. The server is publicly available and proxies incoming connections to the client. Then the connection is further proxied in the client's network.
Tunnel is based HTTP/2 for speed and security. There is a single TCP connection between client and server and all the proxied connections are multiplexed using HTTP/2.
If this project help you reduce time to develop, you can give me a cup of coffee.
A GitHub star is always appreciated!
Copyright (C) 2017 Michał Matczuk
This project is distributed under the AGPL-3 license. See the LICENSE file for details. If you need an enterprice license contact me directly.
$ claude mcp add go-http-tunnel \
-- python -m otcore.mcp_server <graph>