[GH-ISSUE #4579] P2P打洞连接成功后断开重连报错 #3621

Closed
opened 2026-05-05 14:19:29 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @yuhuan05 on GitHub (Dec 11, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4579

Bug Description

在使用P2P打洞成功连接后,中途如果因为网络断开再次重连后会有概率出现

2024-12-11 10:53:34.653 [W] [visitor/xtcp.go:273] [e98b09106949cc2a] [p2p_rdp_visitor2] nathole precheck error: xtcp server for [p2p_rdp_xtcp] doesn't exist
2024-12-11 10:53:44.651 [W] [visitor/xtcp.go:273] [e98b09106949cc2a] [p2p_rdp_visitor2] nathole precheck error: xtcp server for [p2p_rdp_xtcp] doesn't exist
2024-12-11 10:53:54.562 [E] [visitor/xtcp.go:179] [e98b09106949cc2a] [p2p_rdp_visitor2] open tunnel error: open tunnel timeout

该报错持续且无法重连 唯一的方案是在被控制的计算机上重启FRPC的服务。
中途我也在toml中添加以下配置,但是故障依旧
health_check = true
health_check_timeout_s = 1

frpc Version

0.61.0

frps Version

0.61.0

System Architecture

windows/amd64 linux/amd64

Configurations

被控端
[common]
server_addr = ***********
server_port = 7000
token = ***********
health_check = true
health_check_timeout_s = 10

[rdp]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 3389

[p2p_rdp]
type = stcp
sk = ***********
local_ip = 127.0.0.1
local_port = 3389
use_encryption = false
use_compression = false

[p2p_rdp_xtcp]
type = xtcp
sk = ***********
local_ip = 127.0.0.1
local_port = 3389
use_encryption = false
use_compression = false

控制端:
[common]
server_addr = ***********
server_port = 7000
token = ***********
keepTunnelOpen = true
health_check = true
health_check_timeout_s = 10

[p2p_rdp_visitor]
role = visitor
type = stcp
server_name = p2p_rdp
sk = ***********
bind_addr = 127.0.0.1
bind_port = 10000
use_encryption = false
use_compression = false

[p2p_rdp_visitor2]
role = visitor
type = xtcp
server_name = p2p_rdp_xtcp
sk = ***********
bind_addr = 127.0.0.1
bind_port = 10001
use_encryption = false
use_compression = false

frps服务端:
bindAddr = ***********
bindPort = 7000
tcpmuxHTTPConnectPort = 7001 # 指定端口号
tcpmuxPassthrough = true
kcpBindPort = 7000
#quicBindPort = 7001

vhostHTTPPort = 8080
vhostHTTPSPort = 443

transport.maxPoolCount = 2000
transport.tcpMux = true
transport.tcpMuxKeepaliveInterval = 60
transport.tcpKeepalive = 7200
transport.tls.force = false

webServer.addr = ***********
webServer.port = 7500
webServer.user = ***********
webServer.password = ***********
webServer.pprofEnable = true

log.to = "/usr/frps/frp/frps.log"
log.level = "info"
log.maxDays = 3
log.disablePrintColor = false

auth.method = "token"
auth.token = ***********
maxPortsPerClient = 8
udpPacketSize = 1500
natholeAnalysisDataReserveHours = 168

Logs

image
frps.log

Steps to reproduce

  1. P2P打洞成功后网络异常断开后再次连接就会出现该报错

...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @yuhuan05 on GitHub (Dec 11, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4579 ### Bug Description 在使用P2P打洞成功连接后,中途如果因为网络断开再次重连后会有概率出现 2024-12-11 10:53:34.653 [W] [visitor/xtcp.go:273] [e98b09106949cc2a] [p2p_rdp_visitor2] nathole precheck error: xtcp server for [p2p_rdp_xtcp] doesn't exist 2024-12-11 10:53:44.651 [W] [visitor/xtcp.go:273] [e98b09106949cc2a] [p2p_rdp_visitor2] nathole precheck error: xtcp server for [p2p_rdp_xtcp] doesn't exist 2024-12-11 10:53:54.562 [E] [visitor/xtcp.go:179] [e98b09106949cc2a] [p2p_rdp_visitor2] open tunnel error: open tunnel timeout 该报错持续且无法重连 唯一的方案是在被控制的计算机上重启FRPC的服务。 中途我也在toml中添加以下配置,但是故障依旧 health_check = true health_check_timeout_s = 1 ### frpc Version 0.61.0 ### frps Version 0.61.0 ### System Architecture windows/amd64 linux/amd64 ### Configurations 被控端 [common] server_addr = *********** server_port = 7000 token = *********** health_check = true health_check_timeout_s = 10 [rdp] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 3389 [p2p_rdp] type = stcp sk = *********** local_ip = 127.0.0.1 local_port = 3389 use_encryption = false use_compression = false [p2p_rdp_xtcp] type = xtcp sk = *********** local_ip = 127.0.0.1 local_port = 3389 use_encryption = false use_compression = false 控制端: [common] server_addr = *********** server_port = 7000 token = *********** keepTunnelOpen = true health_check = true health_check_timeout_s = 10 [p2p_rdp_visitor] role = visitor type = stcp server_name = p2p_rdp sk = *********** bind_addr = 127.0.0.1 bind_port = 10000 use_encryption = false use_compression = false [p2p_rdp_visitor2] role = visitor type = xtcp server_name = p2p_rdp_xtcp sk = *********** bind_addr = 127.0.0.1 bind_port = 10001 use_encryption = false use_compression = false frps服务端: bindAddr = *********** bindPort = 7000 tcpmuxHTTPConnectPort = 7001 # 指定端口号 tcpmuxPassthrough = true kcpBindPort = 7000 #quicBindPort = 7001 vhostHTTPPort = 8080 vhostHTTPSPort = 443 transport.maxPoolCount = 2000 transport.tcpMux = true transport.tcpMuxKeepaliveInterval = 60 transport.tcpKeepalive = 7200 transport.tls.force = false webServer.addr = *********** webServer.port = 7500 webServer.user = *********** webServer.password = *********** webServer.pprofEnable = true log.to = "/usr/frps/frp/frps.log" log.level = "info" log.maxDays = 3 log.disablePrintColor = false auth.method = "token" auth.token = *********** maxPortsPerClient = 8 udpPacketSize = 1500 natholeAnalysisDataReserveHours = 168 ### Logs ![image](https://github.com/user-attachments/assets/965f126a-7894-4525-8663-0ad920c72c17) [frps.log](https://github.com/user-attachments/files/18089067/frps.log) ### Steps to reproduce 1. P2P打洞成功后网络异常断开后再次连接就会出现该报错 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others
gitea-mirror 2026-05-05 14:19:29 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 26, 2024):

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

<!-- gh-comment-id:2562040173 --> @github-actions[bot] commented on GitHub (Dec 26, 2024): 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#3621
No description provided.