So today we're gonna learn a tool called chisel, from the same creator of overseer that I usually use to graceful restart production service.
What chisel can do? It can forward traffic from private network to public network, for example if you have service/port that only accessible from your internal network, and you want it to be exposed/tunneled to server that has public IP/accessible from outside, but only for the case when you cannot use reverse proxy because the reverse proxy cannot access your private server (eg. because it protected by firewall or doesn't have public IP at all).
internet --> public server <-- internet <-- private server/localhost
<--> tunnel <-->
You can first install chisel by running this command
go install github.com/jpillora/chisel@latest
or download the binary directly.
Then in the public server (server with public IP), you can do something like this:
chisel server --port 3229 --reverse
this would listen to port 3229 for tunnel requests.
On the client/private network that you want to be exposed to public you can run this command:
chisel client http://publicServerIP:3229 R:3006:127.0.0.1:3111
The command above means that on the server, there will be port 3006 listened, any traffic that goes to that port, will be forwarded to client to port 3111.
After that you can add https for example using caddy (don't forget to add DNS first so letsencrypt can get the proper certificate):
https://myWebSite.com {
reverse_proxy localhost:3006
}
Other alternatives are cloudflare tunnel, but it requires you to setup network and other stuff in their website (not sure what they will charge you for excess traffic), there's also ngrok (the original, but now a paid service), localtunnel (but it always dead after few requests).
More alternative and resources here:
