[GH-ISSUE #5181] slow Speed #4045

Closed
opened 2026-05-05 14:33:56 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @xD3adGh0stx on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5181

Bug Description

I have setup frp on my vps and unraid server.
and I have iperf installed on my win11 and unraid in a docker app. When I test the speed, I am getting around 100 Mbits (12mbps) or lower, however my speed is around 170 mbps. and the vps speed is 1gbps

I have not found a way to fix this yet; any help or ideas would be nice

frpc Version

0.67.0

frps Version

0.67.0

System Architecture

GNU/Linux 6.17.0-14-generic x86_64

Configurations

serverAddr = "hidden"
serverPort = 7000
auth.token = "frpisdebest"
loginFailExit = false

proxies
name = "ssh"
type = "tcp"
localIP = "192.168.50.89"
localPort = 22
remotePort = 5000

proxies
name = "nginx-http"
type = "tcp"
localIP = "192.168.50.89"
localPort = 80
remotePort = 80

proxies
name = "nginx-https"
type = "tcp"
localIP = "192.168.50.89"
localPort = 443
remotePort = 443

proxies
name = "iperf-test"
type = "tcp"
localIP = "127.0.0.1"
localPort = 5201
remotePort = 5201

Logs

No response

Steps to reproduce

...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @xD3adGh0stx on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5181 ### Bug Description I have setup frp on my vps and unraid server. and I have iperf installed on my win11 and unraid in a docker app. When I test the speed, I am getting around 100 Mbits (12mbps) or lower, however my speed is around 170 mbps. and the vps speed is 1gbps I have not found a way to fix this yet; any help or ideas would be nice ### frpc Version 0.67.0 ### frps Version 0.67.0 ### System Architecture GNU/Linux 6.17.0-14-generic x86_64 ### Configurations serverAddr = "hidden" serverPort = 7000 auth.token = "frpisdebest" loginFailExit = false [[proxies]] name = "ssh" type = "tcp" localIP = "192.168.50.89" localPort = 22 remotePort = 5000 [[proxies]] name = "nginx-http" type = "tcp" localIP = "192.168.50.89" localPort = 80 remotePort = 80 [[proxies]] name = "nginx-https" type = "tcp" localIP = "192.168.50.89" localPort = 443 remotePort = 443 [[proxies]] name = "iperf-test" type = "tcp" localIP = "127.0.0.1" localPort = 5201 remotePort = 5201 ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [x] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:33:56 -06:00
Author
Owner

@xD3adGh0stx commented on GitHub (Feb 17, 2026):

if i need to give more information just ask

<!-- gh-comment-id:3915396856 --> @xD3adGh0stx commented on GitHub (Feb 17, 2026): if i need to give more information just ask
Author
Owner

@xD3adGh0stx commented on GitHub (Feb 17, 2026):

./iperf3 -c hidden -p 5201
Connecting to host hidden, port 5201
[ 5] local 192.168.50.128 port 46301 connected to hidden port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.02 sec 3.12 MBytes 25.8 Mbits/sec
[ 5] 1.02-2.00 sec 3.62 MBytes 30.8 Mbits/sec
[ 5] 2.00-3.00 sec 5.62 MBytes 47.3 Mbits/sec
[ 5] 3.00-4.01 sec 8.12 MBytes 67.4 Mbits/sec
[ 5] 4.01-5.01 sec 11.5 MBytes 96.7 Mbits/sec
[ 5] 5.01-6.01 sec 11.1 MBytes 93.2 Mbits/sec
[ 5] 6.01-7.01 sec 10.6 MBytes 89.3 Mbits/sec
[ 5] 7.01-8.01 sec 12.9 MBytes 108 Mbits/sec
[ 5] 8.01-9.01 sec 10.1 MBytes 84.9 Mbits/sec
[ 5] 9.01-10.01 sec 14.0 MBytes 118 Mbits/sec


[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.01 sec 90.8 MBytes 76.1 Mbits/sec sender
[ 5] 0.00-10.07 sec 90.3 MBytes 75.2 Mbits/sec receiver

iperf Done.

<!-- gh-comment-id:3916930625 --> @xD3adGh0stx commented on GitHub (Feb 17, 2026): ./iperf3 -c ``hidden`` -p 5201 Connecting to host ``hidden``, port 5201 [ 5] local 192.168.50.128 port 46301 connected to ``hidden`` port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.02 sec 3.12 MBytes 25.8 Mbits/sec [ 5] 1.02-2.00 sec 3.62 MBytes 30.8 Mbits/sec [ 5] 2.00-3.00 sec 5.62 MBytes 47.3 Mbits/sec [ 5] 3.00-4.01 sec 8.12 MBytes 67.4 Mbits/sec [ 5] 4.01-5.01 sec 11.5 MBytes 96.7 Mbits/sec [ 5] 5.01-6.01 sec 11.1 MBytes 93.2 Mbits/sec [ 5] 6.01-7.01 sec 10.6 MBytes 89.3 Mbits/sec [ 5] 7.01-8.01 sec 12.9 MBytes 108 Mbits/sec [ 5] 8.01-9.01 sec 10.1 MBytes 84.9 Mbits/sec [ 5] 9.01-10.01 sec 14.0 MBytes 118 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 90.8 MBytes 76.1 Mbits/sec sender [ 5] 0.00-10.07 sec 90.3 MBytes 75.2 Mbits/sec receiver iperf Done.
Author
Owner

@fatedier commented on GitHub (Feb 24, 2026):

Could you please run two quick A/B tests to narrow this down?

  1. Disable TCP mux (tcpMux) on frpc (it’s on by default):
# frpc.toml
transport.tcpMux = false

Restart frpc and re-run the same iperf test. Please share before/after throughput.

  1. Try QUIC transport (optional, if tcpMux change doesn’t help):

frps.toml

bindPort = 7000
quicBindPort = 7000

frpc.toml

serverAddr = "YOUR_VPS_IP"
serverPort = 7000
transport.protocol = "quic"

Restart frps/frpc and test again.

<!-- gh-comment-id:3948575861 --> @fatedier commented on GitHub (Feb 24, 2026): Could you please run two quick A/B tests to narrow this down? 1. **Disable TCP mux (tcpMux) on frpc** (it’s on by default): ```toml # frpc.toml transport.tcpMux = false ``` Restart frpc and re-run the same iperf test. Please share before/after throughput. 2. **Try QUIC transport** (optional, if tcpMux change doesn’t help): **frps.toml** ```toml bindPort = 7000 quicBindPort = 7000 ``` **frpc.toml** ```toml serverAddr = "YOUR_VPS_IP" serverPort = 7000 transport.protocol = "quic" ``` Restart frps/frpc and test again.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 11, 2026):

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

<!-- gh-comment-id:4035424474 --> @github-actions[bot] commented on GitHub (Mar 11, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#4045
No description provided.