github-starred/frp
2
0
Fork 0
mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00
Code Issues 40 Projects Packages Wiki Activity Actions 1

[GH-ISSUE #4269] frp 0.58.1 Server 连接几分钟后断链 #3365

New issue
Closed
opened 2026-05-05 14:10:11 -06:00 by gitea-mirror · 12 comments
gitea-mirror commented 2026-05-05 14:10:11 -06:00
Owner
Copy link

Originally created by @JustinTangChina on GitHub (Jun 7, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4269

Bug Description

服务端是 ubuntu 24 用得frp 0.58.1
客户端是 群辉 dsm 7,2,1 用的 frp 0.58.1客户端

群辉正常连接后，不做任何操作 过几分钟后 会tcpmux 超时断开连接，服务端和客户端已添加配置项

大神门 救救我！

服务端配置文件

bindPort = 7000

transport.maxPoolCount = 50
webServer.addr = "0.0.0.0"
webServer.port = 7500
webServer.user = "admin"
webServer.password = "admin"

webServer.pprofEnable = false
enablePrometheus = true

vhostHTTPPort = 8008
vhostHTTPSPort = 443

console or real logFile path like ./frps.log

log.to = "/var/log/frp/frps.log"

trace, debug, info, warn, error

log.level = "trace"
log.maxDays = 3

disable log colors when log.to is console, default is false

log.disablePrintColor = false

detailedErrorsToClient = true
auth.method = "token"
auth.token = "12345678"

allowPorts = [
{ start = 0, end = 65535 }
]
maxPortsPerClient = 0
subDomainHost = "nas.6173.online"
udpPacketSize = 1500

transport.heartbeatTimeout = 90
transport.tcpMuxKeepaliveInterval=30
transport.tcpMux =true
transport.tcpKeepalive=7200

客户端配置：
user="nas"
serverAddr = "10.123.123.10"
serverPort = 7000
auth.method = "token"
auth.token = "12345678"

console or real logFile path like ./frps.log

log.to = "/var/log/frpc.log"

trace, debug, info, warn, error

log.level = "trace"
log.maxDays = 3

disable log colors when log.to is console, default is false

log.disablePrintColor = true
transport.tcpMuxKeepaliveInterval = 30
transport.heartbeatInterval = 30
transport.dialServerTimeout=10
transport.dialServerKeepalive =7200
transport.poolCount = 10
transport.tcpMux = true
transport.connectServerLocalIP="192.168.1.6"
transport.heartbeatTimeout = 90

proxies
name = "nas"
type = "tcp"
localIP = "192.168.1.6"
localPort = 5000
remotePort = 5000

proxies
name = "ssh"
type = "tcp"
localIP = "192.168.1.6"
localPort = 22
remotePort = 522

proxies
name = "qinglong"
type = "tcp"
localIP = "192.168.1.6"
localPort = 5700
remotePort = 5700

proxies
name = "transmission"
type = "tcp"
localIP = "192.168.1.6"
localPort = 9091
remotePort = 9091

每次断链后，服务端 报错信息
2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp]
2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200]
2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:107] Http request: [/api/serverinfo]
2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:100] Http response [/api/serverinfo]: code [200]
2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp]
2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200]
2024-06-07 07:18:46.164 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:19:16.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:19:46.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:20:16.176 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:20:46.167 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:21:16.168 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:21:46.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:22:16.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:22:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:23:16.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:23:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:24:28.069 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ftpfile] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ftpfile] listener is closed: accept tcp [::]:2121: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ssh] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ssh] listener is closed: accept tcp [::]:522: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.clashUI] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.clashUI] listener is closed: accept tcp [::]:9080: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.qinglong] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.qinglong] listener is closed: accept tcp [::]:5700: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.transmission] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.transmission] listener is closed: accept tcp [::]:9091: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.nas] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.nas] listener is closed: accept tcp [::]:5000: use of closed network connection
2024-06-07 07:24:28.070 [I] [server/control.go:357] [317bf49fc5283314] client exit success
2024-06-07 07:24:28.070 [D] [server/service.go:525] Accept new mux stream error: keepalive timeout

客户端报错信息

2024-06-07 15:21:46.093 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:21:46.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:22:16.094 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:22:16.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:22:46.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:22:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:23:16.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:23:16.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:23:46.096 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:23:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:24:16.097 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:24:37.999 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:24:38.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:24:48.000 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:24:48.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:24:58.001 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:24:58.001 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:25:08.002 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:25:08.002 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:25:18.003 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:25:38.004 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:25:48.004 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:26:08.005 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:26:18.005 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:26:38.006 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:26:48.007 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:27:08.008 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:27:15.442 [I] [client/service.go:286] [317bf49fc5283314] login to server success, get run id [317bf49fc5283314]
2024-06-07 15:27:15.442 [I] [proxy/proxy_manager.go:173] [317bf49fc5283314] proxy added: [nas.nas nas.ssh nas.qinglong nas.transmission nas.ftpfile nas.clashUI]
2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.ssh] change status from [new] to [wait start]
2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.clashUI] change status from [new] to [wait start]

frpc Version

0.58.1

frps Version

0.58.1

System Architecture

linux/amd64

Configurations

客户端：

user="nas"
serverAddr = "10.123.123.10"
serverPort = 7000
auth.method = "token"
auth.token = "12345678"

console or real logFile path like ./frps.log

log.to = "/var/log/frpc.log"

trace, debug, info, warn, error

log.level = "trace"
log.maxDays = 3

disable log colors when log.to is console, default is false

