Proxy Configuration

Detailed configuration description for frp proxies.

ProxyBaseConfig

FieldTypeDescriptionRequired
namestringProxy name.Yes
typestringProxy type. Options are tcp, udp, http, https, tcpmux, stcp, sudp, xtcp.Yes
enabled*boolWhether this proxy is enabled, default is true. Set to false to disable this proxy, allowing individual control over each proxy’s enabled state.No
annotationsmap[string]stringProxy annotation information that will be displayed in the server’s dashboard.No
transportProxyTransportProxy network layer configuration.No
metadatasmap[string]stringAdditional metadata that will be passed to server plugins to provide additional capabilities.No
loadBalancerLoadBalancerConfigLoad balancing configuration.No
healthCheckHealthCheckConfigHealth check configuration.No
ProxyBackendProxy backend service configuration.Yes

ProxyTransport

FieldTypeDescriptionRequired
useEncryptionboolWhether to enable encryption functionality. When enabled, communication content between this proxy and the server will be encrypted. If frpc has enabled global TLS, this parameter is not needed.No
useCompressionboolWhether to enable compression functionality. When enabled, communication content between this proxy and the server will be compressed.No
bandwidthLimitstringSet bandwidth rate limiting for a single proxy, in MB or KB units. 0 means no limit. If enabled, it will apply to the corresponding frpc by default.No
bandwidthLimitModestringRate limiting type, client-side or server-side rate limiting. Options are client and server, default is client-side rate limiting.No
proxyProtocolVersionstringVersion of proxy protocol to enable. Options are v1 and v2. If enabled, frpc will send proxy protocol after establishing connection with local service, containing original request IP address and port information.No

ProxyBackend

FieldTypeDescriptionRequired
localIPstringIP of the local service being proxied, default is 127.0.0.1.No
localPortintPort of the local service being proxied.No
pluginClientPluginOptionsClient plugin configuration. If client plugin is enabled, localIP and localPort don’t need to be configured, and traffic will be handled by the client plugin. Different plugin types correspond to different configurations, such as HTTPProxyPluginOptions.No

LoadBalancerConfig

FieldTypeDescriptionRequired
groupstringLoad balancing group name. User requests will be sent to proxies in the same group using round-robin.Yes
groupKeystringLoad balancing group key for authenticating the load balancing group. Only proxies with the same groupKey will be added to the same group.No

HealthCheckConfig

FieldTypeDescriptionRequired
typestringHealth check type. Options are tcp and http. After configuration, health check is enabled. tcp considers service healthy if connection succeeds, http requires interface to return 2xx status codes to consider service healthy.Yes
timeoutSecondsintHealth check timeout (seconds), default is 3s.No
maxFailedintConsecutive health check error count. How many consecutive check errors to consider service unhealthy, default is 1.No
intervalSecondsintHealth check interval (seconds). How often to perform health checks, default is 10s.No
pathstringHealth check HTTP interface. If health check type is http, this parameter needs to be configured to specify the path for sending http requests, such as /health.No
httpHeaders[]HTTPHeaderHealth check HTTP request headers, only effective when health check type is http.No

DomainConfig

FieldTypeDescriptionRequired
customDomains[]stringCustom domain list.No
subdomainstringSubdomain.No

TCPProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
remotePortintPort bound by the server. Traffic accessing this port on the server will be forwarded to the corresponding local service.No

UDPProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
remotePortintPort bound by the server. Traffic accessing this port on the server will be forwarded to the corresponding local service.No

HTTPProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
DomainConfigDomain configuration.Yes
locations[]stringURL routing configuration.No
httpUserstringHTTP Basic Auth username.No
httpPasswordstringHTTP Basic Auth password.No
hostHeaderRewritestringReplace Host Header.No
requestHeadersHeaderOperationsRequest Header operation configuration.No
responseHeadersHeaderOperationsResponse Header operation configuration.No
routeByHTTPUserstringRoute by HTTP Basic Auth user.No

HTTPSProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
DomainConfigDomain configuration.Yes

TCPMuxProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
DomainConfigDomain configuration.Yes
httpUserstringUsername. If this parameter is configured, correct identity information needs to be attached via Proxy-Authorization when establishing connection through HTTP CONNECT.No
httpPasswordstringPassword.No
routeByHTTPUserstringRoute by HTTP Basic Auth user.No
multiplexerstringMultiplexer type, currently only supports httpconnect.No

STCPProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
secretKeystringSecret key. The secret key between server and access side must be consistent for the access side to access the server.No
allowUsers[]stringList of visitor users allowed to access. By default, only visitors under the same user are allowed to access. Configure as * to allow any visitor to access.No

XTCPProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
secretKeystringSecret key. The secret key between server and access side must be consistent for the access side to access the server.No
allowUsers[]stringList of visitor users allowed to access. By default, only visitors under the same user are allowed to access. Configure as * to allow any visitor to access.No
natTraversalNatTraversalConfigNAT traversal configuration.No

SUDPProxyConfig

FieldTypeDescriptionRequired
ProxyBaseConfigBase configuration.Yes
secretKeystringSecret key. The secret key between server and access side must be consistent for the access side to access the server.No
allowUsers[]stringList of visitor users allowed to access. By default, only visitors under the same user are allowed to access. Configure as * to allow any visitor to access.No
Last modified January 4, 2026: add docs for v0.66 (#106) (191a9bc)