I’m looking for an easy way to expose internal access for an internal web interface. I feel like I’m close with fly.io, but I’m not sure if it’s actually the right tool.
I have an internal service that exposes a web interface. I want to be able to pop up a public URL so I can access the internal server outside of my local network.
I followed the steps in the Private Networking docs to create a wireguard tunnel and add my internal server as a peer. Then, I created a Docker image for an nginx reverse proxy that forwarded HTTP requests to the peer’s hostname, but when I I deploy it, loading it in the browser just says “connection reset.”
I tried referring to the internal server as both
my-servers-hostname.internal, but neither worked. If I deploy my nginx server to fly, I can ping it from the internal server that’s peered over WireGuard, but I’m not sure if the fly.io VM is seeing the peer.
Here are my fly, Docker, and nginx config files
Is what I’m doing possible with fly? Or am I trying to force a square peg in a round hole?