log.disablePrintColor = true
transport.tcpMuxKeepaliveInterval = 30
transport.heartbeatInterval = 30
transport.dialServerTimeout=10
transport.dialServerKeepalive =7200
transport.poolCount = 10
transport.tcpMux = true
transport.connectServerLocalIP="192.168.1.6"
transport.heartbeatTimeout = 90

proxies
name = "nas"
type = "tcp"
localIP = "192.168.1.6"
localPort = 5000
remotePort = 5000

proxies
name = "ssh"
type = "tcp"
localIP = "192.168.1.6"
localPort = 22
remotePort = 522

proxies
name = "qinglong"
type = "tcp"
localIP = "192.168.1.6"
localPort = 5700
remotePort = 5700

proxies
name = "transmission"
type = "tcp"
localIP = "192.168.1.6"
localPort = 9091
remotePort = 9091

proxies
name = "ftpfile"
type = "tcp"
localIP = "192.168.1.6"
localPort = 21
remotePort = 2121

服务端:
bindPort = 7000

transport.maxPoolCount = 50
webServer.addr = "0.0.0.0"
webServer.port = 7500
webServer.user = "admin"
webServer.password = "admin"

webServer.pprofEnable = false
enablePrometheus = true

vhostHTTPPort = 8008
vhostHTTPSPort = 443

console or real logFile path like ./frps.log

log.to = "/var/log/frp/frps.log"

trace, debug, info, warn, error

log.level = "trace"
log.maxDays = 3

disable log colors when log.to is console, default is false

log.disablePrintColor = false

detailedErrorsToClient = true
auth.method = "token"
auth.token = "12345678"

allowPorts = [
{ start = 0, end = 65535 }
]
maxPortsPerClient = 0
subDomainHost = "nas.098768.online"
udpPacketSize = 1500

transport.heartbeatTimeout = 90
transport.tcpMuxKeepaliveInterval=30
transport.tcpMux =true
transport.tcpKeepalive=7200

Logs

每次断链后，服务端 报错信息
2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp]
2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200]
2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:107] Http request: [/api/serverinfo]
2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:100] Http response [/api/serverinfo]: code [200]
2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp]
2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200]
2024-06-07 07:18:46.164 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:19:16.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:19:46.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:20:16.176 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:20:46.167 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:21:16.168 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:21:46.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:22:16.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:22:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:23:16.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:23:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat
2024-06-07 07:24:28.069 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ftpfile] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ftpfile] listener is closed: accept tcp [::]:2121: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ssh] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ssh] listener is closed: accept tcp [::]:522: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.clashUI] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.clashUI] listener is closed: accept tcp [::]:9080: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.qinglong] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.qinglong] listener is closed: accept tcp [::]:5700: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.transmission] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.transmission] listener is closed: accept tcp [::]:9091: use of closed network connection
2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.nas] proxy closing
2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.nas] listener is closed: accept tcp [::]:5000: use of closed network connection
2024-06-07 07:24:28.070 [I] [server/control.go:357] [317bf49fc5283314] client exit success
2024-06-07 07:24:28.070 [D] [server/service.go:525] Accept new mux stream error: keepalive timeout

客户端报错信息

2024-06-07 15:21:46.093 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:21:46.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:22:16.094 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:22:16.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:22:46.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:22:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:23:16.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:23:16.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:23:46.096 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:23:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server
2024-06-07 15:24:16.097 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF
2024-06-07 15:24:27.999 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:24:37.999 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:24:38.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:24:48.000 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:24:48.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:24:58.001 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:24:58.001 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:25:08.002 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:25:08.002 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:25:18.003 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:25:38.004 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:25:48.004 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:26:08.005 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:26:18.005 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:26:38.006 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:26:48.007 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout
2024-06-07 15:27:08.008 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server...
2024-06-07 15:27:15.442 [I] [client/service.go:286] [317bf49fc5283314] login to server success, get run id [317bf49fc5283314]
2024-06-07 15:27:15.442 [I] [proxy/proxy_manager.go:173] [317bf49fc5283314] proxy added: [nas.nas nas.ssh nas.qinglong nas.transmission nas.ftpfile nas.clashUI]
2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.ssh] change status from [new] to [wait start]
2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.clashUI] change status from [new] to [wait start]

