Repository navigation
Home Server Behind a VPN
Run one engine on a home server, with its peer-to-peer traffic leaving through a VPN, and play from any device on the LAN: VLC on a laptop, or the Android app on a phone or television using it as a remote engine. Client devices need no engine and no VPN of their own.
| Report | Details |
|---|---|
| Source | Outpace maintainers |
| Reported | 2026-11-15 |
| Versions | Outpace v1.2.1 (.deb package); Android app v1.0.0 |
| Host | Proxmox VE, unprivileged Debian LXC container |
| Network | A VPN client inside the container; the LAN stays reachable outside the tunnel |
| Players | VLC on desktop and Android; the Android app with a remote engine |
| Works on | Any Linux machine: a Proxmox container or VM, another hypervisor, or bare metal. The steps use Debian or Ubuntu with systemd. |
Proxmox is only how the machine is split up. On bare metal, or in any other VM, skip step 1 and do the rest on the host. Keep the engine in the same network namespace as the VPN, so its peer traffic follows the tunnel while players reach it on the LAN.
Create an unprivileged Debian container with a static LAN address, outside the router's DHCP
pool. VPN clients need the TUN device, so pass it through in /etc/pve/lxc/<id>.conf:
unprivileged: 1
net0: name=eth0,bridge=vmbr0,gw=192.168.1.1,ip=192.168.1.20/24,type=veth
lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dirThe examples use 192.168.1.20 for the container. Add features: nesting=1,keyctl=1 only if you
run the engine in Docker inside it.
Install and connect your VPN client inside the container, then check two things:
-
Traffic leaves through the tunnel:
curl https://ifconfig.meshows the VPN's address, not your home one. -
The LAN still answers: the container can ping another device on
192.168.1.0/24. Most clients keep local routes by default or have an "allow LAN access" switch; without it, players cannot reach the engine.
Make the VPN start at boot and reconnect on its own, and turn on its kill switch (also called
"block connections without VPN" or "lockdown"). Without one, peer traffic falls back to your home
connection whenever the tunnel drops, and the ifconfig.me check only proves the route while
the tunnel is up. If your client has no kill switch, add firewall rules that drop outgoing
traffic on every interface except the tunnel and loopback (lo), allowing only the LAN and the
VPN server. In the container that is eth0; on bare metal, check ip link for names such as
enp3s0 or wlan0.
Apply the same rules to IPv6, or turn IPv6 off: tunneling IPv6 while connected is not enough if
it falls back to the home route when the tunnel drops.
Download the package for the container's architecture from the releases page and install it. On x86_64:
curl -LO https://github.com/outpace-stream/outpace-engine/releases/download/v1.2.1/outpace_1.2.1_amd64.deb
sudo apt install ./outpace_1.2.1_amd64.deb
sudoedit /etc/outpace/outpace.envOn ARM, use outpace_1.2.1_arm64.deb or outpace_1.2.1_armhf.deb. On Fedora and other RPM
distributions, use the .rpm with dnf; see
Installation. Without systemd, run the
release binary with the same settings.
Set at least:
OUTPACE_BIND=192.168.1.20:6878 # reachable from the LAN
OUTPACE_ACE_COMPAT=true # app shows the engine version; AceStream-API players workAdd OUTPACE_COMPAT_ACESTREAM_SERVICES=true if you want Stream Search in the
app, and OUTPACE_ENABLE_CAST=1 to cast to televisions. Then start it. With systemd:
sudo systemctl enable --now outpace
journalctl -u outpace -f # look for "listening on http://192.168.1.20:6878"Without systemd, run outpace serve with the same variables from your init system; see
Deployment for other service managers.
The Docker image works too; run it with --network host so it
shares the container's VPN.
VLC, on any computer or phone on the LAN: open a network stream (Media → Open Network Stream on desktop, Browse → New stream on Android) with
http://192.168.1.20:6878/streams/ace/0123456789abcdef0123456789abcdef01234567
Replace the placeholder with a real content id. Append .m3u8 for HLS.
Android app, on a phone or Android TV: Settings → Engine connection → Add a
remote engine, address 192.168.1.20:6878. The app then lists the engine's streams and hands
the player the server's URL, so video goes straight from the server to the player. See
Remote engines
in the app guide.
-
Inbound peers: behind most VPNs the engine downloads normally but no peer can connect in,
so it uploads less. If your VPN forwards a port, set
OUTPACE_PEER_LISTEN=0.0.0.0:<forwarded port>; see Seeding and Peers. Cloudflare WARP needs an extra fix, covered in Deployment. - Security: the API has no password. Keep the bind on the LAN address, and never forward 6878 on the router. See Exposing the API safely.
- One engine, many viewers: viewers of the same stream share one download. Each extra stream adds its own buffers; Configuration lists the limits.
This wiki is generated from docs/wiki/ in the main repository. To fix or improve a page, open a pull request there; the wiki is republished automatically when it merges, and edits made in the wiki web UI are overwritten.
Start
Watching
Publishing and peers
- Broadcasting
- Seeding and Peers
- Engine Camouflage
- NAT and Port Mapping
- Private Peer Mode
- Outbound Proxy
Running it
- Deployment
- Routers and Small Devices
- Migrating from AceStream Engine
- Support Sources and Operations
- Troubleshooting
- Releases and Versions
Success stories