github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 16:15:49 -06:00

[GH-ISSUE #4866] 穿透后速度很慢 #3836

New issue

Closed

opened 2026-05-05 14:27:10 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 14:27:10 -06:00

Owner

Originally created by @xiaowen-king on GitHub (Jul 3, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4866

Bug Description

#描述#

云服务器是阿里云香港的200M带宽的，家里面的贷款是300M，用测试软件测试上传带宽有30-40M，但是穿透出来的下载速度只有300KB/S左右，算下来就是2.4M左右的带宽，不知道是什么原因，有么有排查方法呢

#其他#

大佬帮我看一下是不是配置错误了还是什么，或者是有没有办法排查是哪里出了问题，阿里云的服务器为了方便配置反向代理，安装了宝塔面板，然后安装了nginx。

frpc Version

0.63.0

frps Version

0.63.0

System Architecture

X86

Configurations

#FRPS配置文件（frps.toml）#

# 服务端监听地址，"0.0.0.0" 表示监听所有网络接口，允许任何 IP 连接
# 作用：定义 frps 接受 frpc 连接的地址
bindAddr = "0.0.0.0"

# 服务端主监听端口（TCP），用于 frpc 的控制连接
# 作用：客户端通过此端口连接 frps，确保防火墙开放此端口
bindPort = 5443

# KCP 协议的 UDP 端口，用于优化高延迟或丢包网络的连接
# 作用：启用 KCP 协议，适合弱网环境，提高传输效率
kcpBindPort = 5444

# 心跳超时时间（秒），检测 frpc 是否在线
# 作用：默认 90 秒，负值禁用心跳，建议保留默认值
transport.heartbeatTimeout = 90

# 每个代理的最大连接池大小，限制并发连接数
# 作用：防止单一代理占用过多资源，增强稳定性
transport.maxPoolCount = 50

# 启用 TCP 多路复用，允许多个代理请求复用单一 TCP 连接
# 作用：减少连接开销，提高效率
transport.tcpMux = true

# TCP 多路复用的保活间隔（秒）
# 作用：确保复用连接的活跃性
transport.tcpMuxKeepaliveInterval = 30

# TCP 连接的保活探测间隔（秒），负值禁用
# 作用：维持长期连接，防止空闲断开
transport.tcpKeepalive = 7200

# 强制要求 TLS 加密连接
# 作用：增强安全性，需配置证书
transport.tls.force = true

# TLS 证书和私钥文件路径
# 作用：为 QUIC 和 TLS 加密提供证书
transport.tls.certFile = "/root/ssl/frps/server.crt"
transport.tls.keyFile = "/root/ssl/frps/server.key"
transport.tls.trustedCaFile = "/root/ssl/frps/ca.crt"

# HTTP 虚拟主机监听端口
# 作用：处理 HTTP 代理请求，支持子域名路由
vhostHTTPPort = 2049

# HTTPS 虚拟主机监听端口
# 作用：处理 HTTPS 代理请求，需本地服务支持 HTTPS
vhostHTTPSPort = 2050

# HTTP 响应超时时间（秒）
# 作用：限制等待后端服务响应的时间
vhostHTTPTimeout = 60

# Web 仪表盘配置
# 监听地址，仅允许本地访问以提高安全性
webServer.addr = "0.0.0.0"
# 仪表盘端口，访问 frps 管理界面
webServer.port = ****
# 仪表盘用户名和密码
webServer.user = "*******"
webServer.password = "**********"
# 仪表盘 TLS 证书（可选）
webServer.tls.certFile = "/root/ssl/frps/server.crt"
webServer.tls.keyFile = "/root/ssl/frps/server.key"

# 启用 Prometheus 监控，导出指标到 /metrics 接口
# 作用：便于监控 frps 运行状态
enablePrometheus = true

# 日志输出路径，记录到文件便于排查问题
# 作用：保存 frps 运行日志
log.to = "./frps.log"
# 日志级别，debug 提供详细日志
log.level = "debug"
# 日志保留天数
log.maxDays = 15
# 禁用控制台日志颜色
log.disablePrintColor = false

# 是否向 frpc 返回详细错误信息
# 作用：便于调试，但生产环境可关闭以减少敏感信息泄露
detailedErrorsToClient = true 

# 认证方式，使用令牌认证
# 作用：确保只有授权的 frpc 可以连接
auth.method = "token"
# 认证令牌，与客户端保持一致
auth.token = "************"

# 允许的端口范围，限制 frpc 可绑定的端口
# 作用：增强安全性，防止端口滥用
allowPorts = []

# 每个客户端的最大端口数，0 表示无限制
# 作用：限制资源占用
maxPortsPerClient = 10

# 子域名主机，用于 HTTP/HTTPS 代理的域名路由
# 作用：支持如 www.ersansi.top 的子域名访问
subDomainHost = "47.239.226.246"

# 自定义 404 页面路径
# 作用：HTTP 请求未找到服务时返回自定义页面
custom404Page = "/usr/local/frps/frp_erro.html"

# UDP 数据包大小（字节），客户端和服务端需一致
# 作用：优化 UDP 和 XTCP 代理性能
udpPacketSize = 1400

# NAT 打洞数据保留时间（小时）
# 作用：支持 XTCP（P2P）模式，减少服务端带宽压力
natholeAnalysisDataReserveHours = 168

#FRPC配置文件（frpc.toml）#

# 服务端地址，与 frps.toml 的 bindAddr 匹配
# 作用：指定 frps 的公网 IP
serverAddr = "47.239.226.246"

#选择与frps的连接协议
transport.protocol = "kcp"

# 服务端端口，使用 KCP 协议的端口，与 frps.toml 的 kcpBindPort 匹配
serverPort = 5444

# 客户端标识，用于区分多个客户端
# 作用：在 frps 仪表盘中显示客户端名称
user = "MP73"

# 认证方式，与 frps.toml 的 auth.method 匹配
# 作用：使用令牌认证确保安全性
auth.method = "token"
auth.token = "****************"

# 启用 TLS 加密，与 frps.toml 的 transport.tls.force = true 匹配
# 作用：增强数据安全，规避运营商限速
transport.tls.enable = true

transport.tls.certFile = "/root/ssl/frpc/client.crt"
transport.tls.keyFile = "/root/ssl/frpc/client.key"
transport.tls.trustedCaFile = "/root/ssl/frpc/ca.crt"
transport.tls.serverName = "47.***.***.***"

# UDP 数据包大小（字节），与 frps.toml 的 udpPacketSize 一致
# 作用：优化 UDP 和 XTCP 代理性能，避免分片
udpPacketSize = 1400

# 日志输出路径，便于调试
# 作用：记录 frpc 运行日志，排查网速或连接问题
log.to = "./frpc.log"
log.level = "debug"
log.maxDays = 3

# HTTP 代理：Web 服务
[[proxies]]
name = "贰叁肆"
type = "http"
localIP = "127.0.0.1"
localPort = 80
customDomains = ["www.ersansi.top"]
transport.proxyProtocolVersion = "v2"
# 启用加密和压缩，提高安全性并减少带宽占用
transport.useEncryption = true
transport.useCompression = true

# TCP 代理：饥荒控制面板
[[proxies]]
name = "饥荒控制面板"
type = "tcp"
localIP = "127.0.0.1"
localPort = 8082
remotePort = 8082
transport.proxyProtocolVersion = "v2"
# 启用加密，增强安全性
transport.useEncryption = true

[[proxies]]
name = "饥荒游戏端口1"
type = "udp"
localIP = "127.0.0.1"
localPort = 10998
remotePort = 10998

[[proxies]]
name = "饥荒游戏端口2"
type = "udp"
localIP = "127.0.0.1"
localPort = 10999
remotePort = 10999

# HTTP 代理：文件共享
[[proxies]]
name = "文件共享"
type = "http"
localIP = "127.0.0.1"
localPort = 5000
customDomains = ["file.ersansi.top"]
transport.useEncryption = true
transport.useCompression = true

# HTTP 代理：One-KVM
[[proxies]]
name = "One-KVM"
type = "http"
localIP = "192.168.99.3"
localPort = 80
customDomains = ["kvm.ersansi.top"]
transport.useEncryption = true
transport.useCompression = true

# TCP 代理：One-KVM HTTPS
[[proxies]]
name = "One-KVM(443)"
type = "tcp"
localIP = "192.168.99.3"
localPort = 443
remotePort = 2052
transport.useEncryption = true

Logs

#FRPS日志（frps.log）#

2025-07-03 14:48:32.172 [I] [frps/root.go:105] frps uses config file: frps.toml
2025-07-03 14:48:32.197 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:5443
2025-07-03 14:48:32.198 [I] [server/service.go:246] frps kcp listen on udp 0.0.0.0:5444
2025-07-03 14:48:32.198 [I] [server/service.go:305] http service listen on 0.0.0.0:2049
2025-07-03 14:48:32.198 [I] [server/service.go:319] https service listen on 0.0.0.0:2050
2025-07-03 14:48:32.198 [I] [frps/root.go:114] frps started successfully
2025-07-03 14:48:32.198 [I] [server/service.go:351] dashboard listen on 0.0.0.0:2051
2025-07-03 14:48:40.396 [I] [server/dashboard_api.go:107] http request: [/api/serverinfo]
2025-07-03 14:48:40.396 [I] [server/dashboard_api.go:100] http response [/api/serverinfo]: code [200]
2025-07-03 14:48:44.898 [I] [server/dashboard_api.go:227] http request: [/api/proxy/tcp]
2025-07-03 14:48:44.898 [I] [server/dashboard_api.go:221] http response [/api/proxy/tcp]: code [200]
2025-07-03 14:48:46.356 [I] [server/dashboard_api.go:227] http request: [/api/proxy/udp]
2025-07-03 14:48:46.356 [I] [server/dashboard_api.go:221] http response [/api/proxy/udp]: code [200]
2025-07-03 14:48:46.933 [I] [server/dashboard_api.go:107] http request: [/api/serverinfo]
2025-07-03 14:48:46.933 [I] [server/dashboard_api.go:100] http response [/api/serverinfo]: code [200]
2025-07-03 14:48:47.307 [I] [server/dashboard_api.go:227] http request: [/api/proxy/http]
2025-07-03 14:48:47.307 [I] [server/dashboard_api.go:221] http response [/api/proxy/http]: code [200]

#FRPC日志（一部分）#

2025-07-03 22:06:53.142 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口2] start a new work connection, localAddr: 0.0.0.0:39643 remoteAddr: 47.239.226.246:5444
2025-07-03 22:06:53.142 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口2] incoming a new work connection for udp proxy, 47.239.226.246:5444
2025-07-03 22:06:53.244 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口1] start a new work connection, localAddr: 0.0.0.0:39643 remoteAddr: 47.239.226.246:5444
2025-07-03 22:06:53.244 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口1] incoming a new work connection for udp proxy, 47.239.226.246:5444
2025-07-03 22:08:22.595 [W] [proxy/udp.go:128] [d7034590f33ab132] [MP73.饥荒游戏端口1] read from workConn for udp error: EOF
2025-07-03 22:08:22.595 [W] [proxy/udp.go:128] [d7034590f33ab132] [MP73.饥荒游戏端口2] read from workConn for udp error: EOF
2025-07-03 22:08:22.595 [I] [proxy/udp.go:142] [d7034590f33ab132] [MP73.饥荒游戏端口2] writer goroutine for udp work connection closed
2025-07-03 22:08:22.595 [I] [proxy/udp.go:142] [d7034590f33ab132] [MP73.饥荒游戏端口1] writer goroutine for udp work connection closed
2025-07-03 22:08:22.812 [I] [client/service.go:314] [d7034590f33ab132] try to connect to server...
2025-07-03 22:08:23.054 [I] [client/service.go:306] [d7034590f33ab132] login to server success, get run id [d7034590f33ab132]
2025-07-03 22:08:23.054 [I] [proxy/proxy_manager.go:177] [d7034590f33ab132] proxy added: [MP73.贰叁肆 MP73.饥荒控制面板 MP73.饥荒游戏端口1 MP73.饥荒游戏端口2 MP73.文件共享 MP73.One-KVM MP73.One-KVM(443)]
2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.饥荒游戏端口1] start proxy success
2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.贰叁肆] start proxy success
2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.饥荒控制面板] start proxy success
2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.文件共享] start proxy success
2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.One-KVM(443)] start proxy success
2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.饥荒游戏端口2] start proxy success
2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.One-KVM] start proxy success
2025-07-03 22:08:23.669 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口1] start a new work connection, localAddr: 0.0.0.0:49352 remoteAddr: 47.239.226.246:5444
2025-07-03 22:08:23.669 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口1] incoming a new work connection for udp proxy, 47.239.226.246:5444
2025-07-03 22:08:23.792 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口2] start a new work connection, localAddr: 0.0.0.0:49352 remoteAddr: 47.239.226.246:5444
2025-07-03 22:08:23.792 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口2] incoming a new work connection for udp proxy, 47.239.226.246:5444
2025-07-03 22:09:24.876 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.贰叁肆] start a new work connection, localAddr: 0.0.0.0:49352 remoteAddr: 47.239.226.246:5444
2025-07-03 22:09:24.877 [D] [proxy/proxy.go:203] [d7034590f33ab132] [MP73.贰叁肆] join connections, localConn(l[127.0.0.1:37272] r[127.0.0.1:80]) workConn(l[0.0.0.0:49352] r[47.239.226.246:5444])