Steps to reproduce

  1. 大神来救救我啊
  2. 连接几分钟后会断线
  3. 给群辉nas传数据的时候 几分钟后会断链
    ...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @JustinTangChina on GitHub (Jun 7, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4269 ### Bug Description 服务端是 ubuntu 24 用得frp 0.58.1 客户端是 群辉 dsm 7,2,1 用的 frp 0.58.1客户端 群辉正常连接后，不做任何操作 过几分钟后 会tcpmux 超时断开连接，服务端和客户端已添加配置项 大神门 救救我！ 服务端配置文件 bindPort = 7000 transport.maxPoolCount = 50 webServer.addr = "0.0.0.0" webServer.port = 7500 webServer.user = "admin" webServer.password = "admin" webServer.pprofEnable = false enablePrometheus = true vhostHTTPPort = 8008 vhostHTTPSPort = 443 # console or real logFile path like ./frps.log log.to = "/var/log/frp/frps.log" # trace, debug, info, warn, error log.level = "trace" log.maxDays = 3 # disable log colors when log.to is console, default is false log.disablePrintColor = false detailedErrorsToClient = true auth.method = "token" auth.token = "12345678" allowPorts = [ { start = 0, end = 65535 } ] maxPortsPerClient = 0 subDomainHost = "nas.6173.online" udpPacketSize = 1500 transport.heartbeatTimeout = 90 transport.tcpMuxKeepaliveInterval=30 transport.tcpMux =true transport.tcpKeepalive=7200 客户端配置： user="nas" serverAddr = "10.123.123.10" serverPort = 7000 auth.method = "token" auth.token = "12345678" # console or real logFile path like ./frps.log log.to = "/var/log/frpc.log" # trace, debug, info, warn, error log.level = "trace" log.maxDays = 3 # disable log colors when log.to is console, default is false log.disablePrintColor = true transport.tcpMuxKeepaliveInterval = 30 transport.heartbeatInterval = 30 transport.dialServerTimeout=10 transport.dialServerKeepalive =7200 transport.poolCount = 10 transport.tcpMux = true transport.connectServerLocalIP="192.168.1.6" transport.heartbeatTimeout = 90 [[proxies]] name = "nas" type = "tcp" localIP = "192.168.1.6" localPort = 5000 remotePort = 5000 [[proxies]] name = "ssh" type = "tcp" localIP = "192.168.1.6" localPort = 22 remotePort = 522 [[proxies]] name = "qinglong" type = "tcp" localIP = "192.168.1.6" localPort = 5700 remotePort = 5700 [[proxies]] name = "transmission" type = "tcp" localIP = "192.168.1.6" localPort = 9091 remotePort = 9091 每次断链后，服务端 报错信息 2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp] 2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200] 2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:107] Http request: [/api/serverinfo] 2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:100] Http response [/api/serverinfo]: code [200] 2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp] 2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200] 2024-06-07 07:18:46.164 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:19:16.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:19:46.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:20:16.176 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:20:46.167 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:21:16.168 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:21:46.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:22:16.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:22:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:23:16.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:23:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:24:28.069 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ftpfile] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ftpfile] listener is closed: accept tcp [::]:2121: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ssh] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ssh] listener is closed: accept tcp [::]:522: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.clashUI] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.clashUI] listener is closed: accept tcp [::]:9080: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.qinglong] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.qinglong] listener is closed: accept tcp [::]:5700: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.transmission] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.transmission] listener is closed: accept tcp [::]:9091: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.nas] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.nas] listener is closed: accept tcp [::]:5000: use of closed network connection 2024-06-07 07:24:28.070 [I] [server/control.go:357] [317bf49fc5283314] client exit success 2024-06-07 07:24:28.070 [D] [server/service.go:525] Accept new mux stream error: keepalive timeout 客户端报错信息 2024-06-07 15:21:46.093 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:21:46.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:22:16.094 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:22:16.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:22:46.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:22:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:23:16.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:23:16.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:23:46.096 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:23:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:24:16.097 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:24:37.999 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:24:38.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:24:48.000 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:24:48.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:24:58.001 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:24:58.001 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:25:08.002 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:25:08.002 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:25:18.003 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:25:38.004 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:25:48.004 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:26:08.005 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:26:18.005 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:26:38.006 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:26:48.007 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:27:08.008 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:27:15.442 [I] [client/service.go:286] [317bf49fc5283314] login to server success, get run id [317bf49fc5283314] 2024-06-07 15:27:15.442 [I] [proxy/proxy_manager.go:173] [317bf49fc5283314] proxy added: [nas.nas nas.ssh nas.qinglong nas.transmission nas.ftpfile nas.clashUI] 2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.ssh] change status from [new] to [wait start] 2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.clashUI] change status from [new] to [wait start] ### frpc Version 0.58.1 ### frps Version 0.58.1 ### System Architecture linux/amd64 ### Configurations 客户端： user="nas" serverAddr = "10.123.123.10" serverPort = 7000 auth.method = "token" auth.token = "12345678" # console or real logFile path like ./frps.log log.to = "/var/log/frpc.log" # trace, debug, info, warn, error log.level = "trace" log.maxDays = 3 # disable log colors when log.to is console, default is false log.disablePrintColor = true transport.tcpMuxKeepaliveInterval = 30 transport.heartbeatInterval = 30 transport.dialServerTimeout=10 transport.dialServerKeepalive =7200 transport.poolCount = 10 transport.tcpMux = true transport.connectServerLocalIP="192.168.1.6" transport.heartbeatTimeout = 90 [[proxies]] name = "nas" type = "tcp" localIP = "192.168.1.6" localPort = 5000 remotePort = 5000 [[proxies]] name = "ssh" type = "tcp" localIP = "192.168.1.6" localPort = 22 remotePort = 522 [[proxies]] name = "qinglong" type = "tcp" localIP = "192.168.1.6" localPort = 5700 remotePort = 5700 [[proxies]] name = "transmission" type = "tcp" localIP = "192.168.1.6" localPort = 9091 remotePort = 9091 [[proxies]] name = "ftpfile" type = "tcp" localIP = "192.168.1.6" localPort = 21 remotePort = 2121 服务端: bindPort = 7000 transport.maxPoolCount = 50 webServer.addr = "0.0.0.0" webServer.port = 7500 webServer.user = "admin" webServer.password = "admin" webServer.pprofEnable = false enablePrometheus = true vhostHTTPPort = 8008 vhostHTTPSPort = 443 # console or real logFile path like ./frps.log log.to = "/var/log/frp/frps.log" # trace, debug, info, warn, error log.level = "trace" log.maxDays = 3 # disable log colors when log.to is console, default is false log.disablePrintColor = false detailedErrorsToClient = true auth.method = "token" auth.token = "12345678" allowPorts = [ { start = 0, end = 65535 } ] maxPortsPerClient = 0 subDomainHost = "nas.098768.online" udpPacketSize = 1500 transport.heartbeatTimeout = 90 transport.tcpMuxKeepaliveInterval=30 transport.tcpMux =true transport.tcpKeepalive=7200 ### Logs 每次断链后，服务端 报错信息 2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp] 2024-06-07 07:18:35.914 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200] 2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:107] Http request: [/api/serverinfo] 2024-06-07 07:18:40.156 [I] [server/dashboard_api.go:100] Http response [/api/serverinfo]: code [200] 2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:227] Http request: [/api/proxy/tcp] 2024-06-07 07:18:41.304 [I] [server/dashboard_api.go:221] Http response [/api/proxy/tcp]: code [200] 2024-06-07 07:18:46.164 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:19:16.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:19:46.165 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:20:16.176 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:20:46.167 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:21:16.168 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:21:46.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:22:16.169 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:22:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:23:16.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:23:46.171 [D] [server/control.go:430] [317bf49fc5283314] receive heartbeat 2024-06-07 07:24:28.069 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ftpfile] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ftpfile] listener is closed: accept tcp [::]:2121: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.ssh] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.ssh] listener is closed: accept tcp [::]:522: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.clashUI] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.clashUI] listener is closed: accept tcp [::]:9080: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.qinglong] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.qinglong] listener is closed: accept tcp [::]:5700: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.transmission] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.transmission] listener is closed: accept tcp [::]:9091: use of closed network connection 2024-06-07 07:24:28.070 [I] [proxy/proxy.go:115] [317bf49fc5283314] [nas.nas] proxy closing 2024-06-07 07:24:28.070 [W] [proxy/proxy.go:201] [317bf49fc5283314] [nas.nas] listener is closed: accept tcp [::]:5000: use of closed network connection 2024-06-07 07:24:28.070 [I] [server/control.go:357] [317bf49fc5283314] client exit success 2024-06-07 07:24:28.070 [D] [server/service.go:525] Accept new mux stream error: keepalive timeout 客户端报错信息 2024-06-07 15:21:46.093 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:21:46.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:22:16.094 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:22:16.241 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:22:46.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:22:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:23:16.095 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:23:16.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:23:46.096 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:23:46.243 [D] [client/control.go:193] [317bf49fc5283314] receive heartbeat from server 2024-06-07 15:24:16.097 [D] [client/control.go:240] [317bf49fc5283314] send heartbeat to server 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.998 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [T] [client/control.go:145] [317bf49fc5283314] work connection closed before response StartWorkConn message: EOF 2024-06-07 15:24:27.999 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:24:37.999 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:24:38.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:24:48.000 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:24:48.000 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:24:58.001 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:24:58.001 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:25:08.002 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:25:08.002 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:25:18.003 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:25:38.004 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:25:48.004 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:26:08.005 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:26:18.005 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:26:38.006 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:26:48.007 [W] [client/service.go:297] [317bf49fc5283314] connect to server error: dial tcp 192.168.1.6:0->10.123.123.10:7000: i/o timeout 2024-06-07 15:27:08.008 [I] [client/service.go:294] [317bf49fc5283314] try to connect to server... 2024-06-07 15:27:15.442 [I] [client/service.go:286] [317bf49fc5283314] login to server success, get run id [317bf49fc5283314] 2024-06-07 15:27:15.442 [I] [proxy/proxy_manager.go:173] [317bf49fc5283314] proxy added: [nas.nas nas.ssh nas.qinglong nas.transmission nas.ftpfile nas.clashUI] 2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.ssh] change status from [new] to [wait start] 2024-06-07 15:27:15.442 [T] [proxy/proxy_wrapper.go:200] [317bf49fc5283314] [nas.clashUI] change status from [new] to [wait start] ### Steps to reproduce 1. 大神来救救我啊 2. 连接几分钟后会断线 3. 给群辉nas传数据的时候 几分钟后会断链 ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [X] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:10:11 -06:00
gitea-mirror commented 2026-05-05 14:10:15 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Jun 7, 2024):

