Packages / frp

APT repository · deb.freshdeb.com/frpprinted 28 Oct 2026, 07:19 UTC

frp

frp, a fast reverse proxy. frps runs on a server with a public address, frpc next to the services behind a NAT or firewall, and frpc forwards TCP, UDP, HTTP and HTTPS to them through frps. Built like upstream's release, with both web dashboards. One release line for Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04 on amd64 and arm64.

Componentmain

follows every upstream release, minors and majors included. Currently 0.71.1.

Release line
Deliver to
frps 0.71.1-1+freshdeb~deb13

1Trust the signing key (once per machine)

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://deb.freshdeb.com/freshdeb-archive-keyring.gpg \
  | sudo tee /etc/apt/keyrings/freshdeb-archive-keyring.gpg >/dev/null

Fingerprint 3BBD F03A 9C0B F890 F8CA 9510 7595 CC55 468F 3161. How to verify.

2Add the source

sudo tee /etc/apt/sources.list.d/freshdeb-frp.sources >/dev/null <<EOF
Types: deb
URIs: https://deb.freshdeb.com/frp
Suites: $(. /etc/os-release && echo $VERSION_CODENAME)
Components: main
Signed-By: /etc/apt/keyrings/freshdeb-archive-keyring.gpg
EOF

With auto, the shell reads the codename from /etc/os-release on the machine you paste this into.

3Install

sudo apt update && sudo apt install frps
apt policy frps   # expect 0.71.1-1+freshdeb~…

Neither Debian nor Ubuntu ship frp, so there's nothing to replace. frpc, the client, is in the same repository. Neither service is enabled on install: upstream's example frps configuration has no token, so any client could use it. Set one, check with frps verify -c /etc/frp/frps.toml, then systemctl enable --now frps.

frps 0.71.1-1+freshdeb~deb13

How it's packaged

No distribution packages frp, so the packaging is ours, written the way Debian would: Debian's paths and naming, configuration in /etc, a system user and systemd units. The build and the defaults follow upstream's.

Distributions
None ship frp: a Debian ITP from 2023 never got past a draft. The packaging is ours, in Debian's style (how it's done).
Build
Upstream's release build: CGO_ENABLED=0, -trimpath, -ldflags "-s -w", the pinned Go toolchain and vendored modules verified against go.sum. Upstream's unit tests gate the build.
Dashboards
The frps dashboard and the frpc admin UI, built from source as upstream's release workflow builds them: pinned Node, npm ci against upstream's package-lock.json. Without them upstream's Makefile builds -tags noweb.
Configuration
/etc/frp/frps.toml and /etc/frp/frpc.toml are upstream's minimal examples, readable only by root and the frp group because they hold the auth token. The full references are in /usr/share/doc/frps and /usr/share/doc/frpc.
Services
frps and frpc, and frps@<name> and frpc@<name> for /etc/frp/<name>.toml, modeled on the units upstream shipped until 2022. They run as the frp user with systemd's sandboxing; systemctl reload frpc goes through frpc's admin API.

Packing list

Every release line of frp and the distributions it's built for. Each line is its own APT component and only gets the releases it follows (main: every upstream release, minors and majors included). After upstream end of life it stops building but stays installable. Hatched cells have no build: usually that distribution already ships the same or a newer version itself.

LineComponentCurrentbookwormDebian 12trixieDebian 13jammyUbuntu 22.04nobleUbuntu 24.04resoluteUbuntu 26.04Support
main main 0.71.1 built: 0.71.1-1built: 0.71.1-1built: 0.71.1-1built: 0.71.1-1built: 0.71.1-1 –

Versions follow <upstream>-<revision>+freshdeb~<distro>, distro being deb12, deb13, ubuntu22.04, ubuntu24.04 or ubuntu26.04, for amd64 and arm64. Published versions are never rebuilt or replaced.

Contents

frps
The server, with its web dashboard.
frpc
The client, with its admin UI.

Origin

Upstream
github.com/fatedier/frprelease tags pinned to commit hashes
Packaging
our own, in Debian's styleno distribution packages frp
Built for
bookworm, trixie, jammy, noble, resoluteamd64, arm64, built natively

Also in Networking

Maintained by Blendbyte

Blendbyte builds cloud infrastructure, web apps, and developer tools. We've been shipping software to production for 20+ years.

These packages run in our own stack, which is why we keep them maintained. Issues and PRs get read. Good ones get merged.

Also from Blendbytenginx-modules.com: pre-built nginx dynamic modules (Brotli, GeoIP2, ModSecurity and more) for nginx.org's nginx, on the same Debian and Ubuntu releases.