[GH-ISSUE #4916] 0.63似乎有奇怪的bug,会周期性断开 #3878

Closed
opened 2026-05-05 14:28:41 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @BoysheO on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4916

Bug Description

我使用podman部署,通过frpc将内部端口在远程服务器暴露出来。然后现在发现会周期性断开。
远程服务器使用docker部署,宿主机器Ubuntu22.04.4;客户端使用podman部署,宿主机器MacM4

frpc Version

0.63

frps Version

0.63

System Architecture

linux/x86

Configurations

frps配置如下:

bindPort = 7000

[auth]
method = "token"
token  = "<token>"

[transport]
tcpMux = false

frpc配置如下:

serverAddr = "<serverip>"
serverPort = 7000
[auth]
method = "token"
token = "<token>"

[transport]
tcpMux = false
[[proxies]]
name = "harbor"
type = "tcp"
localIP = "127.0.0.1"
localPort = 8080
remotePort = 7005

Logs

2025-08-08 05:08:26.611 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:43412]
2025-08-08 05:08:31.466 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:33194]
2025-08-08 05:08:31.466 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:33202]
2025-08-08 05:20:25.111 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:40602]
2025-08-08 05:20:25.111 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10648: write: broken pipe, times: 0
2025-08-08 05:20:25.111 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10674: write: broken pipe, times: 1
2025-08-08 05:20:30.726 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:41712]
2025-08-08 05:20:30.726 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10673: write: broken pipe, times: 0
2025-08-08 05:20:30.726 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10050: write: broken pipe, times: 1
2025-08-08 05:20:35.105 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:41726]
2025-08-08 05:20:35.105 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10051: write: broken pipe, times: 0
2025-08-08 05:20:35.105 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10059: write: broken pipe, times: 1

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 @BoysheO on GitHub (Aug 8, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4916 ### Bug Description 我使用podman部署,通过frpc将内部端口在远程服务器暴露出来。然后现在发现会周期性断开。 远程服务器使用docker部署,宿主机器Ubuntu22.04.4;客户端使用podman部署,宿主机器MacM4 ### frpc Version 0.63 ### frps Version 0.63 ### System Architecture linux/x86 ### Configurations frps配置如下: ```toml bindPort = 7000 [auth] method = "token" token = "<token>" [transport] tcpMux = false ``` frpc配置如下: ```toml serverAddr = "<serverip>" serverPort = 7000 [auth] method = "token" token = "<token>" [transport] tcpMux = false [[proxies]] name = "harbor" type = "tcp" localIP = "127.0.0.1" localPort = 8080 remotePort = 7005 ``` ### Logs 2025-08-08 05:08:26.611 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:43412] 2025-08-08 05:08:31.466 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:33194] 2025-08-08 05:08:31.466 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:33202] 2025-08-08 05:20:25.111 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:40602] 2025-08-08 05:20:25.111 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10648: write: broken pipe, times: 0 2025-08-08 05:20:25.111 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10674: write: broken pipe, times: 1 2025-08-08 05:20:30.726 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:41712] 2025-08-08 05:20:30.726 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10673: write: broken pipe, times: 0 2025-08-08 05:20:30.726 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10050: write: broken pipe, times: 1 2025-08-08 05:20:35.105 [I] [proxy/proxy.go:204] [cc6320986c2ed6a5] [harbor] get a user connection [172.17.0.1:41726] 2025-08-08 05:20:35.105 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10051: write: broken pipe, times: 0 2025-08-08 05:20:35.105 [W] [proxy/proxy.go:161] [cc6320986c2ed6a5] [harbor] failed to send message to work connection from pool: write tcp 172.17.0.2:7000->114.86.43.186:10059: write: broken pipe, times: 1 ### 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
Author
Owner

@BoysheO commented on GitHub (Aug 8, 2025):

可能是因为我本地机器挂了vpn的问题,不确定,后面测试下

<!-- gh-comment-id:3167450179 --> @BoysheO commented on GitHub (Aug 8, 2025): 可能是因为我本地机器挂了vpn的问题,不确定,后面测试下
Author
Owner

@liuguoping1024 commented on GitHub (Aug 9, 2025):

我也碰到同样的问题了, 用了一段时间之后,就离线了。对方的网络肯定没有问题

Image
<!-- gh-comment-id:3169622275 --> @liuguoping1024 commented on GitHub (Aug 9, 2025): 我也碰到同样的问题了, 用了一段时间之后,就离线了。对方的网络肯定没有问题 <img width="1530" height="717" alt="Image" src="https://github.com/user-attachments/assets/a0e3493b-a511-4353-bc16-836242065995" />
Author
Owner

@BoysheO commented on GitHub (Aug 9, 2025):

停用vpn一日,周期性断网的情况消失了。我的问题可以确认是vpn导致的

<!-- gh-comment-id:3172038107 --> @BoysheO commented on GitHub (Aug 9, 2025): 停用vpn一日,周期性断网的情况消失了。我的问题可以确认是vpn导致的
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#3878
No description provided.