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

[GH-ISSUE #992] http代理,每天都要断线一次 #786

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

Originally created by @rovelover on GitHub (Dec 3, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/992

frps,frpc 版本号:v0.21.0
frps,frpc都是WIN2008R2服务器.
问题描述:
每天不定时的会无法访问网站,浏览器访问网站,一直在等待响应,重启frpc无效,重启frps即可立刻恢复正常,服务器端是固定ip地址,客户端是拨号宽带有公网IP,故障出现和修复后,客户端IP没有切换过,说明没有被电信ISP断线过.因此应该不是断线重新拨号引起的故障.
以前用老版本v0.13.0和更老的版本,这种情况一般一个星期出现一次.

Configures you used:
frps.ini

[common]
bind_addr = 0.0.0.0
bind_port = 1111
vhost_http_port = 80
vhost_https_port = 443
token = 12345678
log_file = ./log/frps.log
log_level = info
log_max_days = 3

frpc.ini

[common]
server_addr = x.x.x.x
server_port = 1111
token = 12345678
login_fail_exit = false
log_file = ./log/frpc.log
log_level = info
log_max_days = 3

[web80]
type = http
local_ip=127.0.0.1
local_port=81
custom_domains=www.xxx.com

[web443]
type = https
local_ip=127.0.0.1
local_port=1443
custom_domains=a.xxx.com

错误日志如下:
日志已包括最后手动重启frps后成功的日志.

服务器frps端,系统时间比客户端快12秒:

2018/12/03 17:41:12 [I] [proxy.go:87] [9f823203d3876a63] [web80] get a new work connection: [183.154.150.190:55545]
.................省略重复错误行数:200........................................
2018/12/03 17:42:11 [I] [proxy.go:87] [9f823203d3876a63] [web80] get a new work connection: [183.154.150.190:55545]
2018/12/03 17:42:17 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0
2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0
2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0
2018/12/03 17:42:19 [W] [control.go:224] [9f823203d3876a63] write message to control connection error: connection write timeout
2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0
.................省略重复错误行数:10........................................
2018/12/03 17:42:21 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0
2018/12/03 17:42:22 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:8........................................
2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: connection write timeout
.................省略重复错误行数:8........................................
2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: connection write timeout
2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:8........................................
2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: EOF
2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: EOF
2018/12/03 17:42:24 [I] [service.go:319] client login info: ip [183.154.150.190:61214] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:42:24 [I] [control.go:196] [9f823203d3876a63] Replaced by client [9f823203d3876a63]
2018/12/03 17:42:24 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:15.......................................
2018/12/03 17:42:32 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:42:35 [I] [service.go:319] client login info: ip [183.154.150.190:61216] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:42:35 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:42:36 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:15........................................
2018/12/03 17:42:45 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:42:47 [I] [service.go:319] client login info: ip [183.154.150.190:61218] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:42:47 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:42:48 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:5........................................
2018/12/03 17:43:00 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:43:01 [I] [service.go:319] client login info: ip [183.154.150.190:61224] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:43:01 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:43:01 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:5........................................
2018/12/03 17:43:17 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:43:19 [I] [service.go:319] client login info: ip [183.154.150.190:61229] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:43:19 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:43:23 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:10........................................
2018/12/03 17:43:39 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:43:45 [I] [service.go:319] client login info: ip [183.154.150.190:61232] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:43:45 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:43:51 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:10........................................
2018/12/03 17:44:08 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:44:15 [I] [service.go:319] client login info: ip [183.154.150.190:61236] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:44:15 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:44:15 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:15........................................
2018/12/03 17:44:44 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:44:45 [I] [service.go:319] client login info: ip [183.154.150.190:61243] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:44:45 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:44:45 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:15........................................
2018/12/03 17:45:12 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:45:15 [I] [service.go:319] client login info: ip [183.154.150.190:61247] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:45:15 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:45:18 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:15........................................
2018/12/03 17:45:42 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:45:45 [I] [service.go:319] client login info: ip [183.154.150.190:61254] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:45:45 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:45:51 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:20........................................
2018/12/03 17:46:15 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:46:15 [I] [service.go:319] client login info: ip [183.154.150.190:61292] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:46:15 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:46:15 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:46:17 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:46:19 [W] [newhttp.go:209] http: proxy error: no such domain
2018/12/03 17:46:19 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:20........................................
2018/12/03 17:46:44 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:46:45 [I] [service.go:319] client login info: ip [183.154.150.190:61298] version [0.21.0] hostname [] os [windows] arch [amd64]
2018/12/03 17:46:45 [I] [control.go:196] Replaced by client [9f823203d3876a63]
2018/12/03 17:46:46 [W] [newhttp.go:209] http: proxy error: context canceled
.................省略重复错误行数:30........................................
2018/12/03 17:47:11 [W] [newhttp.go:209] http: proxy error: context canceled
2018/12/03 17:47:20 [I] [service.go:130] frps tcp listen on 0.0.0.0:8888
2018/12/03 17:47:20 [I] [service.go:172] http service listen on 0.0.0.0:80
2018/12/03 17:47:20 [I] [service.go:193] https service listen on 0.0.0.0:443
2018/12/03 17:47:20 [I] [root.go:207] Start frps success

客户端frpc的错误日志:

2018/12/03 17:41:53 [E] [control.go:152] [9f823203d3876a63] work connection closed, EOF
.................省略重复错误行数:30........................................
2018/12/03 17:42:21 [E] [control.go:152] [9f823203d3876a63] work connection closed, EOF
2018/12/03 17:42:21 [I] [control.go:308] [9f823203d3876a63] control writer is closing
2018/12/03 17:42:21 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:42:21 [W] [control.go:255] [9f823203d3876a63] start new connection to server error: session shutdown
.................省略重复错误行数:10........................................
2018/12/03 17:42:21 [W] [control.go:255] [9f823203d3876a63] start new connection to server error: session shutdown
2018/12/03 17:42:31 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:42:32 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:42:42 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:42:44 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:42:54 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:42:58 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:43:08 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:43:16 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:43:26 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:43:42 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:43:52 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:44:12 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:44:22 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:44:42 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:44:53 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:45:13 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:45:23 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:45:43 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:45:53 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:46:13 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:46:23 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:46:43 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:46:53 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached
2018/12/03 17:47:13 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:47:14 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: dial tcp 47.99.58.218:8888: connectex: No connection could be made because the target machine actively refused it.
2018/12/03 17:47:34 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server...
2018/12/03 17:47:34 [I] [control.go:246] [9f823203d3876a63] login to server success, get run id [9f823203d3876a63], server udp port [0]
2018/12/03 17:47:34 [I] [control.go:169] [9f823203d3876a63] [web443] start proxy success
2018/12/03 17:47:34 [I] [control.go:169] [9f823203d3876a63] [web80] start proxy success

Originally created by @rovelover on GitHub (Dec 3, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/992 frps,frpc 版本号:v0.21.0 frps,frpc都是WIN2008R2服务器. 问题描述: 每天不定时的会无法访问网站,浏览器访问网站,一直在等待响应,重启frpc无效,重启frps即可立刻恢复正常,服务器端是固定ip地址,客户端是拨号宽带有公网IP,故障出现和修复后,客户端IP没有切换过,说明没有被电信ISP断线过.因此应该不是断线重新拨号引起的故障. 以前用老版本v0.13.0和更老的版本,这种情况一般一个星期出现一次. **Configures you used:** frps.ini > [common] bind_addr = 0.0.0.0 bind_port = 1111 vhost_http_port = 80 vhost_https_port = 443 token = 12345678 log_file = ./log/frps.log log_level = info log_max_days = 3 frpc.ini > [common] server_addr = x.x.x.x server_port = 1111 token = 12345678 login_fail_exit = false log_file = ./log/frpc.log log_level = info log_max_days = 3 > [web80] type = http local_ip=127.0.0.1 local_port=81 custom_domains=www.xxx.com > [web443] type = https local_ip=127.0.0.1 local_port=1443 custom_domains=a.xxx.com 错误日志如下: 日志已包括最后手动重启frps后成功的日志. 服务器frps端,系统时间比客户端快12秒: > 2018/12/03 17:41:12 [I] [proxy.go:87] [9f823203d3876a63] [web80] get a new work connection: [183.154.150.190:55545] .................省略重复错误行数:200........................................ 2018/12/03 17:42:11 [I] [proxy.go:87] [9f823203d3876a63] [web80] get a new work connection: [183.154.150.190:55545] 2018/12/03 17:42:17 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0 2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0 2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0 2018/12/03 17:42:19 [W] [control.go:224] [9f823203d3876a63] write message to control connection error: connection write timeout 2018/12/03 17:42:19 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0 .................省略重复错误行数:10........................................ 2018/12/03 17:42:21 [W] [proxy.go:94] [web80] failed to send message to work connection from pool: connection write timeout, times: 0 2018/12/03 17:42:22 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:8........................................ 2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: connection write timeout .................省略重复错误行数:8........................................ 2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: connection write timeout 2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:8........................................ 2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: EOF 2018/12/03 17:42:23 [W] [newhttp.go:209] http: proxy error: EOF 2018/12/03 17:42:24 [I] [service.go:319] client login info: ip [183.154.150.190:61214] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:42:24 [I] [control.go:196] [9f823203d3876a63] Replaced by client [9f823203d3876a63] 2018/12/03 17:42:24 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:15....................................... 2018/12/03 17:42:32 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:42:35 [I] [service.go:319] client login info: ip [183.154.150.190:61216] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:42:35 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:42:36 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:15........................................ 2018/12/03 17:42:45 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:42:47 [I] [service.go:319] client login info: ip [183.154.150.190:61218] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:42:47 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:42:48 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:5........................................ 2018/12/03 17:43:00 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:43:01 [I] [service.go:319] client login info: ip [183.154.150.190:61224] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:43:01 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:43:01 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:5........................................ 2018/12/03 17:43:17 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:43:19 [I] [service.go:319] client login info: ip [183.154.150.190:61229] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:43:19 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:43:23 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:10........................................ 2018/12/03 17:43:39 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:43:45 [I] [service.go:319] client login info: ip [183.154.150.190:61232] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:43:45 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:43:51 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:10........................................ 2018/12/03 17:44:08 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:44:15 [I] [service.go:319] client login info: ip [183.154.150.190:61236] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:44:15 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:44:15 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:15........................................ 2018/12/03 17:44:44 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:44:45 [I] [service.go:319] client login info: ip [183.154.150.190:61243] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:44:45 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:44:45 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:15........................................ 2018/12/03 17:45:12 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:45:15 [I] [service.go:319] client login info: ip [183.154.150.190:61247] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:45:15 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:45:18 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:15........................................ 2018/12/03 17:45:42 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:45:45 [I] [service.go:319] client login info: ip [183.154.150.190:61254] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:45:45 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:45:51 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:20........................................ 2018/12/03 17:46:15 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:46:15 [I] [service.go:319] client login info: ip [183.154.150.190:61292] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:46:15 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:46:15 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:46:17 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:46:19 [W] [newhttp.go:209] http: proxy error: no such domain 2018/12/03 17:46:19 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:20........................................ 2018/12/03 17:46:44 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:46:45 [I] [service.go:319] client login info: ip [183.154.150.190:61298] version [0.21.0] hostname [] os [windows] arch [amd64] 2018/12/03 17:46:45 [I] [control.go:196] Replaced by client [9f823203d3876a63] 2018/12/03 17:46:46 [W] [newhttp.go:209] http: proxy error: context canceled .................省略重复错误行数:30........................................ 2018/12/03 17:47:11 [W] [newhttp.go:209] http: proxy error: context canceled 2018/12/03 17:47:20 [I] [service.go:130] frps tcp listen on 0.0.0.0:8888 2018/12/03 17:47:20 [I] [service.go:172] http service listen on 0.0.0.0:80 2018/12/03 17:47:20 [I] [service.go:193] https service listen on 0.0.0.0:443 2018/12/03 17:47:20 [I] [root.go:207] Start frps success 客户端frpc的错误日志: > 2018/12/03 17:41:53 [E] [control.go:152] [9f823203d3876a63] work connection closed, EOF .................省略重复错误行数:30........................................ 2018/12/03 17:42:21 [E] [control.go:152] [9f823203d3876a63] work connection closed, EOF 2018/12/03 17:42:21 [I] [control.go:308] [9f823203d3876a63] control writer is closing 2018/12/03 17:42:21 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:42:21 [W] [control.go:255] [9f823203d3876a63] start new connection to server error: session shutdown .................省略重复错误行数:10........................................ 2018/12/03 17:42:21 [W] [control.go:255] [9f823203d3876a63] start new connection to server error: session shutdown 2018/12/03 17:42:31 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:42:32 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:42:42 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:42:44 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:42:54 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:42:58 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:43:08 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:43:16 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:43:26 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:43:42 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:43:52 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:44:12 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:44:22 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:44:42 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:44:53 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:45:13 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:45:23 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:45:43 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:45:53 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:46:13 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:46:23 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:46:43 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:46:53 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: i/o deadline reached 2018/12/03 17:47:13 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:47:14 [W] [control.go:410] [9f823203d3876a63] reconnect to server error: dial tcp 47.99.58.218:8888: connectex: No connection could be made because the target machine actively refused it. 2018/12/03 17:47:34 [I] [control.go:407] [9f823203d3876a63] try to reconnect to server... 2018/12/03 17:47:34 [I] [control.go:246] [9f823203d3876a63] login to server success, get run id [9f823203d3876a63], server udp port [0] 2018/12/03 17:47:34 [I] [control.go:169] [9f823203d3876a63] [web443] start proxy success 2018/12/03 17:47:34 [I] [control.go:169] [9f823203d3876a63] [web80] start proxy success
gitea-mirror 2026-05-05 12:30:08 -06:00
gitea-mirror commented 2026-05-05 12:30:11 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Dec 8, 2018):

日志显示错误是网络问题，具体原因还需要自行排查下。

<!-- gh-comment-id:445448109 --> @fatedier commented on GitHub (Dec 8, 2018): 日志显示错误是网络问题，具体原因还需要自行排查下。
gitea-mirror commented 2026-05-05 12:30:12 -06:00
Author
Owner
Copy link

@SeanDemo2017 commented on GitHub (Dec 8, 2018):

排除各自启是否有问题，还有是否是frps使用了断线不再连线的的选项 肖黎东（守护星） 邮箱：xiao940213@gmail.com 签名由 网易邮箱大师 定制 在2018年12月08日 18:12，fatedier 写道： 日志显示错误是网络问题，具体原因还需要自行排查下。 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

<!-- gh-comment-id:445448349 --> @SeanDemo2017 commented on GitHub (Dec 8, 2018): 排除各自启是否有问题，还有是否是frps使用了断线不再连线的的选项 肖黎东（守护星） 邮箱：xiao940213@gmail.com 签名由 网易邮箱大师 定制 在2018年12月08日 18:12，fatedier 写道： 日志显示错误是网络问题，具体原因还需要自行排查下。 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
gitea-mirror commented 2026-05-05 12:30:13 -06:00
Author
Owner
Copy link

@rovelover commented on GitHub (Dec 12, 2018):

这几天观察每次卡死的原因.发现每次网站打不开的时候,阿里云的服务器流量监控显示流量比平时大,因此,怀疑是并发链接过多导致的,已有提交的相似问题:-------访问量比较大的时候丢包比较严重: #457

<!-- gh-comment-id:446448266 --> @rovelover commented on GitHub (Dec 12, 2018): 这几天观察每次卡死的原因.发现每次网站打不开的时候,阿里云的服务器流量监控显示流量比平时大,因此,怀疑是并发链接过多导致的,已有提交的相似问题:-------访问量比较大的时候丢包比较严重: #457
gitea-mirror commented 2026-05-05 12:30:14 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Dec 12, 2018):

你需要借助工具，自行排查下相关的环境，也可以多调试，测试验证。
或者提供能稳定本地复现的配置。
依据你的描述，还没有办法解决任何问题。

<!-- gh-comment-id:446450207 --> @fatedier commented on GitHub (Dec 12, 2018): 你需要借助工具，自行排查下相关的环境，也可以多调试，测试验证。 或者提供能稳定本地复现的配置。 依据你的描述，还没有办法解决任何问题。
gitea-mirror commented 2026-05-05 12:30:15 -06:00
Author
Owner
Copy link

@f8q8 commented on GitHub (Jan 24, 2019):

我也遇到每天断线一次的问题。22的版本，我是在家里放了一个台式机作为生产环境的备份，每一个小时备份一次数据库，备份文件传输大约需要40分钟的时间，每天13:00的备份都是失败的。其他时间，都是正常的。13:00，服务器上的备份文件是正常的，我用的是rsync来拷贝

<!-- gh-comment-id:457036165 --> @f8q8 commented on GitHub (Jan 24, 2019): 我也遇到每天断线一次的问题。22的版本，我是在家里放了一个台式机作为生产环境的备份，每一个小时备份一次数据库，备份文件传输大约需要40分钟的时间，每天13:00的备份都是失败的。其他时间，都是正常的。13:00，服务器上的备份文件是正常的，我用的是rsync来拷贝
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#786
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?