Steps to reproduce

穿透后使用宝塔的nginx进行反向代理，从而达到不带端口访问的目的，再次访问速度很慢

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @xiaowen-king on GitHub (Jul 3, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4866 ### Bug Description #描述# 云服务器是阿里云香港的200M带宽的，家里面的贷款是300M，用测试软件测试上传带宽有30-40M，但是穿透出来的下载速度只有300KB/S左右，算下来就是2.4M左右的带宽，不知道是什么原因，有么有排查方法呢 #其他# 大佬帮我看一下是不是配置错误了还是什么，或者是有没有办法排查是哪里出了问题，阿里云的服务器为了方便配置反向代理，安装了宝塔面板，然后安装了nginx。 ### frpc Version 0.63.0 ### frps Version 0.63.0 ### System Architecture X86 ### Configurations #FRPS配置文件（frps.toml）# ``` # 服务端监听地址，"0.0.0.0" 表示监听所有网络接口，允许任何 IP 连接 # 作用：定义 frps 接受 frpc 连接的地址 bindAddr = "0.0.0.0" # 服务端主监听端口（TCP），用于 frpc 的控制连接 # 作用：客户端通过此端口连接 frps，确保防火墙开放此端口 bindPort = 5443 # KCP 协议的 UDP 端口，用于优化高延迟或丢包网络的连接 # 作用：启用 KCP 协议，适合弱网环境，提高传输效率 kcpBindPort = 5444 # 心跳超时时间（秒），检测 frpc 是否在线 # 作用：默认 90 秒，负值禁用心跳，建议保留默认值 transport.heartbeatTimeout = 90 # 每个代理的最大连接池大小，限制并发连接数 # 作用：防止单一代理占用过多资源，增强稳定性 transport.maxPoolCount = 50 # 启用 TCP 多路复用，允许多个代理请求复用单一 TCP 连接 # 作用：减少连接开销，提高效率 transport.tcpMux = true # TCP 多路复用的保活间隔（秒） # 作用：确保复用连接的活跃性 transport.tcpMuxKeepaliveInterval = 30 # TCP 连接的保活探测间隔（秒），负值禁用 # 作用：维持长期连接，防止空闲断开 transport.tcpKeepalive = 7200 # 强制要求 TLS 加密连接 # 作用：增强安全性，需配置证书 transport.tls.force = true # TLS 证书和私钥文件路径 # 作用：为 QUIC 和 TLS 加密提供证书 transport.tls.certFile = "/root/ssl/frps/server.crt" transport.tls.keyFile = "/root/ssl/frps/server.key" transport.tls.trustedCaFile = "/root/ssl/frps/ca.crt" # HTTP 虚拟主机监听端口 # 作用：处理 HTTP 代理请求，支持子域名路由 vhostHTTPPort = 2049 # HTTPS 虚拟主机监听端口 # 作用：处理 HTTPS 代理请求，需本地服务支持 HTTPS vhostHTTPSPort = 2050 # HTTP 响应超时时间（秒） # 作用：限制等待后端服务响应的时间 vhostHTTPTimeout = 60 # Web 仪表盘配置 # 监听地址，仅允许本地访问以提高安全性 webServer.addr = "0.0.0.0" # 仪表盘端口，访问 frps 管理界面 webServer.port = **** # 仪表盘用户名和密码 webServer.user = "*******" webServer.password = "**********" # 仪表盘 TLS 证书（可选） webServer.tls.certFile = "/root/ssl/frps/server.crt" webServer.tls.keyFile = "/root/ssl/frps/server.key" # 启用 Prometheus 监控，导出指标到 /metrics 接口 # 作用：便于监控 frps 运行状态 enablePrometheus = true # 日志输出路径，记录到文件便于排查问题 # 作用：保存 frps 运行日志 log.to = "./frps.log" # 日志级别，debug 提供详细日志 log.level = "debug" # 日志保留天数 log.maxDays = 15 # 禁用控制台日志颜色 log.disablePrintColor = false # 是否向 frpc 返回详细错误信息 # 作用：便于调试，但生产环境可关闭以减少敏感信息泄露 detailedErrorsToClient = true # 认证方式，使用令牌认证 # 作用：确保只有授权的 frpc 可以连接 auth.method = "token" # 认证令牌，与客户端保持一致 auth.token = "************" # 允许的端口范围，限制 frpc 可绑定的端口 # 作用：增强安全性，防止端口滥用 allowPorts = [] # 每个客户端的最大端口数，0 表示无限制 # 作用：限制资源占用 maxPortsPerClient = 10 # 子域名主机，用于 HTTP/HTTPS 代理的域名路由 # 作用：支持如 www.ersansi.top 的子域名访问 subDomainHost = "47.239.226.246" # 自定义 404 页面路径 # 作用：HTTP 请求未找到服务时返回自定义页面 custom404Page = "/usr/local/frps/frp_erro.html" # UDP 数据包大小（字节），客户端和服务端需一致 # 作用：优化 UDP 和 XTCP 代理性能 udpPacketSize = 1400 # NAT 打洞数据保留时间（小时） # 作用：支持 XTCP（P2P）模式，减少服务端带宽压力 natholeAnalysisDataReserveHours = 168 ``` #FRPC配置文件（frpc.toml）# ``` # 服务端地址，与 frps.toml 的 bindAddr 匹配 # 作用：指定 frps 的公网 IP serverAddr = "47.239.226.246" #选择与frps的连接协议 transport.protocol = "kcp" # 服务端端口，使用 KCP 协议的端口，与 frps.toml 的 kcpBindPort 匹配 serverPort = 5444 # 客户端标识，用于区分多个客户端 # 作用：在 frps 仪表盘中显示客户端名称 user = "MP73" # 认证方式，与 frps.toml 的 auth.method 匹配 # 作用：使用令牌认证确保安全性 auth.method = "token" auth.token = "****************" # 启用 TLS 加密，与 frps.toml 的 transport.tls.force = true 匹配 # 作用：增强数据安全，规避运营商限速 transport.tls.enable = true transport.tls.certFile = "/root/ssl/frpc/client.crt" transport.tls.keyFile = "/root/ssl/frpc/client.key" transport.tls.trustedCaFile = "/root/ssl/frpc/ca.crt" transport.tls.serverName = "47.***.***.***" # UDP 数据包大小（字节），与 frps.toml 的 udpPacketSize 一致 # 作用：优化 UDP 和 XTCP 代理性能，避免分片 udpPacketSize = 1400 # 日志输出路径，便于调试 # 作用：记录 frpc 运行日志，排查网速或连接问题 log.to = "./frpc.log" log.level = "debug" log.maxDays = 3 # HTTP 代理：Web 服务 [[proxies]] name = "贰叁肆" type = "http" localIP = "127.0.0.1" localPort = 80 customDomains = ["www.ersansi.top"] transport.proxyProtocolVersion = "v2" # 启用加密和压缩，提高安全性并减少带宽占用 transport.useEncryption = true transport.useCompression = true # TCP 代理：饥荒控制面板 [[proxies]] name = "饥荒控制面板" type = "tcp" localIP = "127.0.0.1" localPort = 8082 remotePort = 8082 transport.proxyProtocolVersion = "v2" # 启用加密，增强安全性 transport.useEncryption = true [[proxies]] name = "饥荒游戏端口1" type = "udp" localIP = "127.0.0.1" localPort = 10998 remotePort = 10998 [[proxies]] name = "饥荒游戏端口2" type = "udp" localIP = "127.0.0.1" localPort = 10999 remotePort = 10999 # HTTP 代理：文件共享 [[proxies]] name = "文件共享" type = "http" localIP = "127.0.0.1" localPort = 5000 customDomains = ["file.ersansi.top"] transport.useEncryption = true transport.useCompression = true # HTTP 代理：One-KVM [[proxies]] name = "One-KVM" type = "http" localIP = "192.168.99.3" localPort = 80 customDomains = ["kvm.ersansi.top"] transport.useEncryption = true transport.useCompression = true # TCP 代理：One-KVM HTTPS [[proxies]] name = "One-KVM(443)" type = "tcp" localIP = "192.168.99.3" localPort = 443 remotePort = 2052 transport.useEncryption = true ``` ### Logs #FRPS日志（frps.log）# ``` 2025-07-03 14:48:32.172 [I] [frps/root.go:105] frps uses config file: frps.toml 2025-07-03 14:48:32.197 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:5443 2025-07-03 14:48:32.198 [I] [server/service.go:246] frps kcp listen on udp 0.0.0.0:5444 2025-07-03 14:48:32.198 [I] [server/service.go:305] http service listen on 0.0.0.0:2049 2025-07-03 14:48:32.198 [I] [server/service.go:319] https service listen on 0.0.0.0:2050 2025-07-03 14:48:32.198 [I] [frps/root.go:114] frps started successfully 2025-07-03 14:48:32.198 [I] [server/service.go:351] dashboard listen on 0.0.0.0:2051 2025-07-03 14:48:40.396 [I] [server/dashboard_api.go:107] http request: [/api/serverinfo] 2025-07-03 14:48:40.396 [I] [server/dashboard_api.go:100] http response [/api/serverinfo]: code [200] 2025-07-03 14:48:44.898 [I] [server/dashboard_api.go:227] http request: [/api/proxy/tcp] 2025-07-03 14:48:44.898 [I] [server/dashboard_api.go:221] http response [/api/proxy/tcp]: code [200] 2025-07-03 14:48:46.356 [I] [server/dashboard_api.go:227] http request: [/api/proxy/udp] 2025-07-03 14:48:46.356 [I] [server/dashboard_api.go:221] http response [/api/proxy/udp]: code [200] 2025-07-03 14:48:46.933 [I] [server/dashboard_api.go:107] http request: [/api/serverinfo] 2025-07-03 14:48:46.933 [I] [server/dashboard_api.go:100] http response [/api/serverinfo]: code [200] 2025-07-03 14:48:47.307 [I] [server/dashboard_api.go:227] http request: [/api/proxy/http] 2025-07-03 14:48:47.307 [I] [server/dashboard_api.go:221] http response [/api/proxy/http]: code [200] ``` #FRPC日志（一部分）# ``` 2025-07-03 22:06:53.142 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口2] start a new work connection, localAddr: 0.0.0.0:39643 remoteAddr: 47.239.226.246:5444 2025-07-03 22:06:53.142 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口2] incoming a new work connection for udp proxy, 47.239.226.246:5444 2025-07-03 22:06:53.244 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口1] start a new work connection, localAddr: 0.0.0.0:39643 remoteAddr: 47.239.226.246:5444 2025-07-03 22:06:53.244 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口1] incoming a new work connection for udp proxy, 47.239.226.246:5444 2025-07-03 22:08:22.595 [W] [proxy/udp.go:128] [d7034590f33ab132] [MP73.饥荒游戏端口1] read from workConn for udp error: EOF 2025-07-03 22:08:22.595 [W] [proxy/udp.go:128] [d7034590f33ab132] [MP73.饥荒游戏端口2] read from workConn for udp error: EOF 2025-07-03 22:08:22.595 [I] [proxy/udp.go:142] [d7034590f33ab132] [MP73.饥荒游戏端口2] writer goroutine for udp work connection closed 2025-07-03 22:08:22.595 [I] [proxy/udp.go:142] [d7034590f33ab132] [MP73.饥荒游戏端口1] writer goroutine for udp work connection closed 2025-07-03 22:08:22.812 [I] [client/service.go:314] [d7034590f33ab132] try to connect to server... 2025-07-03 22:08:23.054 [I] [client/service.go:306] [d7034590f33ab132] login to server success, get run id [d7034590f33ab132] 2025-07-03 22:08:23.054 [I] [proxy/proxy_manager.go:177] [d7034590f33ab132] proxy added: [MP73.贰叁肆 MP73.饥荒控制面板 MP73.饥荒游戏端口1 MP73.饥荒游戏端口2 MP73.文件共享 MP73.One-KVM MP73.One-KVM(443)] 2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.饥荒游戏端口1] start proxy success 2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.贰叁肆] start proxy success 2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.饥荒控制面板] start proxy success 2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.文件共享] start proxy success 2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.One-KVM(443)] start proxy success 2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.饥荒游戏端口2] start proxy success 2025-07-03 22:08:23.159 [I] [client/control.go:172] [d7034590f33ab132] [MP73.One-KVM] start proxy success 2025-07-03 22:08:23.669 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口1] start a new work connection, localAddr: 0.0.0.0:49352 remoteAddr: 47.239.226.246:5444 2025-07-03 22:08:23.669 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口1] incoming a new work connection for udp proxy, 47.239.226.246:5444 2025-07-03 22:08:23.792 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.饥荒游戏端口2] start a new work connection, localAddr: 0.0.0.0:49352 remoteAddr: 47.239.226.246:5444 2025-07-03 22:08:23.792 [I] [proxy/udp.go:93] [d7034590f33ab132] [MP73.饥荒游戏端口2] incoming a new work connection for udp proxy, 47.239.226.246:5444 2025-07-03 22:09:24.876 [D] [proxy/proxy_wrapper.go:265] [d7034590f33ab132] [MP73.贰叁肆] start a new work connection, localAddr: 0.0.0.0:49352 remoteAddr: 47.239.226.246:5444 2025-07-03 22:09:24.877 [D] [proxy/proxy.go:203] [d7034590f33ab132] [MP73.贰叁肆] join connections, localConn(l[127.0.0.1:37272] r[127.0.0.1:80]) workConn(l[0.0.0.0:49352] r[47.239.226.246:5444]) ``` ### Steps to reproduce 穿透后使用宝塔的nginx进行反向代理，从而达到不带端口访问的目的，再次访问速度很慢 ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [x] Others

gitea-mirror

2026-05-05 14:27:10 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:27:13 -06:00

Author

Owner

@happytrudy commented on GitHub (Jul 14, 2025):

换个协议试试 quic kcp

@happytrudy commented on GitHub (Jul 14, 2025): 换个协议试试 quic kcp

gitea-mirror commented

2026-05-05 14:27:15 -06:00

Author

Owner

@xiaowen-king commented on GitHub (Jul 14, 2025):

换个协议试试 quic kcp

试过了，后面发现是运营商的问题，使用tcp协议套个隧道解决了

@xiaowen-king commented on GitHub (Jul 14, 2025): > 换个协议试试 quic kcp 试过了，后面发现是运营商的问题，使用tcp协议套个隧道解决了

gitea-mirror commented

2026-05-05 14:27:16 -06:00

Author

Owner

@datahuo commented on GitHub (Jul 20, 2025):

换个协议试试 quic kcp

试过了，后面发现是运营商的问题，使用tcp协议套个隧道解决了

大佬，怎么操作的？求配置，我被运营商限速了，千兆只有百兆效果

@datahuo commented on GitHub (Jul 20, 2025): > > 换个协议试试 quic kcp > > 试过了，后面发现是运营商的问题，使用tcp协议套个隧道解决了大佬，怎么操作的？求配置，我被运营商限速了，千兆只有百兆效果

gitea-mirror commented

2026-05-05 14:27:16 -06:00

Author

Owner

@xiaowen-king commented on GitHub (Jul 21, 2025):

换个协议试试 quic kcp

试过了，后面发现是运营商的问题，使用tcp协议套个隧道解决了

大佬，怎么操作的？求配置，我被运营商限速了，千兆只有百兆效果

这个要你先确定上传带宽是多少，你千兆的家庭带宽这个只是下载速度

服务端不用改，客户端加transport.proxyURL = "socks5://user:passwd@192.168.1.128:1080"

等号后面的“”里面填写隧道的代理地址

隧道需要自己搭建，隧道搭建方法可以谷歌一下

或者是你先换QUIC协议连接试试看，端口号换高一点的

@xiaowen-king commented on GitHub (Jul 21, 2025): > > > 换个协议试试 quic kcp > > > > > > 试过了，后面发现是运营商的问题，使用tcp协议套个隧道解决了 > > 大佬，怎么操作的？求配置，我被运营商限速了，千兆只有百兆效果这个要你先确定上传带宽是多少，你千兆的家庭带宽这个只是下载速度服务端不用改，客户端加transport.proxyURL = "socks5://user:passwd@192.168.1.128:1080" 等号后面的“”里面填写隧道的代理地址隧道需要自己搭建，隧道搭建方法可以谷歌一下或者是你先换QUIC协议连接试试看，端口号换高一点的

gitea-mirror commented

2026-05-05 14:27:17 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 5, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Aug 5, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:27:18 -06:00

Author

Owner

@Kiswelrg commented on GitHub (Sep 10, 2025):

有办法吗这个速度问题，直接一个tcp type的代理，速度明显慢的很，千兆网大概300-600k的速度， quic测了也不work, still the same speed

@Kiswelrg commented on GitHub (Sep 10, 2025): 有办法吗这个速度问题，直接一个tcp type的代理，速度明显慢的很，千兆网大概300-600k的速度， quic测了也不work, still the same speed

gitea-mirror commented

2026-05-05 14:27:18 -06:00

Author

Owner

@xiaowen-king commented on GitHub (Sep 12, 2025):

按照国家贵定，上传和下载的速度比例是1:5，也就是你的宽带1000M/bps的上传速度应该是200M/bps，200÷8=25，也就是你在外面下载frp穿透的东西最高应该可以到25M才对，这个是忽略你公网服务器带宽的理论值，如果你公网服务器的带宽不到200M/bps的话也是达不到的，公网服务器的带宽也会限制的，虽然不知道你公网服务器的带宽是多少，但是如果速度没有达到公网服务器带宽的瓶颈或者是家庭网络上传带宽的瓶颈的话可以用下面这个方法试一下

https://www.ersansi.top/index.php/archives/2138/

使用hystera端口跳跃试试看

我现在使用的就是这个方法，上面是我博文地址，但是我这边网络运营商有问题，网络拥堵，所以访问我的博文估计会很慢

Yu Mei @.***> 于2025年9月10日周三 16:05写道：

Kiswelrg left a comment (fatedier/frp#4866)
https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898

有办法吗这个速度问题，直接一个tcp type的代理，速度明显慢的很，千兆网大概300-600k的速度

—
Reply to this email directly, view it on GitHub
https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AO4ZPHEMCJMSSGPWVMUWN533R7LU5AVCNFSM6AAAAACAW67SQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZTHAYDIOBZHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@xiaowen-king commented on GitHub (Sep 12, 2025): 按照国家贵定，上传和下载的速度比例是1:5，也就是你的宽带1000M/bps的上传速度应该是200M/bps，200÷8=25，也就是你在外面下载frp穿透的东西最高应该可以到25M才对，这个是忽略你公网服务器带宽的理论值，如果你公网服务器的带宽不到200M/bps的话也是达不到的，公网服务器的带宽也会限制的，虽然不知道你公网服务器的带宽是多少，但是如果速度没有达到公网服务器带宽的瓶颈或者是家庭网络上传带宽的瓶颈的话可以用下面这个方法试一下 https://www.ersansi.top/index.php/archives/2138/ 使用hystera端口跳跃试试看我现在使用的就是这个方法，上面是我博文地址，但是我这边网络运营商有问题，网络拥堵，所以访问我的博文估计会很慢 Yu Mei ***@***.***> 于2025年9月10日周三 16:05写道： > *Kiswelrg* left a comment (fatedier/frp#4866) > <https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898> > > 有办法吗这个速度问题，直接一个tcp type的代理，速度明显慢的很，千兆网大概300-600k的速度 > > — > Reply to this email directly, view it on GitHub > <https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AO4ZPHEMCJMSSGPWVMUWN533R7LU5AVCNFSM6AAAAACAW67SQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZTHAYDIOBZHA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

gitea-mirror commented

2026-05-05 14:27:18 -06:00

Author

Owner

@xiaowen-king commented on GitHub (Sep 12, 2025):

小区应为电力施工，现在停电了，我的博文访问不了了

空白 @.***> 于2025年9月12日周五 09:12写道：

按照国家贵定，上传和下载的速度比例是1:5，也就是你的宽带1000M/bps的上传速度应该是200M/bps，200÷8=25，也就是你在外面下载frp穿透的东西最高应该可以到25M才对，这个是忽略你公网服务器带宽的理论值，如果你公网服务器的带宽不到200M/bps的话也是达不到的，公网服务器的带宽也会限制的，虽然不知道你公网服务器的带宽是多少，但是如果速度没有达到公网服务器带宽的瓶颈或者是家庭网络上传带宽的瓶颈的话可以用下面这个方法试一下

https://www.ersansi.top/index.php/archives/2138/

使用hystera端口跳跃试试看

我现在使用的就是这个方法，上面是我博文地址，但是我这边网络运营商有问题，网络拥堵，所以访问我的博文估计会很慢

Yu Mei @.***> 于2025年9月10日周三 16:05写道：

Kiswelrg left a comment (fatedier/frp#4866)
https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898

有办法吗这个速度问题，直接一个tcp type的代理，速度明显慢的很，千兆网大概300-600k的速度

—
Reply to this email directly, view it on GitHub
https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO4ZPHEMCJMSSGPWVMUWN533R7LU5AVCNFSM6AAAAACAW67SQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZTHAYDIOBZHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@xiaowen-king commented on GitHub (Sep 12, 2025): 小区应为电力施工，现在停电了，我的博文访问不了了空白 ***@***.***> 于2025年9月12日周五 09:12写道： > > 按照国家贵定，上传和下载的速度比例是1:5，也就是你的宽带1000M/bps的上传速度应该是200M/bps，200÷8=25，也就是你在外面下载frp穿透的东西最高应该可以到25M才对，这个是忽略你公网服务器带宽的理论值，如果你公网服务器的带宽不到200M/bps的话也是达不到的，公网服务器的带宽也会限制的，虽然不知道你公网服务器的带宽是多少，但是如果速度没有达到公网服务器带宽的瓶颈或者是家庭网络上传带宽的瓶颈的话可以用下面这个方法试一下 > > https://www.ersansi.top/index.php/archives/2138/ > > 使用hystera端口跳跃试试看 > > 我现在使用的就是这个方法，上面是我博文地址，但是我这边网络运营商有问题，网络拥堵，所以访问我的博文估计会很慢 > > Yu Mei ***@***.***> 于2025年9月10日周三 16:05写道： > >> *Kiswelrg* left a comment (fatedier/frp#4866) >> <https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898> >> >> 有办法吗这个速度问题，直接一个tcp type的代理，速度明显慢的很，千兆网大概300-600k的速度 >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/fatedier/frp/issues/4866#issuecomment-3273804898>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AO4ZPHEMCJMSSGPWVMUWN533R7LU5AVCNFSM6AAAAACAW67SQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZTHAYDIOBZHA> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

gitea-mirror commented

2026-05-05 14:27:19 -06:00

Author

Owner

@Kiswelrg commented on GitHub (Sep 12, 2025):

小区应为电力施工，现在停电了，我的博文访问不了了

空白 @.***> 于2025年9月12日周五 09:12写道：
…

haha thanks for replying, i tried nps, it have the normal speed, which is dozens of MB/s, and that's definately not a bandwidth problem. but FPP > NPS, don wanna use nps.
and i'm sure it's the macos darwin version frpc problem, i tested the exact frpc.toml on macos and ubuntu, the ubuntu one have the proper speed while macos frpc only gives like 300k.
In a word:

macos: frpc, darwin, 0.64.0/0.61.2, tcp or http or quic, 300k
macos: nps, 30m
ubuntu: frpc, linux amd64, 30m

@Kiswelrg commented on GitHub (Sep 12, 2025): > 小区应为电力施工，现在停电了，我的博文访问不了了 > > 空白 ***@***.***> 于2025年9月12日周五 09:12写道： > […](#) haha thanks for replying, i tried nps, it have the normal speed, which is dozens of MB/s, and that's definately not a bandwidth problem. but FPP > NPS, don wanna use nps. and i'm sure it's the macos darwin version frpc problem, i tested the exact frpc.toml on macos and ubuntu, the ubuntu one have the proper speed while macos frpc only gives like 300k. In a word: 1. macos: frpc, darwin, 0.64.0/0.61.2, tcp or http or quic, 300k 2. macos: nps, 30m 3. ubuntu: frpc, linux amd64, 30m