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 #1178] 公司电脑启用客户端后能连上服务端，但每隔30秒就断开重连，也无法远程接入 #922

New issue
Closed
opened 2026-05-05 12:35:13 -06:00 by gitea-mirror · 7 comments
gitea-mirror commented 2026-05-05 12:35:13 -06:00
Owner
Copy link

Originally created by @wpok on GitHub (Apr 5, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1178

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。)

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?
frp_0.25.3_windows_amd64

What operating system and processor architecture are you using (go env)?
Win10

Configures you used:
[common]
server_addr = x.x.x.x
server_port = 7000

[RDP-corp]
type = tcp
local_ip = 0.0.0.0
local_port = 3389
remote_port = 6000

Steps to reproduce the issue:

  1. 客户端启动后，能正常连接上服务端，服务端的dashboard上也看到该客户端已经online
  2. 看屏幕输出每隔30秒就会提示 control writer is closing，work connection closed, EOF，之后就会重新连接服务端成功，再哥30秒断开重连一直反复
  3. 尝试使用RDP工具远程连接客户端所在机器，可以看到服务端输出提示有新连接进入，但客户端输出一直没有提示有连接进入，还是继续每隔30秒就断开重连
  4. 同样一份客户端配置，在家里的电脑（WIN7）客户端启动后，手机使用4G和RDP工具是可以接入远程的

Describe the results you received:
这是客户端的输出内容：
2019/04/05 09:08:18 [I] [service.go:127] try to reconnect to server...
2019/04/05 09:08:18 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0]
2019/04/05 09:08:18 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp]
2019/04/05 09:08:18 [I] [control.go:144] [RDP-corp] start proxy success
2019/04/05 09:08:48 [I] [control.go:224] control writer is closing
2019/04/05 09:08:48 [E] [control.go:127] work connection closed, EOF
2019/04/05 09:08:48 [I] [service.go:127] try to reconnect to server...
2019/04/05 09:08:48 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0]
2019/04/05 09:08:48 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp]
2019/04/05 09:08:48 [I] [control.go:144] [RDP-corp] start proxy success
2019/04/05 09:09:18 [I] [control.go:224] control writer is closing
2019/04/05 09:09:18 [E] [control.go:127] work connection closed, EOF
2019/04/05 09:09:18 [I] [service.go:127] try to reconnect to server...
2019/04/05 09:09:18 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0]
2019/04/05 09:09:18 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp]
2019/04/05 09:09:18 [I] [control.go:144] [RDP-corp] start proxy success
2019/04/05 09:09:48 [E] [control.go:127] work connection closed, EOF
2019/04/05 09:09:48 [I] [control.go:224] control writer is closing
2019/04/05 09:09:48 [I] [service.go:127] try to reconnect to server...
2019/04/05 09:09:48 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0]
2019/04/05 09:09:48 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp]
2019/04/05 09:09:48 [I] [control.go:144] [RDP-corp] start proxy success
2019/04/05 09:10:18 [E] [control.go:127] work connection closed, EOF
2019/04/05 09:10:18 [I] [control.go:224] control writer is closing
2019/04/05 09:10:36 [I] [service.go:127] try to reconnect to server...
2019/04/05 09:10:36 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0]
2019/04/05 09:10:36 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp]
2019/04/05 09:10:36 [I] [control.go:144] [RDP-corp] start proxy success

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Originally created by @wpok on GitHub (Apr 5, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1178 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。) Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** frp_0.25.3_windows_amd64 **What operating system and processor architecture are you using (`go env`)?** Win10 **Configures you used:** [common] server_addr = x.x.x.x server_port = 7000 [RDP-corp] type = tcp local_ip = 0.0.0.0 local_port = 3389 remote_port = 6000 **Steps to reproduce the issue:** 1. 客户端启动后，能正常连接上服务端，服务端的dashboard上也看到该客户端已经online 2. 看屏幕输出每隔30秒就会提示 control writer is closing，work connection closed, EOF，之后就会重新连接服务端成功，再哥30秒断开重连一直反复 3. 尝试使用RDP工具远程连接客户端所在机器，可以看到服务端输出提示有新连接进入，但客户端输出一直没有提示有连接进入，还是继续每隔30秒就断开重连 4. 同样一份客户端配置，在家里的电脑（WIN7）客户端启动后，手机使用4G和RDP工具是可以接入远程的 **Describe the results you received:** 这是客户端的输出内容： 2019/04/05 09:08:18 [I] [service.go:127] try to reconnect to server... 2019/04/05 09:08:18 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0] 2019/04/05 09:08:18 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp] 2019/04/05 09:08:18 [I] [control.go:144] [RDP-corp] start proxy success 2019/04/05 09:08:48 [I] [control.go:224] control writer is closing 2019/04/05 09:08:48 [E] [control.go:127] work connection closed, EOF 2019/04/05 09:08:48 [I] [service.go:127] try to reconnect to server... 2019/04/05 09:08:48 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0] 2019/04/05 09:08:48 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp] 2019/04/05 09:08:48 [I] [control.go:144] [RDP-corp] start proxy success 2019/04/05 09:09:18 [I] [control.go:224] control writer is closing 2019/04/05 09:09:18 [E] [control.go:127] work connection closed, EOF 2019/04/05 09:09:18 [I] [service.go:127] try to reconnect to server... 2019/04/05 09:09:18 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0] 2019/04/05 09:09:18 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp] 2019/04/05 09:09:18 [I] [control.go:144] [RDP-corp] start proxy success 2019/04/05 09:09:48 [E] [control.go:127] work connection closed, EOF 2019/04/05 09:09:48 [I] [control.go:224] control writer is closing 2019/04/05 09:09:48 [I] [service.go:127] try to reconnect to server... 2019/04/05 09:09:48 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0] 2019/04/05 09:09:48 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp] 2019/04/05 09:09:48 [I] [control.go:144] [RDP-corp] start proxy success 2019/04/05 09:10:18 [E] [control.go:127] work connection closed, EOF 2019/04/05 09:10:18 [I] [control.go:224] control writer is closing 2019/04/05 09:10:36 [I] [service.go:127] try to reconnect to server... 2019/04/05 09:10:36 [I] [service.go:221] login to server success, get run id [0fea65e65c19893c], server udp port [0] 2019/04/05 09:10:36 [I] [proxy_manager.go:137] [0fea65e65c19893c] proxy added: [RDP-corp] 2019/04/05 09:10:36 [I] [control.go:144] [RDP-corp] start proxy success **Describe the results you expected:** **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**
gitea-mirror commented 2026-05-05 12:35:15 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Apr 9, 2019):

