Show HN: wireport – lightweight ingress+DNS+VPN for self-hosted apps behind NAT

2 points

7 months ago

I built wireport to easily and securely host, manage, and access self-hosted workloads across multiple environments. It started as a set of scripts and gradually became a lightweight solution, tackling some of the most common challenges I've encountered -- ready to run in about 5 minutes with just a few terminal commands.

wireport is an open-source, self-hosted ingress proxy and VPN tunnel. Among its advantages: it requires no config tinkering and makes your remote self-hosted services accessible locally by their Docker container names (e.g., `grafana-dashboard:8080` in your browser to access a self-hosted grafana dashboard).

- GitHub: https://github.com/MultionLabs/wireport

- Quick setup tutorial: https://youtu.be/9wvxT-QOZ2Q

Common use cases:

- exposing self-hosted services from behind NAT: from laptop, private servers, home lab/NAS devices

- secure access to internal dashboards, databases, development tools, and game servers from anywhere

- sharing locally-hosted demos securely with colleagues or clients

- safely accessing services from IoT and edge devices

- enabling docker workloads from different nodes to talk to each other

Some highlights:

- automatic handling of TLS (HTTPS) certificates — free provisioning and renewal

- support for raw TCP and UDP, as well as protocols built on top of them

- support for HTTP Basic Auth for HTTP/HTTPS tunnels

- declarative tunnel configuration via Docker labels

- written in Go, powered by CoreDNS, Caddy, and WireGuard

- builds available for macOS, Linux and Windows (amd64 & arm64 versions)

wireport is for developers, tinkerers, and home lab enthusiasts who want secure, easy access to their private services from anywhere.

I'd love to hear from fellow self-hosters about your experiences — what challenges are you facing and how are you solving them currently?

Happy to read any feedback and questions!