frps

os: rockylinux 8
version: v0.35 and v0.64

frpc

os: windows 10
version: v0.35 and v0.64

connection

frpc v0.35 connecting frps v0.35 redirect remote port 33389 to local port 3389
frpc v0.64 connecting frps v0.64 redirect remote port 43389 to local port 3389

issue

the remote desktop with port 43389 is much more laggy than the remote desktop with port 33389!

frpc Version

0.35, 0.64

frps Version

0.35, 0.64

System Architecture

frps: linux/amd64, frpc: windows/amd64

Configurations

frp v0.35

frps.ini in rockylinux 8

[common]
bind_addr = 0.0.0.0
bind_port = 0
kcp_bind_port = 7000
detailed_errors_to_client = true
authentication_method = token
token = 123456
max_pool_count = 16

frpc.ini in windows 10

[common]
server_addr = x.x.x.x
server_port = 7000
protocol = kcp
tls_enable = true
token = 123456
pool_count = 2

[win10-rdp]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 33389
use_compression = false

frp v0.64

frps.yml in the same rockylinux8

bindAddr: 0.0.0.0
bindPort: 7100
quicBindPort: 7100
custom404Page: /404.html
auth:
  method: token
  token: 123456

frpc.yml in the same windows 10

serverAddr: x.x.x.x
serverPort: 7100
user: colben
transport:
  protocol: quic
auth:
  method: token
  token: 123456
proxies:
- name: rdp
  type: tcp
  localIP: 127.0.0.1
  localPort: 3389
  remotePort: 43389
  transport:
    useCompression: true

Logs

all normal, nothing error.

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 @colben on GitHub (Sep 17, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4982 ### Bug Description # frps - os: rockylinux 8 - version: v0.35 and v0.64 # frpc - os: windows 10 - version: v0.35 and v0.64 # connection - frpc v0.35 connecting frps v0.35 redirect remote port 33389 to local port 3389 - frpc v0.64 connecting frps v0.64 redirect remote port 43389 to local port 3389 # issue - the remote desktop with port 43389 is much more laggy than the remote desktop with port 33389! ### frpc Version 0.35, 0.64 ### frps Version 0.35, 0.64 ### System Architecture frps: linux/amd64, frpc: windows/amd64 ### Configurations # frp v0.35 - frps.ini in rockylinux 8 ``` [common] bind_addr = 0.0.0.0 bind_port = 0 kcp_bind_port = 7000 detailed_errors_to_client = true authentication_method = token token = 123456 max_pool_count = 16 ``` - frpc.ini in windows 10 ``` [common] server_addr = x.x.x.x server_port = 7000 protocol = kcp tls_enable = true token = 123456 pool_count = 2 [win10-rdp] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 33389 use_compression = false ``` # frp v0.64 - frps.yml in the same rockylinux8 ``` bindAddr: 0.0.0.0 bindPort: 7100 quicBindPort: 7100 custom404Page: /404.html auth: method: token token: 123456 ``` - frpc.yml in the same windows 10 ``` serverAddr: x.x.x.x serverPort: 7100 user: colben transport: protocol: quic auth: method: token token: 123456 proxies: - name: rdp type: tcp localIP: 127.0.0.1 localPort: 3389 remotePort: 43389 transport: useCompression: true ``` ### Logs all normal, nothing error. ### Steps to reproduce ### 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:30:10 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:30:14 -06:00

Author

Owner

@colben commented on GitHub (Sep 18, 2025):

i've changed the protocol to "kcp", it worked.

@colben commented on GitHub (Sep 18, 2025): i've changed the protocol to "kcp", it worked.

gitea-mirror commented

2026-05-05 14:30:14 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 3, 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 (Oct 3, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.