Operations 4 min read

Mastering FRP: Fast Reverse Proxy for Secure Intranet-to-Internet Access

This guide explains what FRP (Fast Reverse Proxy) is, its core features, and provides step‑by‑step instructions for downloading, installing, configuring both server and client, and running the service to expose internal applications to the public internet.

Efficient Ops
Efficient Ops
Efficient Ops
Mastering FRP: Fast Reverse Proxy for Secure Intranet-to-Internet Access

What is FRP

FRP (Fast Reverse Proxy) is an open‑source, high‑performance reverse proxy tool focused on intranet penetration. It supports multiple protocols such as TCP, UDP, HTTP, HTTPS and offers P2P communication, allowing you to securely expose internal services to the public network via a server with a public IP.

Core Features

Multiple protocol support : TCP, QUIC, WebSocket, etc.

TCP connection multiplexing : Multiple requests share a single connection, reducing latency.

Load balancing between proxy groups

Port reuse : Multiple services can share the same server port.

P2P communication : Traffic can bypass the server, fully utilizing bandwidth.

Installation and Deployment

You can download the latest client and server binaries from the GitHub release page.

Extract the archive: tar -zxvf frp_0.36.2_linux_amd64.tar.gz Copy frpc to the machine inside the LAN and frps to the machine with a public IP.

Server configuration (frps.toml)

[common]
bind_port = 7000
# frp visual dashboard port
dashboard_port = 7500
dashboard_user = <em>login_username</em>
dashboard_pwd = <em>login_password</em>
vhost_http_port = 8088

Client configuration (frpc.toml)

[common]
server_addr = 101.x.x.x
server_port = 7000

[web]
type = http
local_port = 8088
custom_domains = 101.x.x.x

Start the server: ./frps -c ./frps.toml Start the client: ./frpc -c ./frpc.toml For long‑running background execution, consider using systemd, supervisor, or similar tools.

Summary

FRP offers powerful capabilities far beyond the basic features described here, including advanced use cases such as exposing RDP (3389) for remote desktop. Explore the official repository and documentation for deeper insights.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

DevOpsreverse proxyServer Configurationfrpnetwork tunneling
Efficient Ops
Written by

Efficient Ops

This public account is maintained by Xiaotianguo and friends, regularly publishing widely-read original technical articles. We focus on operations transformation and accompany you throughout your operations career, growing together happily.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.