[GH-ISSUE #4179] frpc transport: protocol: kcp 似乎无法在非root权限下运行

gitea-mirror commented

2026-05-05 14:07:28 -06:00

Owner

Originally created by @bonjour-py on GitHub (Apr 24, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4179

Bug Description

frpc transport: protocol: kcp 似乎无法在非root权限下运行
os ubuntu desktop 23.10 表现为无法响应

使用sudo 运行正常

奇怪的是在 no-root-user on kalilinux in lxd on this ubuntu 运行正常

frpc Version

0.57.0

frps Version

ghcr.io/fatedier/frps:v0.56.0

System Architecture

linux/amd64

Configurations

webServer:
  port: 7000
serverAddr: -----------------------
serverPort: 30200
transport:
  protocol: kcp
auth:
  token: ----------------------
user: ------------
proxies:
  - name: -------------
    type: tcp
    localPort: ------------
    remotePort: 7018
  - name: -------------
    type: udp
    localPort: ----------
    remotePort: 7018

Logs

bonjour@work:~/文档/frp$ ./frpc -c config.yaml 
2024-04-24 15:48:41.743 [I] [sub/root.go:142] start frpc service for config file [config.yaml]
2024-04-24 15:48:41.743 [I] [client/service.go:294] try to connect to server...
^C^C^C^C^C^C^Z
[1]+  已停止               ./frpc -c config.yaml
bonjour@work:~/文档/frp$ kill -9 %1

[1]+  已停止               ./frpc -c config.yaml
bonjour@work:~/文档/frp$ 
[1]+  已杀死               ./frpc -c config.yaml

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 @bonjour-py on GitHub (Apr 24, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4179 ### Bug Description frpc transport: protocol: kcp 似乎无法在非root权限下运行 os ubuntu desktop 23.10 表现为无法响应使用sudo 运行正常奇怪的是在 no-root-user on kalilinux in lxd on this ubuntu 运行正常 ### frpc Version 0.57.0 ### frps Version ghcr.io/fatedier/frps:v0.56.0 ### System Architecture linux/amd64 ### Configurations ``` webServer: port: 7000 serverAddr: ----------------------- serverPort: 30200 transport: protocol: kcp auth: token: ---------------------- user: ------------ proxies: - name: ------------- type: tcp localPort: ------------ remotePort: 7018 - name: ------------- type: udp localPort: ---------- remotePort: 7018 ``` ### Logs ``` bonjour@work:~/文档/frp$ ./frpc -c config.yaml 2024-04-24 15:48:41.743 [I] [sub/root.go:142] start frpc service for config file [config.yaml] 2024-04-24 15:48:41.743 [I] [client/service.go:294] try to connect to server... ^C^C^C^C^C^C^Z [1]+ 已停止 ./frpc -c config.yaml bonjour@work:~/文档/frp$ kill -9 %1 [1]+ 已停止 ./frpc -c config.yaml bonjour@work:~/文档/frp$ [1]+ 已杀死 ./frpc -c config.yaml ``` ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:07:28 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:07:31 -06:00

Author

Owner

@bonjour-py commented on GitHub (Apr 24, 2024):

等一下ubuntu 24.04吧马上出了看看结果再来反馈

@bonjour-py commented on GitHub (Apr 24, 2024): 等一下ubuntu 24.04吧马上出了看看结果再来反馈

gitea-mirror commented

2026-05-05 14:07:32 -06:00

Author

Owner

@bonjour-py commented on GitHub (Apr 26, 2024):

on ubuntu24.04 ：甚至使用sudo 也无法执行表现和23.10一致无响应

@bonjour-py commented on GitHub (Apr 26, 2024): on ubuntu24.04 ：甚至使用sudo 也无法执行表现和23.10一致无响应

gitea-mirror commented

2026-05-05 14:07:33 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 26, 2024):

建议换 quic 尝试吧

@fatedier commented on GitHub (Apr 26, 2024): 建议换 quic 尝试吧

gitea-mirror commented

2026-05-05 14:07:34 -06:00

Author

Owner

@bonjour-py commented on GitHub (Apr 26, 2024):

建议换 quic 尝试吧

quic目前正常

@bonjour-py commented on GitHub (Apr 26, 2024): > 建议换 quic 尝试吧 quic目前正常

gitea-mirror commented

2026-05-05 14:07:35 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (May 18, 2024):

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

@github-actions[bot] commented on GitHub (May 18, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.