[GH-ISSUE #4648] Mysterious Network Connection Failure

gitea-mirror commented

2026-05-05 14:21:18 -06:00

Owner

Originally created by @NearlyHeadlessJack on GitHub (Jan 22, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4648

Bug Description

摘要：两个frpc连接同一个frps，其中一个永远正常，另一个经常报connection refused , 无法判别是frp的问题还是云服务商的问题。
背景：A、B两服务器均运行Minecraft Server，想通过frp将MC服务器的rcon映射到C服务器上进行其他业务操作。 AB服务器使用的frpc，C服务器使用的frps。
BUG：A服务器的业务完全正常，但B服务器会经常报connection refused。(以下用x.x.x.x代替C服务器IP)
情况一：启动连接时正常，过十几分钟就报错：connect to server error: dial tcp x.x.x.x:7000: connect: connection refused
情况二：启动连接都无法进行，如上。

服务端记录，只在连接成功然后突然断联情况下有：

[control.go:401] [5aa6ff4616974e14] new proxy [rcon1] type [tcp] success
[proxy.go:115] [5aa6ff4616974e14] [rcon1] proxy closing
[proxy.go:201] [5aa6ff4616974e14] [rcon1] listener is closed: accept tcp [::]:10086: use of closed network connection
[control.go:359] [5aa6ff4616974e14] client exit success

在情况二下，服务端没有任何记录。

网络
C服务器是阿里云ECS，A服务器是甘肃电信家庭宽带，B服务器是河北联通家庭宽带。
C服务器安全组已放行bindport。

frpc Version

0.53.2

frps Version

0.53.2

System Architecture

linux/amd64

Configurations

frps.toml

bindPort = 7000
token = "okokok123"

frpc.toml of Server A

serverAddr = "x.x.x.x"
serverPort = 7000
token = "okokok123"

[[proxies]]

name = "rcon"
type = "tcp"
localIP = "127.0.0.1"
localPort = 1001
remotePort = 10085

frpc.toml of Server B

serverAddr = "x.x.x.x"
serverPort = 7000
token = "okokok123"

[[proxies]]

name = "rcon"
type = "tcp"
localIP = "127.0.0.1"
localPort = 1001
remotePort = 10086

Logs

No response

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 @NearlyHeadlessJack on GitHub (Jan 22, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4648 ### Bug Description - 摘要：两个frpc连接同一个frps，其中一个永远正常，另一个经常报`connection refused` , 无法判别是frp的问题还是云服务商的问题。 - 背景：A、B两服务器均运行Minecraft Server，想通过frp将MC服务器的rcon映射到C服务器上进行其他业务操作。 AB服务器使用的frpc，C服务器使用的frps。 - BUG：A服务器的业务完全正常，但B服务器会经常报`connection refused`。(以下用x.x.x.x代替C服务器IP) 情况一：启动连接时正常，过十几分钟就报错：`connect to server error: dial tcp x.x.x.x:7000: connect: connection refused` 情况二：启动连接都无法进行，如上。服务端记录，只在连接成功然后突然断联情况下有： ``` [control.go:401] [5aa6ff4616974e14] new proxy [rcon1] type [tcp] success [proxy.go:115] [5aa6ff4616974e14] [rcon1] proxy closing [proxy.go:201] [5aa6ff4616974e14] [rcon1] listener is closed: accept tcp [::]:10086: use of closed network connection [control.go:359] [5aa6ff4616974e14] client exit success ``` 在情况二下，服务端没有任何记录。 - 网络 C服务器是阿里云ECS，A服务器是甘肃电信家庭宽带，B服务器是河北联通家庭宽带。 C服务器安全组已放行bindport。 ### frpc Version 0.53.2 ### frps Version 0.53.2 ### System Architecture linux/amd64 ### Configurations frps.toml ``` toml bindPort = 7000 token = "okokok123" ``` frpc.toml of Server A ``` toml serverAddr = "x.x.x.x" serverPort = 7000 token = "okokok123" [[proxies]] name = "rcon" type = "tcp" localIP = "127.0.0.1" localPort = 1001 remotePort = 10085 ``` frpc.toml of Server B ``` toml serverAddr = "x.x.x.x" serverPort = 7000 token = "okokok123" [[proxies]] name = "rcon" type = "tcp" localIP = "127.0.0.1" localPort = 1001 remotePort = 10086 ``` ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### 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:21:18 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:21:22 -06:00

Author

Owner

@NearlyHeadlessJack commented on GitHub (Jan 22, 2025):

勘误，Server B的服务名不是rcon，是rcon1

@NearlyHeadlessJack commented on GitHub (Jan 22, 2025): 勘误，Server B的服务名不是rcon，是rcon1

gitea-mirror commented

2026-05-05 14:21:23 -06:00

Author

Owner

@xqzr commented on GitHub (Jan 28, 2025):

勘误，Server B的服务名不是rcon，是rcon1

~~善用“编辑”功能~~

https://github.com/fatedier/frp/issues/4572#issuecomment-2518116808

@xqzr commented on GitHub (Jan 28, 2025): > 勘误，Server B的服务名不是rcon，是rcon1 ~~善用“编辑”功能~~ https://github.com/fatedier/frp/issues/4572#issuecomment-2518116808

gitea-mirror commented

2026-05-05 14:21:24 -06:00

Author

Owner

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

gitea-mirror commented

2026-05-05 14:21:24 -06:00

Author

Owner

@f0lg0 commented on GitHub (Mar 10, 2025):

I'm experiencing the exact same behavior with multiple clients connected to the same server.

@f0lg0 commented on GitHub (Mar 10, 2025): I'm experiencing the exact same behavior with multiple clients connected to the same server.