尽量用最简化的配置，你不清楚的那一堆 transport 配置都删除掉，先从最简化的配置开始测试，弄懂一个配置项再加一个去尝试。

<!-- gh-comment-id:2154296151 --> @fatedier commented on GitHub (Jun 7, 2024): 尽量用最简化的配置，你不清楚的那一堆 transport 配置都删除掉，先从最简化的配置开始测试，弄懂一个配置项再加一个去尝试。
gitea-mirror commented 2026-05-05 14:10:16 -06:00
Author
Owner
Copy link

@xqzr commented on GitHub (Jun 8, 2024):

看起来是网络问题，可以尝试持续 ping 10.123.123.10 观察 frp 断链时，是否 ping 通

<!-- gh-comment-id:2155892442 --> @xqzr commented on GitHub (Jun 8, 2024): 看起来是**网络问题**，可以尝试持续 `ping 10.123.123.10` 观察 frp 断链时，是否 ping 通
gitea-mirror commented 2026-05-05 14:10:16 -06:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jun 30, 2024):

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

<!-- gh-comment-id:2198386680 --> @github-actions[bot] commented on GitHub (Jun 30, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
gitea-mirror commented 2026-05-05 14:10:17 -06:00
Author
Owner
Copy link

@Greeed-islanl commented on GitHub (Jul 7, 2024):

I had the same situation as him.
0.58.1
The FRTC>FRPS connection disconnects and reconnects itself every 90s

Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.514 [I] [client/service.go:294] [d024c066cf3db8db] try to connect to server...
Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.622 [I] [client/service.go:286] [d024c066cf3db8db] login to server success, get run id [d024c066cf3db8db]
Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.623 [I] [proxy/proxy_manager.go:173] [d024c066cf3db8db] proxy added: [mumble-tcp]
Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.659 [I] [client/control.go:168] [d024c066cf3db8db] [mumble-tcp] start proxy success
Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.669 [I] [client/service.go:294] [d024c066cf3db8db] try to connect to server...
Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.780 [I] [client/service.go:286] [d024c066cf3db8db] login to server success, get run id [d024c066cf3db8db]
Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.780 [I] [proxy/proxy_manager.go:173] [d024c066cf3db8db] proxy added: [mumble-tcp]
Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.826 [I] [client/control.go:168] [d024c066cf3db8db] [mumble-tcp] start proxy success

FRPC

serverAddr = "*
serverPort = *
auth.method = "token"
auth.token = ""
proxies
name = ""
type = "tcp"
localIP = "*"
localPort = *
remotePort = *

FRPS

bindAddr = "0.0.0.0"
bindPort = 5443
kcpBindPort = 5443
quicBindPort = 443
transport.heartbeatTimeout = 90
transport.maxPoolCount = 5
transport.tcpMux = true
vhostHTTPPort = 80
vhostHTTPSPort = 443
webServer.addr = "0.0.0.0"
webServer.port = *
webServer.user = ""
webServer.password = ""
log.to = "enable"
log.level = "info"
log.maxDays = 3
auth.method = "token"
auth.token = ""
subDomainHost = ""

<!-- gh-comment-id:2212468804 --> @Greeed-islanl commented on GitHub (Jul 7, 2024): I had the same situation as him. 0.58.1 The FRTC>FRPS connection disconnects and reconnects itself every 90s Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.514 [I] [client/service.go:294] [d024c066cf3db8db] try to connect to server... Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.622 [I] [client/service.go:286] [d024c066cf3db8db] login to server success, get run id [d024c066cf3db8db] Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.623 [I] [proxy/proxy_manager.go:173] [d024c066cf3db8db] proxy added: [mumble-tcp] Jul 07 22:19:03 sh-all-n2n frpc[84765]: 2024-07-07 22:19:03.659 [I] [client/control.go:168] [d024c066cf3db8db] [mumble-tcp] start proxy success Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.669 [I] [client/service.go:294] [d024c066cf3db8db] try to connect to server... Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.780 [I] [client/service.go:286] [d024c066cf3db8db] login to server success, get run id [d024c066cf3db8db] Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.780 [I] [proxy/proxy_manager.go:173] [d024c066cf3db8db] proxy added: [mumble-tcp] Jul 07 22:20:33 sh-all-n2n frpc[84765]: 2024-07-07 22:20:33.826 [I] [client/control.go:168] [d024c066cf3db8db] [mumble-tcp] start proxy success FRPC serverAddr = "* serverPort = * auth.method = "token" auth.token = "*" [[proxies]] name = "*" type = "tcp" localIP = "*" localPort = * remotePort = * FRPS bindAddr = "0.0.0.0" bindPort = 5443 kcpBindPort = 5443 quicBindPort = 443 transport.heartbeatTimeout = 90 transport.maxPoolCount = 5 transport.tcpMux = true vhostHTTPPort = 80 vhostHTTPSPort = 443 webServer.addr = "0.0.0.0" webServer.port = * webServer.user = "*" webServer.password = "*" log.to = "enable" log.level = "info" log.maxDays = 3 auth.method = "token" auth.token = "*" subDomainHost = "*"
gitea-mirror commented 2026-05-05 14:10:19 -06:00
Author
Owner
Copy link

@Greeed-islanl commented on GitHub (Jul 7, 2024):

2024-07-07 14:26:35.706 [W] [server/control.go:307] [d024c066cf3db8db] heartbeat timeout

<!-- gh-comment-id:2212470075 --> @Greeed-islanl commented on GitHub (Jul 7, 2024): 2024-07-07 14:26:35.706 [W] [server/control.go:307] [d024c066cf3db8db] heartbeat timeout
gitea-mirror commented 2026-05-05 14:10:19 -06:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jul 29, 2024):

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