可以咨询公司的网络拦截策略。

<!-- gh-comment-id:481067470 --> @fatedier commented on GitHub (Apr 9, 2019): 可以咨询公司的网络拦截策略。
gitea-mirror commented 2026-05-05 12:35:16 -06:00
Author
Owner
Copy link

@LamTech commented on GitHub (Apr 20, 2019):

确实存在这个情况，很高频的。

<!-- gh-comment-id:485054369 --> @LamTech commented on GitHub (Apr 20, 2019): 确实存在这个情况，很高频的。
gitea-mirror commented 2026-05-05 12:35:17 -06:00
Author
Owner
Copy link

@92ewing commented on GitHub (Apr 20, 2019):

我也碰到这个问题 远程桌面反复断开再反复连接

<!-- gh-comment-id:485079331 --> @92ewing commented on GitHub (Apr 20, 2019): 我也碰到这个问题 远程桌面反复断开再反复连接
gitea-mirror commented 2026-05-05 12:35:18 -06:00
Author
Owner
Copy link

@phtwo commented on GitHub (Apr 21, 2019):

我反馈一个相关，不类似的问题

同一个 client 有两个 tcp 的 proxy ，其中一个 ph2_home.rdp 是转发 window 的远程桌面 3389 的，在服务端一直打印下面的日志，但客户端除了偶然网络不好时的重连外，没有对应的日志。奇怪的是，另一个 tcp 的 proxy 不会。

这个蛮夸张的，今天的服务端日志一直有，从客户端连接上后一直输出。回看了最近十天的，也不是一直这样，有几天客户端连接上后没有这些输出的。

...
2019/04/21 07:07:09 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151]
2019/04/21 07:11:17 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151]
2019/04/21 07:11:17 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151]
2019/04/21 07:12:56 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151]
2019/04/21 07:12:56 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151]
...
<!-- gh-comment-id:485224588 --> @phtwo commented on GitHub (Apr 21, 2019): 我反馈一个相关，不类似的问题 同一个 client 有两个 tcp 的 `proxy` ，其中一个 `ph2_home.rdp` 是转发 window 的远程桌面 `3389` 的，在服务端一直打印下面的日志，但客户端除了偶然网络不好时的重连外，没有对应的日志。奇怪的是，另一个 tcp 的 proxy 不会。 这个蛮夸张的，今天的服务端日志一直有，从客户端连接上后一直输出。回看了最近十天的，也不是一直这样，有几天客户端连接上后没有这些输出的。 ``` ... 2019/04/21 07:07:09 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151] 2019/04/21 07:11:17 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151] 2019/04/21 07:11:17 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151] 2019/04/21 07:12:56 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151] 2019/04/21 07:12:56 [I] [proxy.go:82] [91861b77babf1fd7] [ph2_home.rdp] get a new work connection: [x.x.x.x:52151] ... ```
gitea-mirror commented 2026-05-05 12:35:18 -06:00
Author
Owner
Copy link

@yuanxy commented on GitHub (May 5, 2019):

我也遇到这样的情况

<!-- gh-comment-id:489409105 --> @yuanxy commented on GitHub (May 5, 2019): 我也遇到这样的情况
gitea-mirror commented 2026-05-05 12:35:19 -06:00
Author
Owner
Copy link

@reece15 commented on GitHub (May 21, 2019):

我也遇到这样的情况

<!-- gh-comment-id:494356851 --> @reece15 commented on GitHub (May 21, 2019): 我也遇到这样的情况
gitea-mirror commented 2026-05-05 12:35:19 -06:00
Author
Owner
Copy link

@LIUJINGQING commented on GitHub (Aug 2, 2021):

我也是这样的情况，最后发现是我的主机有多个网口。网口启动多个后就会发生这样的情况。之启用一个网口就没有问题。不知道对你们有没有帮助。
目前还不知道有没有什么办法在启用多个网口的情况下解决这个问题。希望有大神指点。

<!-- gh-comment-id:890795700 --> @LIUJINGQING commented on GitHub (Aug 2, 2021): 我也是这样的情况，最后发现是我的主机有多个网口。网口启动多个后就会发生这样的情况。之启用一个网口就没有问题。不知道对你们有没有帮助。 目前还不知道有没有什么办法在启用多个网口的情况下解决这个问题。希望有大神指点。
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#922
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?