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 #1307] 隔一段时间会自动掉线，不知道为什么，求大神指导。。。。 #1038

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

Originally created by @seklure on GitHub (Jul 6, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1307

2019/06/20 13:04:51 [I] [control.go:246] [86a0362b4732b036] login to server success, get run id [86a0362b4732b036], server udp port [7001]
2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_0] start proxy success
2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_1] start proxy success
2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_2] start proxy success
2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_3] start proxy success
2019/06/20 13:05:31 [I] [control.go:308] [86a0362b4732b036] control writer is closing
2019/06/20 13:05:31 [I] [control.go:407] [86a0362b4732b036] try to reconnect to server...
2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF
2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF
2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF
2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF
2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF

Originally created by @seklure on GitHub (Jul 6, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1307 2019/06/20 13:04:51 [I] [control.go:246] [86a0362b4732b036] login to server success, get run id [86a0362b4732b036], server udp port [7001] 2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_0] start proxy success 2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_1] start proxy success 2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_2] start proxy success 2019/06/20 13:04:51 [I] [control.go:169] [86a0362b4732b036] [tcp_port1_3] start proxy success 2019/06/20 13:05:31 [I] [control.go:308] [86a0362b4732b036] control writer is closing 2019/06/20 13:05:31 [I] [control.go:407] [86a0362b4732b036] try to reconnect to server... 2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF 2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF 2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF 2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF 2019/06/20 13:05:31 [E] [control.go:152] [86a0362b4732b036] work connection closed, EOF
gitea-mirror commented 2026-05-05 12:40:03 -06:00
Author
Owner
Copy link

@vritser commented on GitHub (Jul 8, 2019):

看日志是 frps 挂掉了， 可以起个daemon，或者使用docker image: https://hub.docker.com/r/vritser/frps

<!-- gh-comment-id:509148765 --> @vritser commented on GitHub (Jul 8, 2019): 看日志是 frps 挂掉了， 可以起个daemon，或者使用docker image: https://hub.docker.com/r/vritser/frps
gitea-mirror commented 2026-05-05 12:40:04 -06:00
Author
Owner
Copy link

@seklure commented on GitHub (Jul 8, 2019):

看日志是 frps 挂掉了， 可以起个daemon，或者使用docker image: https://hub.docker.com/r/vritser/frps

之前用的是kcp协议，后来非常不稳定就用了tcp，稍微好点了，但是看日志记录，还是存在这个问题。我之前用的是docker，现在改成了官方命令启动了，还在观察中。。。。

<!-- gh-comment-id:509155798 --> @seklure commented on GitHub (Jul 8, 2019): > 看日志是 frps 挂掉了， 可以起个daemon，或者使用docker image: https://hub.docker.com/r/vritser/frps 之前用的是kcp协议，后来非常不稳定就用了tcp，稍微好点了，但是看日志记录，还是存在这个问题。我之前用的是docker，现在改成了官方命令启动了，还在观察中。。。。
gitea-mirror commented 2026-05-05 12:40:05 -06:00
Author
Owner
Copy link

@wwqgtxx commented on GitHub (Jul 11, 2019):

在我的移动宽带下出现过类似情况，将配置文件中的启用加密打开之后就稳定了，而在电信宽带下就无该问题，具体原因不明

<!-- gh-comment-id:510290077 --> @wwqgtxx commented on GitHub (Jul 11, 2019): 在我的移动宽带下出现过类似情况，将配置文件中的启用加密打开之后就稳定了，而在电信宽带下就无该问题，具体原因不明
gitea-mirror commented 2026-05-05 12:40:05 -06:00
Author
Owner
Copy link

@seklure commented on GitHub (Jul 11, 2019):

在我的移动宽带下出现过类似情况，将配置文件中的启用加密打开之后就稳定了，而在电信宽带下就无该问题，具体原因不明

我的就是在移动快带下出现这个情况的，加密也启用了但是还是很不稳定！

<!-- gh-comment-id:510381037 --> @seklure commented on GitHub (Jul 11, 2019): > 在我的移动宽带下出现过类似情况，将配置文件中的启用加密打开之后就稳定了，而在电信宽带下就无该问题，具体原因不明 我的就是在移动快带下出现这个情况的，加密也启用了但是还是很不稳定！
gitea-mirror commented 2026-05-05 12:40:06 -06:00
Author
Owner
Copy link

@seklure commented on GitHub (Jul 11, 2019):

@fatedier 观察了一段时间，目前还是会出现掉线不稳定的情况，能够优化做个类似ping的探测之类模块，能够解决中间网络传输问题？

<!-- gh-comment-id:510384708 --> @seklure commented on GitHub (Jul 11, 2019): @fatedier 观察了一段时间，目前还是会出现掉线不稳定的情况，能够优化做个类似ping的探测之类模块，能够解决中间网络传输问题？
gitea-mirror commented 2026-05-05 12:40:07 -06:00
Author
Owner
Copy link

@seklure commented on GitHub (Jul 11, 2019):