<!-- gh-comment-id:2254735800 --> @github-actions[bot] commented on GitHub (Jul 29, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
gitea-mirror commented 2026-05-05 14:10:19 -06:00
Author
Owner
Copy link

@arui3015 commented on GitHub (Jul 30, 2024):

我也是同样的问题，之前的版本貌似没有出现过

<!-- gh-comment-id:2257379721 --> @arui3015 commented on GitHub (Jul 30, 2024): 我也是同样的问题，之前的版本貌似没有出现过
gitea-mirror commented 2026-05-05 14:10:19 -06:00
Author
Owner
Copy link

@haimian467 commented on GitHub (Aug 19, 2024):

同样的问题，0.58.1以及0.59都会出现，换成0.57 好了

<!-- gh-comment-id:2295570608 --> @haimian467 commented on GitHub (Aug 19, 2024): 同样的问题，0.58.1以及0.59都会出现，换成0.57 好了
gitea-mirror commented 2026-05-05 14:10:20 -06:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Sep 10, 2024):

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

<!-- gh-comment-id:2339386837 --> @github-actions[bot] commented on GitHub (Sep 10, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
gitea-mirror commented 2026-05-05 14:10:20 -06:00
Author
Owner
Copy link

@focuseyes360 commented on GitHub (Jan 21, 2025):

Image
这个不能停了，1.现象：
公网云服务器linux系统上部署frps，同一路由器下挂三个相同配置的linux设备frpc，同样网络情况下，前两个设备稳如狗，第三个出现幺蛾子了，尝试了v0.48.0 、v0.57.0、v0.60.0 版本，过几分钟到半小时必定在frps server日志上出现frps [service.go:450] accept new mux stream error: keepalive timeout，然后断线重连成功，平均每小时断线重连2次左右。前面这几个版本尝试了issue中提到的修改keepmuxalive 和keepheartalive参数都没有效果。后来把frps更换成了v0.60.0 ，上面两个设备很稳定，但是第三个设备依然会断链，日志基本都是accept new mux stream error: keepalive timeout 。

  1. 出现断线问题时的日志：
    【frps】日志：
    2025/01/20 12:58:44 [D] [control.go:493] [8fd40d4957c2f938] receive heartbeat
    2025/01/20 12:58:57 [D] [control.go:493] [8ad2c6c0839b61a4] receive heartbeat
    2025/01/20 12:59:07 [D] [control.go:493] [6e811ef4307be7d7] receive heartbeat
    2025/01/20 12:59:14 [D] [control.go:493] [8fd40d4957c2f938] receive heartbeat
    2025/01/20 12:59:27 [D] [control.go:493] [8ad2c6c0839b61a4] receive heartbeat
    2025/01/20 12:59:37 [D] [control.go:493] [6e811ef4307be7d7] receive heartbeat
    2025/01/20 12:59:44 [D] [control.go:493] [8fd40d4957c2f938] receive heartbeat
    2025/01/20 12:59:57 [D] [service.go:450] Accept new mux stream error: keepalive timeout
    2025/01/20 12:59:57 [D] [control.go:334] [6879c9f0ff6df0a4] control connection closed
    2025/01/20 12:59:57 [I] [control.go:306] [6879c9f0ff6df0a4] control writer is closing
    2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.id] proxy closing
    2025/01/20 12:59:57 [D] [proxy.go:326] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] join connections closed
    2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.id] listener is closed: accept tcp [::]:7025: use of closed network connection
    2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.web] proxy closing
    2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.web] listener is closed: accept tcp [::]:7023: use of closed network connection
    2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.asd] proxy closing
    2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.asd] listener is closed: accept tcp [::]:7024: use of closed network connection
    2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.bm] proxy closing
    2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.bm] listener is closed: accept tcp [::]:7026: use of closed network connection
    2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] proxy closing
    2025/01/20 12:59:57 [I] [control.go:395] [6879c9f0ff6df0a4] client exit success
    2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] listener is closed: listener closed
    2025/01/20 12:59:57 [D] [control.go:493] [8ad2c6c0839b61a4] receive heartbeat
    2025/01/20 12:59:57 [T] [service.go:423] start check TLS connection...
    2025/01/20 12:59:57 [T] [service.go:432] check TLS connection success, isTLS: true custom: false
    2025/01/20 12:59:57 [I] [service.go:500] [6879c9f0ff6df0a4] client login info: ip [49.65.xx.xx:5421] version [0.60.0] hostname [] os [linux] arch [amd64]
    2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.asd] tcp proxy listen port [7024]
    2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.asd] type [tcp] success
    2025/01/20 12:59:57 [D] [control.go:218] [6879c9f0ff6df0a4] new work connection registered
    2025/01/20 12:59:57 [I] [stcp.go:36] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] stcp proxy custom listen success
    2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.stcp-home-xxx] type [stcp] success
    2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.id] tcp proxy listen port [7025]
    2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.id] type [tcp] success
    2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.bm] tcp proxy listen port [7026]
    2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.bm] type [tcp] success
    2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.web] tcp proxy listen port [7023]
    2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.web] type [tcp] success

