[GH-ISSUE #4816] QUIC connection failed. #3802

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

Originally created by @Einck0 on GitHub (May 26, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4816

Bug Description

Cannot connect after adding transport.protocol = "quic" in frpc.
In addition, I have opened UDP and TCP ports at 7000.

frpc Version

0.61.1

frps Version

0.61.1

System Architecture

windows/amd64

Configurations

frps.toml
"""toml
bindAddr = "0.0.0.0" # 监听所有网卡,允许通过域名访问
bindPort = 7000
quicBindPort = 7000

webServer.addr = "0.0.0.0" # 监听所有网卡
webServer.port = 7500
webServer.user = "e"
webServer.password = "1"

auth.method = "token"
auth.token = "1"

log.level = "warn"
log.to = "/home/data/service/frp/frps.log"
subDomainHost = ".xyz"
"""

frpc.toml
"""toml
serverAddr = ".xyz"
serverPort = 7000
auth.method = "token"
auth.token = "1"
transport.protocol = "quic"
proxies
name = "rdp"
type = "tcp"
localIP = "127.0.0.1"
localPort = 3389
remotePort = 13338
#subdomain = "frp"
"""

Logs

PS D:\Programs\frp> ./frpc -c frpc.toml
2025-05-26 19:21:40.242 [I] [sub/root.go:149] start frpc service for config file [frpc.toml]
2025-05-26 19:21:40.254 [I] [client/service.go:314] try to connect to server...
2025-05-26 19:21:45.274 [W] [client/service.go:317] connect to server error: timeout: no recent network activity
2025-05-26 19:21:45.275 [I] [sub/root.go:167] frpc service for config file [frpc.toml] stopped
login to the server failed: timeout: no recent network activity. With loginFailExit enabled, no additional retries will be attempted

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 @Einck0 on GitHub (May 26, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4816 ### Bug Description Cannot connect after adding transport.protocol = "quic" in frpc. In addition, I have opened UDP and TCP ports at 7000. ### frpc Version 0.61.1 ### frps Version 0.61.1 ### System Architecture windows/amd64 ### Configurations frps.toml """toml bindAddr = "0.0.0.0" # 监听所有网卡,允许通过域名访问 bindPort = 7000 quicBindPort = 7000 webServer.addr = "0.0.0.0" # 监听所有网卡 webServer.port = 7500 webServer.user = "e" webServer.password = "1" auth.method = "token" auth.token = "1" log.level = "warn" log.to = "/home/data/service/frp/frps.log" subDomainHost = ".xyz" """ frpc.toml """toml serverAddr = ".xyz" serverPort = 7000 auth.method = "token" auth.token = "1" transport.protocol = "quic" [[proxies]] name = "rdp" type = "tcp" localIP = "127.0.0.1" localPort = 3389 remotePort = 13338 #subdomain = "frp" """ ### Logs PS D:\Programs\frp> ./frpc -c frpc.toml 2025-05-26 19:21:40.242 [I] [sub/root.go:149] start frpc service for config file [frpc.toml] 2025-05-26 19:21:40.254 [I] [client/service.go:314] try to connect to server... 2025-05-26 19:21:45.274 [W] [client/service.go:317] connect to server error: timeout: no recent network activity 2025-05-26 19:21:45.275 [I] [sub/root.go:167] frpc service for config file [frpc.toml] stopped login to the server failed: timeout: no recent network activity. With loginFailExit enabled, no additional retries will be attempted ### 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:26:03 -06:00
Author
Owner

@fatedier commented on GitHub (May 27, 2025):

Please perform the following actions on your frps server machine:

  • Edit frps.toml: Change log.level = "warn" to log.level = "info".
  • Restart frps.
  • Check the frps logs (at /home/data/service/frp/frps.log): Look for messages confirming it's listening on UDP port 7000 for QUIC.
  • Run netstat:
    Linux: sudo netstat -lunp | grep 7000
    Windows: netstat -ano | findstr ":7000" (and verify the PID belongs to frps)
    Let me know what you find, especially the output of netstat and any relevant lines from the frps log.
<!-- gh-comment-id:2912410779 --> @fatedier commented on GitHub (May 27, 2025): Please perform the following actions on your frps server machine: * Edit frps.toml: Change log.level = "warn" to log.level = "info". * Restart frps. * Check the frps logs (at /home/data/service/frp/frps.log): Look for messages confirming it's listening on UDP port 7000 for QUIC. * Run netstat: Linux: sudo netstat -lunp | grep 7000 Windows: netstat -ano | findstr ":7000" (and verify the PID belongs to frps) Let me know what you find, especially the output of netstat and any relevant lines from the frps log.
Author
Owner

@aguier commented on GitHub (Jun 1, 2025):

我也是相同版本,tcp和kcp均可以连接成功,但是quic不行,也通过netstat和nc确认了frps确实在监听quic的UDP端口,切可以正常连接上相应的UDP端口,但是quic连接不上,客户端连接timeout,服务端没有日志输出

<!-- gh-comment-id:2926503265 --> @aguier commented on GitHub (Jun 1, 2025): 我也是相同版本,tcp和kcp均可以连接成功,但是quic不行,也通过netstat和nc确认了frps确实在监听quic的UDP端口,切可以正常连接上相应的UDP端口,但是quic连接不上,客户端连接timeout,服务端没有日志输出
Author
Owner

@github-actions[bot] commented on GitHub (Jun 16, 2025):

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

<!-- gh-comment-id:2974811131 --> @github-actions[bot] commented on GitHub (Jun 16, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@linonetwo commented on GitHub (Dec 3, 2025):

timeout: no recent network activity 我一开始也是 quic 用不了

https://github.com/fatedier/frp/issues/3378#issuecomment-1569416972 检查防火墙是不是开了 7000 的 UDP

开了 UDP 协议就好了。

<!-- gh-comment-id:3608095644 --> @linonetwo commented on GitHub (Dec 3, 2025): timeout: no recent network activity 我一开始也是 quic 用不了 https://github.com/fatedier/frp/issues/3378#issuecomment-1569416972 检查防火墙是不是开了 7000 的 UDP 开了 UDP 协议就好了。
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#3802
No description provided.