@fatedier
2019/07/11 08:26:56 [I] [control.go:274] [112383f4b813a6fe] control writer is closing
2019/07/11 08:26:56 [I] [proxy.go:69] [112383f4b813a6fe] [tcp_port5_0] proxy closing
2019/07/11 08:26:56 [I] [proxy.go:135] [112383f4b813a6fe] [tcp_port5_0] listener is closed
2019/07/11 08:26:56 [I] [control.go:350] [112383f4b813a6fe] client exit success
2019/07/11 08:27:00 [I] [control.go:274] [bb5a05a01597f29e] control writer is closing
2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_1] proxy closing
2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_1] listener is closed
2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_2] proxy closing
2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_2] listener is closed
2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_3] proxy closing
2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_3] listener is closed
2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_0] proxy closing
2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_0] listener is closed
2019/07/11 08:27:00 [I] [control.go:350] [bb5a05a01597f29e] client exit success
2019/07/11 08:27:06 [I] [control.go:274] [43f670e0cbb041a3] control writer is closing
2019/07/11 08:27:06 [I] [proxy.go:69] [43f670e0cbb041a3] [tcp_port6_0] proxy closing
2019/07/11 08:27:06 [I] [proxy.go:135] [43f670e0cbb041a3] [tcp_port6_0] listener is closed
2019/07/11 08:27:06 [I] [control.go:350] [43f670e0cbb041a3] client exit success

<!-- gh-comment-id:510385388 --> @seklure commented on GitHub (Jul 11, 2019): @fatedier 2019/07/11 08:26:56 [I] [control.go:274] [112383f4b813a6fe] control writer is closing 2019/07/11 08:26:56 [I] [proxy.go:69] [112383f4b813a6fe] [tcp_port5_0] proxy closing 2019/07/11 08:26:56 [I] [proxy.go:135] [112383f4b813a6fe] [tcp_port5_0] listener is closed 2019/07/11 08:26:56 [I] [control.go:350] [112383f4b813a6fe] client exit success 2019/07/11 08:27:00 [I] [control.go:274] [bb5a05a01597f29e] control writer is closing 2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_1] proxy closing 2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_1] listener is closed 2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_2] proxy closing 2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_2] listener is closed 2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_3] proxy closing 2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_3] listener is closed 2019/07/11 08:27:00 [I] [proxy.go:69] [bb5a05a01597f29e] [tcp_port1_0] proxy closing 2019/07/11 08:27:00 [I] [proxy.go:135] [bb5a05a01597f29e] [tcp_port1_0] listener is closed 2019/07/11 08:27:00 [I] [control.go:350] [bb5a05a01597f29e] client exit success 2019/07/11 08:27:06 [I] [control.go:274] [43f670e0cbb041a3] control writer is closing 2019/07/11 08:27:06 [I] [proxy.go:69] [43f670e0cbb041a3] [tcp_port6_0] proxy closing 2019/07/11 08:27:06 [I] [proxy.go:135] [43f670e0cbb041a3] [tcp_port6_0] listener is closed 2019/07/11 08:27:06 [I] [control.go:350] [43f670e0cbb041a3] client exit success
gitea-mirror commented 2026-05-05 12:40:07 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Jul 11, 2019):

网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。

另外，试试 protocol = websocket，如果不行就不行了，不用再继续在这里提了。

<!-- gh-comment-id:510388297 --> @fatedier commented on GitHub (Jul 11, 2019): 网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。 另外，试试 `protocol = websocket`，如果不行就不行了，不用再继续在这里提了。
gitea-mirror commented 2026-05-05 12:40:09 -06:00
Author
Owner
Copy link

@seklure commented on GitHub (Jul 11, 2019):

网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。

另外，试试 protocol = websocket，如果不行就不行了，不用再继续在这里提了。

好的，我再试试，感谢！！

<!-- gh-comment-id:510392729 --> @seklure commented on GitHub (Jul 11, 2019): > 网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。 > > 另外，试试 `protocol = websocket`，如果不行就不行了，不用再继续在这里提了。 好的，我再试试，感谢！！
gitea-mirror commented 2026-05-05 12:40:09 -06:00
Author
Owner
Copy link

@seklure commented on GitHub (Jul 11, 2019):

网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。

另外，试试 protocol = websocket，如果不行就不行了，不用再继续在这里提了。

@fatedier 大神，想咨询一下，FRP自带的有重连机制吗？如果发生断开多久会重连？这个重连机制时间是否能够修改？如何修改？

<!-- gh-comment-id:510450040 --> @seklure commented on GitHub (Jul 11, 2019): > 网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。 > > 另外，试试 `protocol = websocket`，如果不行就不行了，不用再继续在这里提了。 @fatedier 大神，想咨询一下，FRP自带的有重连机制吗？如果发生断开多久会重连？这个重连机制时间是否能够修改？如何修改？
gitea-mirror commented 2026-05-05 12:40:10 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Jul 11, 2019):

有，可以搜以前的 issue。

<!-- gh-comment-id:510452926 --> @fatedier commented on GitHub (Jul 11, 2019): 有，可以搜以前的 issue。
gitea-mirror commented 2026-05-05 12:40:11 -06:00
Author
Owner
Copy link

@seklure commented on GitHub (Jul 13, 2019):

