[GH-ISSUE #3378] 嘗試在客戶端使用QUIC 報錯並中斷服務

gitea-mirror commented

2026-05-05 13:44:33 -06:00

Owner

Originally created by @jspantheonlab on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3378

Bug Description

已在服務段開啟QUIC，但在客戶端啟用時無法正常運作

docker run -it -v "/Users/user/frpc.ini:/frpc.ini" -p "7001:7000" --add-host=host.docker.internal:host-gateway --restart unless-stopped --name="frpc" fatedier/frpc:v0.48.0 --config frpc.ini

frpc Version

v0.48.0

frps Version

v0.48.0

System Architecture

linux/amd64

Configurations

#frps.ini
[common]
bind_port = 7000
dashboard_port = 7001
vhost_https_port=6033
vhost_http_port=6032
quic_bind_port = 7000

#frpc.ini
[common]
server_addr = 1.2.3.4
server_port = 7000
protocol = quic

[test]
type = http
custom_domains = example.com
local_port = 3003
local_ip = host.docker.internal

Logs

2023/03/29 05:15:58 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023/03/29 05:16:03 [W] [service.go:134] login to server failed: timeout: no recent network activity
timeout: no recent network activity
2023/03/29 05:16:04 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023/03/29 05:16:09 [W] [service.go:134] login to server failed: timeout: no recent network activity
timeout: no recent network activity
2023/03/29 05:16:09 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023/03/29 05:16:14 [W] [service.go:134] login to server failed: timeout: no recent network activity
timeout: no recent network activity
2023/03/29 05:16:15 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023/03/29 05:16:20 [W] [service.go:134] login to server failed: timeout: no recent network activity
timeout: no recent network activity

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 @jspantheonlab on GitHub (Mar 29, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3378 ### Bug Description 已在服務段開啟QUIC，但在客戶端啟用時無法正常運作 ```sh docker run -it -v "/Users/user/frpc.ini:/frpc.ini" -p "7001:7000" --add-host=host.docker.internal:host-gateway --restart unless-stopped --name="frpc" fatedier/frpc:v0.48.0 --config frpc.ini ``` ### frpc Version v0.48.0 ### frps Version v0.48.0 ### System Architecture linux/amd64 ### Configurations ```ini #frps.ini [common] bind_port = 7000 dashboard_port = 7001 vhost_https_port=6033 vhost_http_port=6032 quic_bind_port = 7000 ``` ```ini #frpc.ini [common] server_addr = 1.2.3.4 server_port = 7000 protocol = quic [test] type = http custom_domains = example.com local_port = 3003 local_ip = host.docker.internal ``` ### Logs ```log 2023/03/29 05:15:58 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details. 2023/03/29 05:16:03 [W] [service.go:134] login to server failed: timeout: no recent network activity timeout: no recent network activity 2023/03/29 05:16:04 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details. 2023/03/29 05:16:09 [W] [service.go:134] login to server failed: timeout: no recent network activity timeout: no recent network activity 2023/03/29 05:16:09 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details. 2023/03/29 05:16:14 [W] [service.go:134] login to server failed: timeout: no recent network activity timeout: no recent network activity 2023/03/29 05:16:15 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details. 2023/03/29 05:16:20 [W] [service.go:134] login to server failed: timeout: no recent network activity timeout: no recent network activity ``` ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [ ] Server Plugin - [X] Extensions - [ ] Others

gitea-mirror closed this issue

2026-05-05 13:44:34 -06:00

gitea-mirror commented

2026-05-05 13:44:38 -06:00

Author

Owner

@xingtongsf commented on GitHub (Mar 30, 2023):

quic使用另外的端口，不要和kcp使用相同的端口，这个在作者帮助里没有明确，但是实际使用下来，kcp和quic不能使用同一端口

@xingtongsf commented on GitHub (Mar 30, 2023): quic使用另外的端口，不要和kcp使用相同的端口，这个在作者帮助里没有明确，但是实际使用下来，kcp和quic不能使用同一端口

gitea-mirror commented

2026-05-05 13:44:39 -06:00

Author

Owner

@jspantheonlab commented on GitHub (Mar 30, 2023):

quic使用另外的端口，不要和kcp使用相同的端口，这个在作者帮助里没有明确，但是实际使用下来，kcp和quic不能使用同一端口

可是沒啟用kcp

@jspantheonlab commented on GitHub (Mar 30, 2023): > quic使用另外的端口，不要和kcp使用相同的端口，这个在作者帮助里没有明确，但是实际使用下来，kcp和quic不能使用同一端口可是沒啟用kcp

gitea-mirror commented

2026-05-05 13:44:40 -06:00

Author

Owner

@superzjg commented on GitHub (Mar 30, 2023):

配置文件看上去沒有問題。考慮端口是不是沒通，比如防火墻。
注意一下：quic、kcp、nat打洞的端口不能相同。

@superzjg commented on GitHub (Mar 30, 2023): 配置文件看上去沒有問題。考慮端口是不是沒通，比如防火墻。注意一下：quic、kcp、nat打洞的端口不能相同。

gitea-mirror commented

2026-05-05 13:44:40 -06:00

Author

Owner

@xqzr commented on GitHub (Apr 9, 2023):

开放 UDP 7000

@xqzr commented on GitHub (Apr 9, 2023): 开放 UDP 7000

gitea-mirror commented

2026-05-05 13:44:41 -06:00

Author

Owner

@qyh214 commented on GitHub (May 8, 2023):

我也遇到了这个问题，题主标注了已关闭是怎么解决的呢

@qyh214 commented on GitHub (May 8, 2023): 我也遇到了这个问题，题主标注了已关闭是怎么解决的呢

gitea-mirror commented

2026-05-05 13:44:42 -06:00

Author

Owner

@liujianying commented on GitHub (May 30, 2023):

frps.ini [common] bind_port = 7000 quic_bind_port = 7000 #vhost_http_port =81 tcp_mux = false #tls_enable = true dashboard_port = 7001 dashboard_user = admin dashboard_pwd = 123456

`
frpc.ini
[common]
server_addr = 124.222.13x.xx
server_port = 7000
protocol = quic
tcp_mux = false
log_file = ./frpc.log
admin_addr = 0.0.0.0
admin_port = 7400
admin_user = admin
admin_pwd = admin

[tcpadb]
type = tcp
local_ip = 127.0.0.1
local_port = 5555
remote_port = 8555
use_compression = true`

报错如下
2023/05/30 22:18:32 [W] [service.go:131] login to server failed: timeout: no recent network activity

@liujianying commented on GitHub (May 30, 2023): ` frps.ini [common] bind_port = 7000 quic_bind_port = 7000 #vhost_http_port =81 tcp_mux = false #tls_enable = true dashboard_port = 7001 dashboard_user = admin dashboard_pwd = 123456` ` frpc.ini [common] server_addr = 124.222.13x.xx server_port = 7000 protocol = quic tcp_mux = false log_file = ./frpc.log admin_addr = 0.0.0.0 admin_port = 7400 admin_user = admin admin_pwd = admin [tcpadb] type = tcp local_ip = 127.0.0.1 local_port = 5555 remote_port = 8555 use_compression = true` ### 报错如下 **2023/05/30 22:18:32 [W] [service.go:131] login to server failed: timeout: no recent network activity**

gitea-mirror commented

2026-05-05 13:44:42 -06:00

Author

Owner

@jspantheonlab commented on GitHub (May 31, 2023):

我也遇到了这个问题，题主标注了已关闭是怎么解决的呢

服務器UDP端口沒開放看看防火牆

@jspantheonlab commented on GitHub (May 31, 2023): > 我也遇到了这个问题，题主标注了已关闭是怎么解决的呢服務器UDP端口沒開放看看防火牆

Rows
Columns

[GH-ISSUE #3378] 嘗試在客戶端使用QUIC 報錯並中斷服務 #2706

Bug Description

frpc Version

frps Version

System Architecture

Configurations

Logs

Steps to reproduce

Affected area