【frpc】日志：
2025-01-20 12:59:57.229 [I] [client/service.go:295] [6879c9f0ff6df0a4] try to connect to server...
2025-01-20 12:59:57.229 [D] [proxy/proxy.go:222] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] join connections closed
2025-01-20 12:59:57.314 [I] [client/service.go:287] [6879c9f0ff6df0a4] login to server success, get run id [6879c9f0ff6df0a4]
2025-01-20 12:59:57.314 [I] [proxy/proxy_manager.go:173] [6879c9f0ff6df0a4] proxy added: [box-19.web box-19.as box-19.ids box-19.bm box-19.stcp-home-xxx]
2025-01-20 12:59:57.342 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.asd] start proxy success
2025-01-20 12:59:57.343 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] start proxy success
2025-01-20 12:59:57.343 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.id] start proxy success
2025-01-20 12:59:57.343 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.bm] start proxy success
2025-01-20 12:59:57.372 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.web] start proxy success

3.烦请大大们帮忙看看到底是什么问题导致frps Accept new mux stream error: keepalive timeout，多谢！！！

<!-- gh-comment-id:2603928337 --> @focuseyes360 commented on GitHub (Jan 21, 2025): ![Image](https://github.com/user-attachments/assets/2f4dd3cf-49e9-4509-bfac-6a85c7c55122) 这个不能停了，1.现象： 公网云服务器linux系统上部署frps，同一路由器下挂三个相同配置的linux设备frpc，同样网络情况下，前两个设备稳如狗，第三个出现幺蛾子了，尝试了v0.48.0 、v0.57.0、v0.60.0 版本，过几分钟到半小时必定在frps server日志上出现frps [service.go:450] accept new mux stream error: keepalive timeout，然后断线重连成功，平均每小时断线重连2次左右。前面这几个版本尝试了issue中提到的修改keepmuxalive 和keepheartalive参数都没有效果。后来把frps更换成了v0.60.0 ，上面两个设备很稳定，但是第三个设备依然会断链，日志基本都是accept new mux stream error: keepalive timeout 。 2. 出现断线问题时的日志： 【frps】日志： 2025/01/20 12:58:44 [D] [control.go:493] [8fd40d4957c2f938] receive heartbeat 2025/01/20 12:58:57 [D] [control.go:493] [8ad2c6c0839b61a4] receive heartbeat 2025/01/20 12:59:07 [D] [control.go:493] [6e811ef4307be7d7] receive heartbeat 2025/01/20 12:59:14 [D] [control.go:493] [8fd40d4957c2f938] receive heartbeat 2025/01/20 12:59:27 [D] [control.go:493] [8ad2c6c0839b61a4] receive heartbeat 2025/01/20 12:59:37 [D] [control.go:493] [6e811ef4307be7d7] receive heartbeat 2025/01/20 12:59:44 [D] [control.go:493] [8fd40d4957c2f938] receive heartbeat 2025/01/20 12:59:57 [D] [service.go:450] Accept new mux stream error: keepalive timeout 2025/01/20 12:59:57 [D] [control.go:334] [6879c9f0ff6df0a4] control connection closed 2025/01/20 12:59:57 [I] [control.go:306] [6879c9f0ff6df0a4] control writer is closing 2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.id] proxy closing 2025/01/20 12:59:57 [D] [proxy.go:326] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] join connections closed 2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.id] listener is closed: accept tcp [::]:7025: use of closed network connection 2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.web] proxy closing 2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.web] listener is closed: accept tcp [::]:7023: use of closed network connection 2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.asd] proxy closing 2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.asd] listener is closed: accept tcp [::]:7024: use of closed network connection 2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.bm] proxy closing 2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.bm] listener is closed: accept tcp [::]:7026: use of closed network connection 2025/01/20 12:59:57 [I] [proxy.go:98] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] proxy closing 2025/01/20 12:59:57 [I] [control.go:395] [6879c9f0ff6df0a4] client exit success 2025/01/20 12:59:57 [W] [proxy.go:186] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] listener is closed: listener closed 2025/01/20 12:59:57 [D] [control.go:493] [8ad2c6c0839b61a4] receive heartbeat 2025/01/20 12:59:57 [T] [service.go:423] start check TLS connection... 2025/01/20 12:59:57 [T] [service.go:432] check TLS connection success, isTLS: true custom: false 2025/01/20 12:59:57 [I] [service.go:500] [6879c9f0ff6df0a4] client login info: ip [49.65.xx.xx:5421] version [0.60.0] hostname [] os [linux] arch [amd64] 2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.asd] tcp proxy listen port [7024] 2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.asd] type [tcp] success 2025/01/20 12:59:57 [D] [control.go:218] [6879c9f0ff6df0a4] new work connection registered 2025/01/20 12:59:57 [I] [stcp.go:36] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] stcp proxy custom listen success 2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.stcp-home-xxx] type [stcp] success 2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.id] tcp proxy listen port [7025] 2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.id] type [tcp] success 2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.bm] tcp proxy listen port [7026] 2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.bm] type [tcp] success 2025/01/20 12:59:57 [I] [tcp.go:66] [6879c9f0ff6df0a4] [box-19.web] tcp proxy listen port [7023] 2025/01/20 12:59:57 [I] [control.go:464] [6879c9f0ff6df0a4] new proxy [box-19.web] type [tcp] success 【frpc】日志： 2025-01-20 12:59:57.229 [I] [client/service.go:295] [6879c9f0ff6df0a4] try to connect to server... 2025-01-20 12:59:57.229 [D] [proxy/proxy.go:222] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] join connections closed 2025-01-20 12:59:57.314 [I] [client/service.go:287] [6879c9f0ff6df0a4] login to server success, get run id [6879c9f0ff6df0a4] 2025-01-20 12:59:57.314 [I] [proxy/proxy_manager.go:173] [6879c9f0ff6df0a4] proxy added: [box-19.web box-19.as box-19.ids box-19.bm box-19.stcp-home-xxx] 2025-01-20 12:59:57.342 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.asd] start proxy success 2025-01-20 12:59:57.343 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.stcp-home-xxx] start proxy success 2025-01-20 12:59:57.343 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.id] start proxy success 2025-01-20 12:59:57.343 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.bm] start proxy success 2025-01-20 12:59:57.372 [I] [client/control.go:168] [6879c9f0ff6df0a4] [box-19.web] start proxy success 3.烦请大大们帮忙看看到底是什么问题导致frps Accept new mux stream error: keepalive timeout，多谢！！！
gitea-mirror commented 2026-05-05 14:10:21 -06:00
Author
Owner
Copy link

@linjinxing commented on GitHub (Jun 6, 2025):

我也是半小时重连一次。哎，实在不行，就看看其它的软件了。这个不行。

<!-- gh-comment-id:2947215472 --> @linjinxing commented on GitHub (Jun 6, 2025): 我也是半小时重连一次。哎，实在不行，就看看其它的软件了。这个不行。
gitea-mirror commented 2026-05-05 14:10:21 -06:00
Author
Owner
Copy link

@ssyangchn commented on GitHub (Jun 12, 2025):

同样几分钟就断开

Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.125 [I] [server/service.go:582] [1c78543bf280f879] client login info: ip [xxx.xxx.xx.xx:6427] version [0.48.0] hostname [] os [linux] arch [arm64]
Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.203 [D] [server/control.go:243] [1c78543bf280f879] new work connection registered
Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [proxy/tcp.go:82] [1c78543bf280f879] [DDNS-GO] tcp proxy listen port [9876]
Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [server/control.go:399] [1c78543bf280f879] new proxy [DDNS-GO] type [tcp] success
Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [proxy/tcp.go:82] [1c78543bf280f879] [iStore后台] tcp proxy listen port [9880]
Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [server/control.go:399] [1c78543bf280f879] new proxy [iStore后台] type [tcp] success
Jun 13 06:04:53 arm frps[1557311]: 2025-06-13 06:04:53.209 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:05:23 arm frps[1557311]: 2025-06-13 06:05:23.229 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:05:53 arm frps[1557311]: 2025-06-13 06:05:53.229 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:06:23 arm frps[1557311]: 2025-06-13 06:06:23.205 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:06:53 arm frps[1557311]: 2025-06-13 06:06:53.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:07:23 arm frps[1557311]: 2025-06-13 06:07:23.218 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:07:53 arm frps[1557311]: 2025-06-13 06:07:53.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:08:23 arm frps[1557311]: 2025-06-13 06:08:23.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:08:53 arm frps[1557311]: 2025-06-13 06:08:53.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat
Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.799 [D] [server/service.go:531] accept new mux stream error: keepalive timeout
Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.800 [I] [proxy/proxy.go:115] [1c78543bf280f879] [DDNS-GO] proxy closing
Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.801 [W] [proxy/proxy.go:201] [1c78543bf280f879] [DDNS-GO] listener is closed: accept tcp [::]:9876: use of closed network connection
Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.802 [I] [proxy/proxy.go:115] [1c78543bf280f879] [iStore后台] proxy closing
Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.802 [W] [proxy/proxy.go:201] [1c78543bf280f879] [iStore后台] listener is closed: accept tcp [::]:9880: use of closed network connection
Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.802 [I] [server/control.go:357] [1c78543bf280f879] client exit success
<!-- gh-comment-id:2968457499 --> @ssyangchn commented on GitHub (Jun 12, 2025): 同样几分钟就断开 ``` Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.125 [I] [server/service.go:582] [1c78543bf280f879] client login info: ip [xxx.xxx.xx.xx:6427] version [0.48.0] hostname [] os [linux] arch [arm64] Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.203 [D] [server/control.go:243] [1c78543bf280f879] new work connection registered Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [proxy/tcp.go:82] [1c78543bf280f879] [DDNS-GO] tcp proxy listen port [9876] Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [server/control.go:399] [1c78543bf280f879] new proxy [DDNS-GO] type [tcp] success Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [proxy/tcp.go:82] [1c78543bf280f879] [iStore后台] tcp proxy listen port [9880] Jun 13 06:04:23 arm frps[1557311]: 2025-06-13 06:04:23.252 [I] [server/control.go:399] [1c78543bf280f879] new proxy [iStore后台] type [tcp] success Jun 13 06:04:53 arm frps[1557311]: 2025-06-13 06:04:53.209 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:05:23 arm frps[1557311]: 2025-06-13 06:05:23.229 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:05:53 arm frps[1557311]: 2025-06-13 06:05:53.229 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:06:23 arm frps[1557311]: 2025-06-13 06:06:23.205 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:06:53 arm frps[1557311]: 2025-06-13 06:06:53.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:07:23 arm frps[1557311]: 2025-06-13 06:07:23.218 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:07:53 arm frps[1557311]: 2025-06-13 06:07:53.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:08:23 arm frps[1557311]: 2025-06-13 06:08:23.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:08:53 arm frps[1557311]: 2025-06-13 06:08:53.219 [D] [server/control.go:430] [1c78543bf280f879] receive heartbeat Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.799 [D] [server/service.go:531] accept new mux stream error: keepalive timeout Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.800 [I] [proxy/proxy.go:115] [1c78543bf280f879] [DDNS-GO] proxy closing Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.801 [W] [proxy/proxy.go:201] [1c78543bf280f879] [DDNS-GO] listener is closed: accept tcp [::]:9876: use of closed network connection Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.802 [I] [proxy/proxy.go:115] [1c78543bf280f879] [iStore后台] proxy closing Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.802 [W] [proxy/proxy.go:201] [1c78543bf280f879] [iStore后台] listener is closed: accept tcp [::]:9880: use of closed network connection Jun 13 06:09:33 arm frps[1557311]: 2025-06-13 06:09:33.802 [I] [server/control.go:357] [1c78543bf280f879] client exit success ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
new
master
copilot/review-pull-request-5198
v0.68.1
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.1
v0.62.0
v0.61.2
v0.61.1
v0.61.0
v0.60.0
v0.59.0
v0.58.1
v0.58.0
v0.57.0
v0.56.0
v0.55.1
v0.55.0
v0.54.0
v0.53.2
v0.53.1
v0.53.0
v0.52.3
v0.52.2
v0.52.1
v0.52.0
v0.51.3
v0.51.2
v0.51.1
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.1
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.1
v0.39.0
v0.38.0
v0.37.1
v0.37.0
v0.36.2
v0.36.1
v0.36.0
v0.35.1
v0.35.0
v0.34.3
v0.34.2
v0.34.1
v0.34.0
v0.33.0
v0.32.1
v0.32.0
v0.31.2
v0.31.1
v0.31.0
v0.30.0
v0.29.1
v0.29.0
v0.28.2
v0.28.1
v0.28.0
v0.27.1
v0.27.0
v0.26.0
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.1
v0.24.0
v0.23.3
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.1
v0.19.0
v0.18.0
v0.17.0
v0.16.1
v0.16.0
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.1
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
In Progress

   
WIP

   
WaitingForInfo

   
bug

   
doc

   
duplicate

   
easy

   
enhancement

   
future

   
help wanted

   
invalid

   
lifecycle/stale

   
need-issue-template

   
need-usage-help

   
no plan

   
proposal

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
todo
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#3365
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?