有，可以搜以前的 issue。

@fatedier 大神，我收了一下貌似没看到有类似重连机制的设置？下面是调整为websocket之后也报错。有方法排查是什么原因吗？
2019/07/13 09:45:59 [I] [control.go:274] [0d181298512fc597] control writer is closing
2019/07/13 09:45:59 [I] [proxy.go:69] [0d181298512fc597] [tcp_port5_0] proxy closing
2019/07/13 09:45:59 [I] [proxy.go:135] [0d181298512fc597] [tcp_port5_0] listener is closed
2019/07/13 09:45:59 [I] [control.go:350] [0d181298512fc597] client exit success
2019/07/13 09:46:11 [I] [control.go:274] [d2a78885c18c7bab] control writer is closing
2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_0] proxy closing
2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_0] listener is closed
2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_1] proxy closing
2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_1] listener is closed
2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_2] proxy closing
2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_2] listener is closed
2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_3] proxy closing
2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_3] listener is closed
2019/07/13 09:46:11 [I] [control.go:350] [d2a78885c18c7bab] client exit success
2019/07/13 09:46:12 [I] [control.go:274] [d5b81d54e6513e73] control writer is closing
2019/07/13 09:46:12 [I] [proxy.go:69] [d5b81d54e6513e73] [tcp_port6_0] proxy closing
2019/07/13 09:46:12 [I] [proxy.go:135] [d5b81d54e6513e73] [tcp_port6_0] listener is closed
2019/07/13 09:46:12 [I] [control.go:350] [d5b81d54e6513e73] client exit success

<!-- gh-comment-id:511104932 --> @seklure commented on GitHub (Jul 13, 2019): > 有，可以搜以前的 issue。 @fatedier 大神，我收了一下貌似没看到有类似重连机制的设置？下面是调整为websocket之后也报错。有方法排查是什么原因吗？ 2019/07/13 09:45:59 [I] [control.go:274] [0d181298512fc597] control writer is closing 2019/07/13 09:45:59 [I] [proxy.go:69] [0d181298512fc597] [tcp_port5_0] proxy closing 2019/07/13 09:45:59 [I] [proxy.go:135] [0d181298512fc597] [tcp_port5_0] listener is closed 2019/07/13 09:45:59 [I] [control.go:350] [0d181298512fc597] client exit success 2019/07/13 09:46:11 [I] [control.go:274] [d2a78885c18c7bab] control writer is closing 2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_0] proxy closing 2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_0] listener is closed 2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_1] proxy closing 2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_1] listener is closed 2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_2] proxy closing 2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_2] listener is closed 2019/07/13 09:46:11 [I] [proxy.go:69] [d2a78885c18c7bab] [tcp_port1_3] proxy closing 2019/07/13 09:46:11 [I] [proxy.go:135] [d2a78885c18c7bab] [tcp_port1_3] listener is closed 2019/07/13 09:46:11 [I] [control.go:350] [d2a78885c18c7bab] client exit success 2019/07/13 09:46:12 [I] [control.go:274] [d5b81d54e6513e73] control writer is closing 2019/07/13 09:46:12 [I] [proxy.go:69] [d5b81d54e6513e73] [tcp_port6_0] proxy closing 2019/07/13 09:46:12 [I] [proxy.go:135] [d5b81d54e6513e73] [tcp_port6_0] listener is closed 2019/07/13 09:46:12 [I] [control.go:350] [d5b81d54e6513e73] client exit success
gitea-mirror commented 2026-05-05 12:40:12 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Jul 14, 2019):

建议更换其他宽带，或自行研究其他中间加密方案，环境问题还是请自行解决。

<!-- gh-comment-id:511168932 --> @fatedier commented on GitHub (Jul 14, 2019): 建议更换其他宽带，或自行研究其他中间加密方案，环境问题还是请自行解决。
gitea-mirror commented 2026-05-05 12:40:12 -06:00
Author
Owner
Copy link

@wwqgtxx commented on GitHub (Jul 14, 2019):

网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。

另外，试试 protocol = websocket，如果不行就不行了，不用再继续在这里提了。

提个问题，这里写了支持websocket协议，那么请问目前的版本支持wss么，能否使用nginx进行基于vhost的proxy_pass呢，这样可能可以看起来更像普通的https流量吧

<!-- gh-comment-id:511172685 --> @wwqgtxx commented on GitHub (Jul 14, 2019): > 网络问题还是自行想其他解决方案，每个项目都有自己的侧重点，可以尝试结合其他项目解决。 > > 另外，试试 `protocol = websocket`，如果不行就不行了，不用再继续在这里提了。 提个问题，这里写了支持`websocket`协议，那么请问目前的版本支持`wss`么，能否使用`nginx`进行基于`vhost`的`proxy_pass`呢，这样可能可以看起来更像普通的https流量吧
gitea-mirror commented 2026-05-05 12:40:13 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Jul 14, 2019):

@wwqgtxx 直接测试一下不就知道了？

<!-- gh-comment-id:511176459 --> @fatedier commented on GitHub (Jul 14, 2019): @wwqgtxx 直接测试一下不就知道了？
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#1038
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?