I run quite a few services on my home server — alist, Open WebUI, and a handful of small projects of my own.
My previous setup used DDNS to pin down my dynamic public IP, with Nginx Proxy Manager in front to reverse-proxy everything to my LAN services.
The catch: residential broadband blocks certain ports — 80 (HTTP) and 443 (HTTPS) included — which forced me to reach alist at https://alist.mihouo.com:8443. Since 443 was blocked, Nginx Proxy Manager had to listen on 8443 and proxy through to 443.
My end goal was simple: kill the :8443 for good, so I could open https://alist.mihouo.com like a normal site.
FRP (Fast Reverse Proxy) is a high-performance reverse proxy application built for NAT traversal. It exposes services on a local network to the public internet, working around NAT and firewall restrictions. FRP consists of two parts: frps (the server) and frpc (the client). The idea is to tunnel an internal service out through a proxy so the outside world can reach it.
Client (frpc): usually runs inside the LAN; it forwards local service traffic out over the tunnel.
Server (frps): usually runs on a machine with a public IP; it receives requests from the outside and relays them to the corresponding local service.
frpc and frps communicate over a single TCP connection. frps acts as the proxy front end, accepting external requests and forwarding them to the right internal service, while frpc picks up whatever frps sends and hands it to the local service.
For reasons I never fully tracked down, launchctl kept failing with failed: 5: Input/output error even though my config file was fine. In the end I just ran frpc inside tmux.