FRP Manager is a self-hosted web panel for frps and frpc. Open ports, filter who reaches them, read the logs and update frp, without editing TOML files over SSH.
The panel finds your frp services on its own, systemd units and Docker containers alike, and keeps your configuration files as plain TOML.
Every tunnel is listed as the path it opens, vps.example.net:25565 → 127.0.0.1:25565. The guided editor covers tcp, udp, http, https, stcp, xtcp and visitors, with PROXY protocol, encryption and compression. Settings it does not handle are kept as they are.
Decide who can connect to the ports frps opens: allow only, or block, by address, network or whole provider (AS number, prefixes fetched from RIPEstat). Rules are applied in the kernel with nftables, before Docker's NAT, and keep working if the panel stops.
Follow the systemd journal, a log file or a Docker container as it is written, over WebSocket with an automatic fallback. Errors and warnings stand out, and a filter narrows the lines down.
frps and frpc services, binaries, configs and Docker containers, one card each.
frps and frpc settings in sections; TOML is checked before it is written.
frp downloaded and checked against its published SHA-256; the panel updates itself.
Run the panel in a container and drive frp on the host, or manage frp containers.
Readable on desktop and mobile, in English and French.
Mandatory setup, argon2id passwords, CSRF protection, localhost only.
The live demo runs the real interface with sample data. Everything can be clicked; nothing is actually changed, and it resets when you close the tab.
On the machine that runs frps or frpc. The panel installs frp for you if it is missing.
Download the compose file and start the container
curl -O https://raw.githubusercontent.com/Gogowwww/frp-manager/main/docker-compose.yml
docker compose up -dReach the panel through an SSH tunnel: it only listens on 127.0.0.1
ssh -L 8765:127.0.0.1:8765 user@serverOpen https://127.0.0.1:8765 and create the administrator account
Download the latest release and run the installer as root
curl -LO https://github.com/Gogowwww/frp-manager/releases/latest/download/frp-manager.zip
unzip frp-manager.zip && cd frp-manager && sudo bash install.shReach the panel through an SSH tunnel: it only listens on 127.0.0.1
ssh -L 8765:127.0.0.1:8765 user@serverOpen https://127.0.0.1:8765 and create the administrator account
Opening the panel to your network, reverse proxy, configuration keys: installation guide.
frp is a single binary configured by TOML files. Running it by hand works well; managing it day to day is where the time goes. FRP Manager keeps the same files and adds a layer on top.
| Task | frp by hand | With FRP Manager |
|---|---|---|
| Add or change a tunnel | Edit frpc.toml, restart frpc | Guided form, TOML checked, save and restart in one click |
| See what is exposed | Read the configs | List of ports with their path, per client |
| Several frps or frpc | One unit and one file per instance to track | Detected automatically, one card each |
| Filter who reaches frps | Write nftables or iptables rules | Rules by IP, network or AS, tested before applying |
| Follow the logs | journalctl -fu frpc over SSH | Live logs in the browser |
| Update frp | Download, check, replace the binaries, restart | One click, SHA-256 checked, services restarted |
Removing the panel leaves frp running as before: your configuration stays plain TOML.
The panel controls exposed ports and runs as root, so it starts locked down.
Until an administrator account exists, the initial setup page is the only thing it serves.
Hashed with argon2id, 12 characters minimum, attempts limited per IP.
A new install listens on 127.0.0.1; opening it to the network is your call.
CSRF tokens, strict cookies, Content-Security-Policy, no clickjacking.
frp archives and panel updates are verified against their published SHA-256.
Commands are argument lists, names are allow-listed, archives extracted safely.
Using Docker? The container uses pid: host and nsenter to drive systemd on the host: that is root-equivalent access to the host. What it implies.
Threat model and vulnerability reporting: security policy.
No. FRP Manager drives the official frps and frpc binaries and reads and writes their usual TOML files. You can keep editing them by hand, and frp keeps running if you remove the panel.
No. The install script downloads frps and frpc, creates their systemd services and leaves them stopped until you configure them. frp is then updated from the Updates page.
Yes. The panel detects frps and frpc containers through the Docker socket and can start, stop and restart them, read their logs and list their ports.
A new install only listens on 127.0.0.1. Use an SSH tunnel, a local reverse proxy (nginx, Caddy), or set the listening address to 0.0.0.0 in Settings and filter access by IP.
Run python3 app.py --reset-password in the install directory (or through docker exec), then restart the panel.
English and French, messages from the server included. The panel follows your browser's language; you can change it in Settings, Preferences.
Open the demo, or install it on the machine that runs frp.