frp | Support by cloudimg

Overview

frp is a fast, high performance reverse proxy that lets you expose a local server sitting behind NAT or a firewall to the public internet. An frps server runs on a host with a public IP, and frpc clients running next to your private services connect out to it and register tunnels, so traffic to the public server is forwarded back to the private service over a single persistent connection. This image delivers the frps server fully installed and configured as a system service, with the built in web dashboard ready to use, so a production grade reverse proxy gateway is running within minutes of launch.

Application Stack

The frps server binary installed under /opt/frp and run by a dedicated unprivileged service account. The server configuration in /etc/frp and the server runtime state on a dedicated data disk so it is independently resizable. A systemd service that starts frps on boot and restarts it on failure. The built in frps web dashboard published on port 80 through an nginx reverse proxy. The frpc client binary is also installed so you can immediately test a tunnel from the same host.

Reverse Proxy Server

frps listens on the control port (7000) for frpc clients and supports TCP, UDP, HTTP, HTTPS, STCP and other proxy types. Clients authenticate to the server with a shared token, register named proxies, and frp forwards public traffic to the matching private service. Use it to publish a home or office service, give a remote teammate access to an internal tool, or expose a development server for a webhook callback, all without opening inbound firewall ports on the private network.

Secure First Boot

On the first boot of your instance a one shot service generates a fresh dashboard password and a fresh server authentication token, both unique to that instance, writes them into the frps configuration and writes them to a root only file. The dashboard binds to loopback only and is published through an authenticating proxy. No shared or default credentials ship in the image.

Ready To Use

The frps web dashboard is served on port 80 through nginx. Sign in with the generated administrator credentials to see connected clients, active proxies, per proxy traffic counters and the server version. Point an frpc client at the instance on the control port using the generated server token to register your first tunnel.

cloudimg Support

24/7 technical support by email and chat. Help with deployment, frpc client configuration, proxy type selection, the dashboard, token and dashboard credential rotation, TLS and tuning.

Use Cases

Expose a service behind NAT or a firewall to the public internet. Publish a home lab or office service without a static public IP on the private network. Receive webhooks on a local development server. Give remote access to an internal tool over an authenticated tunnel. Self host an alternative to commercial tunnelling services.

All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.