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 #1134] reconnect to server error: i/o deadline reached #888

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

Originally created by @doraven on GitHub (Mar 13, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1134

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)?
both 0.25.0

What operating system and processor architecture are you using (go env)?
server: linode, Linux myserver 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

client: Linux myclient 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Configures you used:
server:

[common]
bind_addr = 0.0.0.0
bind_port = 4451
kcp_bind_port = 4451
vhost_http_port = 880
vhost_https_port = 8443

dashboard_addr = 127.0.0.1 
dashboard_port = 1236
dashboard_user = xx
dashboard_pwd = xx

token = xxx

log_file = /home/xxx/sky/code/frps/log/frps.log
log_level = info
log_max_days = 30

max_pool_count = 5

max_ports_per_client = 5

subdomain_host = xxxx

client:

[common]
server_addr = xxxx
server_port = 4451

log_file = /home/xxx/code/frpc/log/frpc.log
log_level = info

log_max_days = 30
token = xxxx
admin_addr = 127.0.0.1
admin_port = 2360
admin_user = admin
admin_passwd = admin
pool_count = 5

tcp_mux = true

user = xxxx

login_fail_exit = false
protocol = kcp

[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 4410
use_encryption = false
use_compression = false
remote_port = 4410
group = xxx
group_key = xxxx

[web01]
type = http
local_ip = 127.0.0.1
local_port = 4000
use_encryption = false
use_compression = false
subdomain = xxxxx

[web02]
type = http
local_ip = 127.0.0.1
local_port = 3990
use_encryption = false
use_compression = true
subdomain = xxxx

And here is the service configure:

server:

[Unit]
Description=Frp Server
After=network.target

[Service]
# User=xxx
ExecStart=/home/xxx/sky/code/frps/frps -c /home/xxx/sky/code/frps/frps.ini

[Install]
WantedBy=multi-user.target

client:

[Unit]
Description=Frp Client
After=network.target

[Service]
User=xxxx
ExecStart=/home/xxx/code/frpc/frpc -c /home/xxxx/code/frpc/frpc.ini

[Install]
WantedBy=multi-user.target

In client, i use my local user for service. And in server, it's sudo.

Steps to reproduce the issue:
It just happened, after about 1h of frp service.

Describe the results you received:

  • server_log:
2019/03/13 14:52:59 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451
2019/03/13 14:52:59 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451
2019/03/13 14:57:25 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451
2019/03/13 14:57:25 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451
2019/03/13 14:59:13 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451
2019/03/13 14:59:13 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451
2019/03/13 15:02:29 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451
2019/03/13 15:02:29 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451
2019/03/13 15:02:30 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451
2019/03/13 15:02:30 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451
2019/03/13 15:02:34 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451
2019/03/13 15:02:34 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451
2019/03/13 15:02:51 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451
2019/03/13 15:02:51 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451
2019/03/13 15:02:51 [I] [service.go:178] http service listen on 0.0.0.0:880
2019/03/13 15:02:51 [I] [service.go:199] https service listen on 0.0.0.0:8443
2019/03/13 15:02:51 [I] [service.go:229] Dashboard listen on 127.0.0.1:1236
2019/03/13 15:02:51 [I] [root.go:204] Start frps success
2019/03/13 15:02:56 [I] [service.go:337] client login info: ip [xx.xx.xx.xx:40590] version [0.25.0] hostname [] os [linux] arch [amd64]
2019/03/13 15:02:56 [I] [tcp.go:48] [a4094ec4e204c729] [xxx.ssh] tcp proxy listen port [4410] in group [xxx]
2019/03/13 15:02:56 [I] [control.go:397] [a4094ec4e204c729] new proxy [xxxxx.ssh] success
2019/03/13 15:02:56 [I] [http.go:85] [a4094ec4e204c729] [xxxxxx.web01] http proxy listen for host [xxxx.xxx.xxx] location []
2019/03/13 15:02:56 [I] [control.go:397] [a4094ec4e204c729] new proxy [xxxxxx.web01] success
2019/03/13 15:02:56 [I] [http.go:85] [a4094ec4e204c729] [xxxxxx.web02] http proxy listen for host [xxxx.xxx.xxx] location []
2019/03/13 15:02:56 [I] [control.go:397] [a4094ec4e204c729] new proxy [xxxxxx.web02] success
2019/03/13 15:11:24 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590]
2019/03/13 15:11:32 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590]
2019/03/13 15:11:32 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590]
2019/03/13 15:11:38 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590]
2019/03/13 15:11:39 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590]
2019/03/13 15:11:44 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590]
2019/03/13 15:11:45 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590]
2019/03/13 15:25:40 [I] [control.go:274] [a4094ec4e204c729] control writer is closing
2019/03/13 15:25:40 [I] [proxy.go:67] [a4094ec4e204c729] [xxxxxx.ssh] proxy closing
2019/03/13 15:25:40 [I] [proxy.go:67] [a4094ec4e204c729] [xxxxxx.web01] proxy closing
2019/03/13 15:25:40 [I] [proxy.go:67] [a4094ec4e204c729] [xxxxxx.web02] proxy closing
2019/03/13 15:25:40 [I] [control.go:349] [a4094ec4e204c729] client exit success
2019/03/13 15:25:40 [I] [proxy.go:112] [a4094ec4e204c729] [xxxxxx.ssh] listener is closed
2019/03/13 15:41:40 [W] [newhttp.go:209] http: proxy error: no such domain
  • client_log:
2019/03/13 14:50:06 [W] [service.go:82] login to server failed: EOF
2019/03/13 14:50:17 [W] [service.go:82] login to server failed: EOF
2019/03/13 14:50:27 [W] [service.go:82] login to server failed: EOF
2019/03/13 14:50:37 [W] [service.go:82] login to server failed: EOF
2019/03/13 14:50:47 [I] [service.go:221] login to server success, get run id [a4094ec4e204c729], server udp port [0]
2019/03/13 14:50:47 [I] [proxy_manager.go:137] [a4094ec4e204c729] proxy added: [xxxxxx.web01 xxxxxx.web02 xxxxxx.ssh]
2019/03/13 14:50:47 [I] [service.go:109] admin server listen on 127.0.0.1:2360
2019/03/13 14:50:48 [I] [control.go:144] [xxxxxx.web01] start proxy success
2019/03/13 14:50:48 [I] [control.go:144] [xxxxxx.web02] start proxy success
2019/03/13 14:50:48 [I] [control.go:144] [xxxxxx.ssh] start proxy success
2019/03/13 14:52:38 [E] [control.go:127] work connection closed, EOF
2019/03/13 14:52:38 [E] [control.go:127] work connection closed, EOF
2019/03/13 14:52:38 [I] [control.go:224] control writer is closing
2019/03/13 14:52:38 [E] [control.go:127] work connection closed, EOF
2019/03/13 14:52:38 [I] [service.go:127] try to reconnect to server...
2019/03/13 14:52:38 [W] [service.go:130] reconnect to server error: EOF
2019/03/13 14:52:39 [I] [service.go:127] try to reconnect to server...
2019/03/13 14:52:39 [W] [service.go:130] reconnect to server error: EOF
2019/03/13 15:02:35 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:02:36 [W] [service.go:130] reconnect to server error: EOF
2019/03/13 15:02:56 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:02:56 [I] [service.go:221] login to server success, get run id [a4094ec4e204c729], server udp port [0]
2019/03/13 15:02:56 [I] [proxy_manager.go:137] [a4094ec4e204c729] proxy added: [xxxxxx.ssh xxxxxx.web01 xxxxxx.web02]
2019/03/13 15:02:56 [I] [control.go:144] [xxxxxx.ssh] start proxy success
2019/03/13 15:02:56 [I] [control.go:144] [xxxxxx.web01] start proxy success
2019/03/13 15:02:56 [I] [control.go:144] [xxxxxx.web02] start proxy success
2019/03/13 15:25:59 [E] [control.go:127] work connection closed, EOF
2019/03/13 15:25:59 [E] [control.go:127] work connection closed, EOF
2019/03/13 15:25:59 [I] [control.go:224] control writer is closing
2019/03/13 15:25:59 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:26:09 [W] [service.go:130] reconnect to server error: i/o deadline reached
2019/03/13 15:26:10 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:26:20 [W] [service.go:130] reconnect to server error: i/o deadline reached
2019/03/13 15:26:22 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:26:32 [W] [service.go:130] reconnect to server error: i/o deadline reached
2019/03/13 15:26:36 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:47:01 [W] [service.go:130] reconnect to server error: i/o deadline reached
2019/03/13 15:47:21 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:47:31 [W] [service.go:130] reconnect to server error: i/o deadline reached
2019/03/13 15:47:51 [I] [service.go:127] try to reconnect to server...
2019/03/13 15:47:51 [W] [service.go:130] reconnect to server error: EOF

I have deleted repeated error log and my personal infomation.

Describe the results you expected:

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

It's reproduced twice since I use version-0.25.0 instead of 0.19.0

Network is definitly fine, because I sshed server and tail -f logfile to see what's going on. ("lianghui" is ending.)

Can you point out what caused this issue (optional)

I guess error comes out in last line of server_log.

Originally created by @doraven on GitHub (Mar 13, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1134 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)?** both 0.25.0 **What operating system and processor architecture are you using (`go env`)?** server: linode, Linux myserver 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux client: Linux myclient 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux **Configures you used:** server: ``` [common] bind_addr = 0.0.0.0 bind_port = 4451 kcp_bind_port = 4451 vhost_http_port = 880 vhost_https_port = 8443 dashboard_addr = 127.0.0.1 dashboard_port = 1236 dashboard_user = xx dashboard_pwd = xx token = xxx log_file = /home/xxx/sky/code/frps/log/frps.log log_level = info log_max_days = 30 max_pool_count = 5 max_ports_per_client = 5 subdomain_host = xxxx ``` client: ``` [common] server_addr = xxxx server_port = 4451 log_file = /home/xxx/code/frpc/log/frpc.log log_level = info log_max_days = 30 token = xxxx admin_addr = 127.0.0.1 admin_port = 2360 admin_user = admin admin_passwd = admin pool_count = 5 tcp_mux = true user = xxxx login_fail_exit = false protocol = kcp [ssh] type = tcp local_ip = 127.0.0.1 local_port = 4410 use_encryption = false use_compression = false remote_port = 4410 group = xxx group_key = xxxx [web01] type = http local_ip = 127.0.0.1 local_port = 4000 use_encryption = false use_compression = false subdomain = xxxxx [web02] type = http local_ip = 127.0.0.1 local_port = 3990 use_encryption = false use_compression = true subdomain = xxxx ``` And here is the service configure: server: ``` [Unit] Description=Frp Server After=network.target [Service] # User=xxx ExecStart=/home/xxx/sky/code/frps/frps -c /home/xxx/sky/code/frps/frps.ini [Install] WantedBy=multi-user.target ``` client: ``` [Unit] Description=Frp Client After=network.target [Service] User=xxxx ExecStart=/home/xxx/code/frpc/frpc -c /home/xxxx/code/frpc/frpc.ini [Install] WantedBy=multi-user.target ``` In client, i use my local user for service. And in server, it's sudo. **Steps to reproduce the issue:** It just happened, after about 1h of frp service. **Describe the results you received:** - server_log: ``` 2019/03/13 14:52:59 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451 2019/03/13 14:52:59 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451 2019/03/13 14:57:25 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451 2019/03/13 14:57:25 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451 2019/03/13 14:59:13 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451 2019/03/13 14:59:13 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451 2019/03/13 15:02:29 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451 2019/03/13 15:02:29 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451 2019/03/13 15:02:30 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451 2019/03/13 15:02:30 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451 2019/03/13 15:02:34 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451 2019/03/13 15:02:34 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451 2019/03/13 15:02:51 [I] [service.go:136] frps tcp listen on 0.0.0.0:4451 2019/03/13 15:02:51 [I] [service.go:145] frps kcp listen on udp 0.0.0.0:4451 2019/03/13 15:02:51 [I] [service.go:178] http service listen on 0.0.0.0:880 2019/03/13 15:02:51 [I] [service.go:199] https service listen on 0.0.0.0:8443 2019/03/13 15:02:51 [I] [service.go:229] Dashboard listen on 127.0.0.1:1236 2019/03/13 15:02:51 [I] [root.go:204] Start frps success 2019/03/13 15:02:56 [I] [service.go:337] client login info: ip [xx.xx.xx.xx:40590] version [0.25.0] hostname [] os [linux] arch [amd64] 2019/03/13 15:02:56 [I] [tcp.go:48] [a4094ec4e204c729] [xxx.ssh] tcp proxy listen port [4410] in group [xxx] 2019/03/13 15:02:56 [I] [control.go:397] [a4094ec4e204c729] new proxy [xxxxx.ssh] success 2019/03/13 15:02:56 [I] [http.go:85] [a4094ec4e204c729] [xxxxxx.web01] http proxy listen for host [xxxx.xxx.xxx] location [] 2019/03/13 15:02:56 [I] [control.go:397] [a4094ec4e204c729] new proxy [xxxxxx.web01] success 2019/03/13 15:02:56 [I] [http.go:85] [a4094ec4e204c729] [xxxxxx.web02] http proxy listen for host [xxxx.xxx.xxx] location [] 2019/03/13 15:02:56 [I] [control.go:397] [a4094ec4e204c729] new proxy [xxxxxx.web02] success 2019/03/13 15:11:24 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590] 2019/03/13 15:11:32 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590] 2019/03/13 15:11:32 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590] 2019/03/13 15:11:38 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590] 2019/03/13 15:11:39 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590] 2019/03/13 15:11:44 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590] 2019/03/13 15:11:45 [I] [proxy.go:80] [a4094ec4e204c729] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:40590] 2019/03/13 15:25:40 [I] [control.go:274] [a4094ec4e204c729] control writer is closing 2019/03/13 15:25:40 [I] [proxy.go:67] [a4094ec4e204c729] [xxxxxx.ssh] proxy closing 2019/03/13 15:25:40 [I] [proxy.go:67] [a4094ec4e204c729] [xxxxxx.web01] proxy closing 2019/03/13 15:25:40 [I] [proxy.go:67] [a4094ec4e204c729] [xxxxxx.web02] proxy closing 2019/03/13 15:25:40 [I] [control.go:349] [a4094ec4e204c729] client exit success 2019/03/13 15:25:40 [I] [proxy.go:112] [a4094ec4e204c729] [xxxxxx.ssh] listener is closed 2019/03/13 15:41:40 [W] [newhttp.go:209] http: proxy error: no such domain ``` - client_log: ``` 2019/03/13 14:50:06 [W] [service.go:82] login to server failed: EOF 2019/03/13 14:50:17 [W] [service.go:82] login to server failed: EOF 2019/03/13 14:50:27 [W] [service.go:82] login to server failed: EOF 2019/03/13 14:50:37 [W] [service.go:82] login to server failed: EOF 2019/03/13 14:50:47 [I] [service.go:221] login to server success, get run id [a4094ec4e204c729], server udp port [0] 2019/03/13 14:50:47 [I] [proxy_manager.go:137] [a4094ec4e204c729] proxy added: [xxxxxx.web01 xxxxxx.web02 xxxxxx.ssh] 2019/03/13 14:50:47 [I] [service.go:109] admin server listen on 127.0.0.1:2360 2019/03/13 14:50:48 [I] [control.go:144] [xxxxxx.web01] start proxy success 2019/03/13 14:50:48 [I] [control.go:144] [xxxxxx.web02] start proxy success 2019/03/13 14:50:48 [I] [control.go:144] [xxxxxx.ssh] start proxy success 2019/03/13 14:52:38 [E] [control.go:127] work connection closed, EOF 2019/03/13 14:52:38 [E] [control.go:127] work connection closed, EOF 2019/03/13 14:52:38 [I] [control.go:224] control writer is closing 2019/03/13 14:52:38 [E] [control.go:127] work connection closed, EOF 2019/03/13 14:52:38 [I] [service.go:127] try to reconnect to server... 2019/03/13 14:52:38 [W] [service.go:130] reconnect to server error: EOF 2019/03/13 14:52:39 [I] [service.go:127] try to reconnect to server... 2019/03/13 14:52:39 [W] [service.go:130] reconnect to server error: EOF 2019/03/13 15:02:35 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:02:36 [W] [service.go:130] reconnect to server error: EOF 2019/03/13 15:02:56 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:02:56 [I] [service.go:221] login to server success, get run id [a4094ec4e204c729], server udp port [0] 2019/03/13 15:02:56 [I] [proxy_manager.go:137] [a4094ec4e204c729] proxy added: [xxxxxx.ssh xxxxxx.web01 xxxxxx.web02] 2019/03/13 15:02:56 [I] [control.go:144] [xxxxxx.ssh] start proxy success 2019/03/13 15:02:56 [I] [control.go:144] [xxxxxx.web01] start proxy success 2019/03/13 15:02:56 [I] [control.go:144] [xxxxxx.web02] start proxy success 2019/03/13 15:25:59 [E] [control.go:127] work connection closed, EOF 2019/03/13 15:25:59 [E] [control.go:127] work connection closed, EOF 2019/03/13 15:25:59 [I] [control.go:224] control writer is closing 2019/03/13 15:25:59 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:26:09 [W] [service.go:130] reconnect to server error: i/o deadline reached 2019/03/13 15:26:10 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:26:20 [W] [service.go:130] reconnect to server error: i/o deadline reached 2019/03/13 15:26:22 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:26:32 [W] [service.go:130] reconnect to server error: i/o deadline reached 2019/03/13 15:26:36 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:47:01 [W] [service.go:130] reconnect to server error: i/o deadline reached 2019/03/13 15:47:21 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:47:31 [W] [service.go:130] reconnect to server error: i/o deadline reached 2019/03/13 15:47:51 [I] [service.go:127] try to reconnect to server... 2019/03/13 15:47:51 [W] [service.go:130] reconnect to server error: EOF ``` I have deleted repeated error log and my personal infomation. **Describe the results you expected:** **Additional information you deem important (e.g. issue happens only occasionally):** It's reproduced twice since I use version-0.25.0 instead of 0.19.0 Network is definitly fine, because I sshed server and `tail -f` logfile to see what's going on. ("lianghui" is ending.) **Can you point out what caused this issue (optional)** I guess error comes out in last line of server_log.
gitea-mirror commented 2026-05-05 12:33:54 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Mar 13, 2019):

Use tcp protocol or try to change kcp_bind_port.

<!-- gh-comment-id:472326979 --> @fatedier commented on GitHub (Mar 13, 2019): Use tcp protocol or try to change kcp_bind_port.
gitea-mirror commented 2026-05-05 12:33:54 -06:00
Author
Owner
Copy link

@doraven commented on GitHub (Mar 13, 2019):

Use tcp protocol or try to change kcp_bind_port.

ok, I've delete kcp settings both in client and server .ini file.

protocol = kcp

kcp_bind_port = 4451

I'll test by your instructions.

And do you mean kcp and tcp shall not share the same ports now in 0.25.0, because it worked fine before I update today.

<!-- gh-comment-id:472330525 --> @doraven commented on GitHub (Mar 13, 2019): > Use tcp protocol or try to change kcp_bind_port. ok, I've delete kcp settings both in client and server .ini file. ~~protocol = kcp~~ ~~kcp_bind_port = 4451~~ I'll test by your instructions. And do you mean kcp and tcp shall not share the same ports now in 0.25.0, because it worked fine before I update today.
gitea-mirror commented 2026-05-05 12:33:55 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Mar 13, 2019):

No, just try each case to find what's wrong.

<!-- gh-comment-id:472331590 --> @fatedier commented on GitHub (Mar 13, 2019): No, just try each case to find what's wrong.
gitea-mirror commented 2026-05-05 12:33:55 -06:00
Author
Owner
Copy link

@doraven commented on GitHub (Mar 14, 2019):

No, just try each case to find what's wrong.

Now reports:

Now it got a error in server_log here, but it still works now

server_log

Although It got error twice yesterday, worked fine yet.

I've selected the error-part of logs.

-
-
-
2019/03/13 18:16:27 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.web02] get a new work connection: [xxx.xxx.xxx.xxx:37854]
2019/03/13 20:04:52 [W] [newhttp.go:209] http: proxy error: no such domain
2019/03/13 20:18:27 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:37854]
-
-
-
2019/03/13 20:58:58 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:37854]
2019/03/13 22:23:21 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:37854]
2019/03/13 22:38:37 [W] [newhttp.go:209] http: proxy error: no such domain
2019/03/13 23:36:17 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.ssh] get a new work connection: [xxx.xxx.xxx.xxx:37854]
2019/03/13 23:36:36 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.ssh] get a new work connection: [xxx.xxx.xxx.xxx:37854]
-
-
-

client_log when error appears

[Nothing!]

Last log in client is saying:

2019/03/13 16:38:39 [I] [service.go:221] login to server success, get run id [0984257b3a63f2b8], server udp port [0]
2019/03/13 16:38:39 [I] [proxy_manager.go:137] [0984257b3a63f2b8] proxy added: [xxxxx.web01 xxxxx.web02 xxxxx.ssh]
2019/03/13 16:38:39 [I] [service.go:109] admin server listen on 127.0.0.1:2360
2019/03/13 16:38:39 [I] [control.go:144] [xxxxx.web01] start proxy success
2019/03/13 16:38:39 [I] [control.go:144] [xxxxx.web02] start proxy success
2019/03/13 16:38:39 [I] [control.go:144] [xxxxx.ssh] start proxy success

** I'd like to test kcp, but I don't know how to config. As far as my knowledge, I can only send one port to frp server.

<!-- gh-comment-id:472669505 --> @doraven commented on GitHub (Mar 14, 2019): > No, just try each case to find what's wrong. Now reports: Now it got a error in server_log here, but it still works now ## server_log Although It got error twice yesterday, worked fine yet. I've selected the error-part of logs. ``` - - - 2019/03/13 18:16:27 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.web02] get a new work connection: [xxx.xxx.xxx.xxx:37854] 2019/03/13 20:04:52 [W] [newhttp.go:209] http: proxy error: no such domain 2019/03/13 20:18:27 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:37854] - - - 2019/03/13 20:58:58 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:37854] 2019/03/13 22:23:21 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.web01] get a new work connection: [xxx.xxx.xxx.xxx:37854] 2019/03/13 22:38:37 [W] [newhttp.go:209] http: proxy error: no such domain 2019/03/13 23:36:17 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.ssh] get a new work connection: [xxx.xxx.xxx.xxx:37854] 2019/03/13 23:36:36 [I] [proxy.go:80] [0984257b3a63f2b8] [xxxxx.ssh] get a new work connection: [xxx.xxx.xxx.xxx:37854] - - - ``` ## client_log when error appears ``` [Nothing!] ``` Last log in client is saying: ``` 2019/03/13 16:38:39 [I] [service.go:221] login to server success, get run id [0984257b3a63f2b8], server udp port [0] 2019/03/13 16:38:39 [I] [proxy_manager.go:137] [0984257b3a63f2b8] proxy added: [xxxxx.web01 xxxxx.web02 xxxxx.ssh] 2019/03/13 16:38:39 [I] [service.go:109] admin server listen on 127.0.0.1:2360 2019/03/13 16:38:39 [I] [control.go:144] [xxxxx.web01] start proxy success 2019/03/13 16:38:39 [I] [control.go:144] [xxxxx.web02] start proxy success 2019/03/13 16:38:39 [I] [control.go:144] [xxxxx.ssh] start proxy success ``` ** I'd like to test kcp, but I don't know how to config. As far as my knowledge, I can only send one port to frp server.
gitea-mirror commented 2026-05-05 12:33:56 -06:00
Author
Owner
Copy link

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

https://github.com/fatedier/frp#support-kcp-protocol

I'm not sure what's wrong about kcp, maybe it's not stable.

<!-- gh-comment-id:472721494 --> @fatedier commented on GitHub (Mar 14, 2019): https://github.com/fatedier/frp#support-kcp-protocol I'm not sure what's wrong about kcp, maybe it's not stable.
gitea-mirror commented 2026-05-05 12:33:56 -06:00
Author
Owner
Copy link

@doraven commented on GitHub (Mar 14, 2019):

I tried with kcp using different portocol to tcp. And it runned 1h with no error.

Now I config back to yesterday, to see if this issue can be reproduced.

sry, it's working fine now. I'll report later if error appears.

<!-- gh-comment-id:472808024 --> @doraven commented on GitHub (Mar 14, 2019): I tried with kcp using different portocol to tcp. And it runned 1h with no error. Now I config back to yesterday, to see if this issue can be reproduced. sry, it's working fine now. I'll report later if error appears.
gitea-mirror commented 2026-05-05 12:33:57 -06:00
Author
Owner
Copy link

@doraven commented on GitHub (Mar 15, 2019):

I tried with kcp using different portocol to tcp. And it runned 1h with no error.

Now I config back to yesterday, to see if this issue can be reproduced.

sry, it's working fine now. I'll report later if error appears.

Okay, error still came out.

Reproduced, but it runned 6 hours this time before crash. In my early tests, only 25mins will crash the program.

reconnect to server error:i/o deadline reached

client_log before that

2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF
2019/03/14 22:47:41 [I] [control.go:224] control writer is closing
2019/03/14 22:47:41 [I] [service.go:127] try to reconnect to server...
2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF
2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF
2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF
2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF

At that time of server_log:

2019/03/14 22:47:25 [I] [control.go:274] [4a055b8b49cda113] control writer is closing
2019/03/14 22:47:25 [I] [proxy.go:67] [4a055b8b49cda113] [xxx.ssh] proxy closing
2019/03/14 22:47:25 [I] [proxy.go:67] [4a055b8b49cda113] [xxxx.web01] proxy closing
2019/03/14 22:47:25 [I] [proxy.go:67] [4a055b8b49cda113] [xxxx.web02] proxy closing
2019/03/14 22:47:25 [I] [control.go:349] [4a055b8b49cda113] client exit success
2019/03/14 22:47:25 [I] [proxy.go:112] [4a055b8b49cda113] [xxxxx.ssh] listener is closed

So from my test

If kcp set the same protocol as tcp, it'll get errors.

And different protocols or only use tcp will run as expected.

<!-- gh-comment-id:473123852 --> @doraven commented on GitHub (Mar 15, 2019): > I tried with kcp using different portocol to tcp. And it runned 1h with no error. > > Now I config back to yesterday, to see if this issue can be reproduced. > > sry, it's working fine now. I'll report later if error appears. Okay, error still came out. Reproduced, but it runned 6 hours this time before crash. In my early tests, only 25mins will crash the program. `reconnect to server error:i/o deadline reached` client_log before that ``` 2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF 2019/03/14 22:47:41 [I] [control.go:224] control writer is closing 2019/03/14 22:47:41 [I] [service.go:127] try to reconnect to server... 2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF 2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF 2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF 2019/03/14 22:47:41 [E] [control.go:127] work connection closed, EOF ``` At that time of server_log: ``` 2019/03/14 22:47:25 [I] [control.go:274] [4a055b8b49cda113] control writer is closing 2019/03/14 22:47:25 [I] [proxy.go:67] [4a055b8b49cda113] [xxx.ssh] proxy closing 2019/03/14 22:47:25 [I] [proxy.go:67] [4a055b8b49cda113] [xxxx.web01] proxy closing 2019/03/14 22:47:25 [I] [proxy.go:67] [4a055b8b49cda113] [xxxx.web02] proxy closing 2019/03/14 22:47:25 [I] [control.go:349] [4a055b8b49cda113] client exit success 2019/03/14 22:47:25 [I] [proxy.go:112] [4a055b8b49cda113] [xxxxx.ssh] listener is closed ``` ### So from my test If kcp set the same protocol as tcp, it'll get errors. And different protocols or only use tcp will run as expected.
gitea-mirror commented 2026-05-05 12:33:57 -06:00
Author
Owner
Copy link

@doraven commented on GitHub (Mar 16, 2019):

It seems to be problem of kcp protocol.

It threw out error even if I set different ports as tcp.

<!-- gh-comment-id:473528393 --> @doraven commented on GitHub (Mar 16, 2019): It seems to be problem of kcp protocol. It threw out error even if I set different ports as tcp.
gitea-mirror commented 2026-05-05 12:33:58 -06:00
Author
Owner
Copy link

@keeno1982 commented on GitHub (Apr 29, 2019):

@fatedier 这个后面有解决吗？我也遇到这个问题，从0.25.0这个版本开始就会一直断线，每个版本我都试过了，一直没有解决这个问题，只能一直用0.24.1

<!-- gh-comment-id:487636607 --> @keeno1982 commented on GitHub (Apr 29, 2019): @fatedier 这个后面有解决吗？我也遇到这个问题，从0.25.0这个版本开始就会一直断线，每个版本我都试过了，一直没有解决这个问题，只能一直用0.24.1
gitea-mirror commented 2026-05-05 12:33:58 -06:00
Author
Owner
Copy link

@befantasy commented on GitHub (Jun 3, 2019):

same problem for me. 0.27 version.

<!-- gh-comment-id:498106554 --> @befantasy commented on GitHub (Jun 3, 2019): same problem for me. 0.27 version.
gitea-mirror commented 2026-05-05 12:33:59 -06:00
Author
Owner
Copy link

@fatedier commented on GitHub (Jun 4, 2019):

Track #1267

<!-- gh-comment-id:498543249 --> @fatedier commented on GitHub (Jun 4, 2019): Track #1267
gitea-mirror commented 2026-05-05 12:33:59 -06:00
Author
Owner
Copy link

@marcuswang6 commented on GitHub (Apr 4, 2022):

same for me 2022.4.4

<!-- gh-comment-id:1087070924 --> @marcuswang6 commented on GitHub (Apr 4, 2022): same for me 2022.4.4
gitea-mirror commented 2026-05-05 12:33:59 -06:00
Author
Owner
Copy link

@lliding commented on GitHub (Apr 16, 2022):

same for me 2022.4.16 with server and client v0.37.1

<!-- gh-comment-id:1100666109 --> @lliding commented on GitHub (Apr 16, 2022): same for me 2022.4.16 with server and client v0.37.1
gitea-mirror commented 2026-05-05 12:34:01 -06:00
Author
Owner
Copy link

@shaojs321 commented on GitHub (Feb 23, 2023):

出现同样问题
使用tcp连接ssh，frp服务器是腾讯国内服务器，连接的是老家的nas

frp客户端日志：
adline reached
2023/02/23 08:45:52 [I] [service.go:174] [3ff048e286e44363] try to reconnect to server...
2023/02/23 08:46:02 [W] [service.go:177] [3ff048e286e44363] reconnect to server error: i/o deadline reached

frp服务器日志：
363]
2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [xx.xx.xx.xx5:5291]
2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5293]
2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5297]
2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5299]
2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5301]
2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5303]
2023/02/23 08:46:53 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5305]
2023/02/23 08:46:56 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5307]
2023/02/23 08:47:05 [I] [proxy.go:179] [3ff048e286e44363] [群晖ssh] get a user connection [xx.xx.xx.xx:59726]
2023/02/23 08:47:16 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [45.79.168.172:38668]
2023/02/23 08:47:22 [I] [service.go:500] [3ff048e286e44363] client login info: ip [183.209.92.53:20982] version [0.38.0] hostname [] os [linux] arch [amd64]
2023/02/23 08:47:22 [I] [control.go:280] [3ff048e286e44363] Replaced by client [3ff048e286e44363]
2023/02/23 08:47:25 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [45.79.168.172:38669]
2023/02/23 08:47:35 [I] [proxy.go:179] [3ff048e286e44363] [群晖ssh] get a user connection [xx,xx,xx.xx8:42566]
2023/02/23 08:47:52 [I] [service.go:500] [3ff048e286e44363] client login info: ip [183.209.92.53:21228] version [0.38.0] hostname [] os [linux] arch [amd64]
2023/02/23 08:47:52 [I] [control.go:280] [3ff048e286e44363] Replaced by client [3ff048e286e44363]
2023/02/23 08:48:09 [I] [proxy.go:179] [3ff048e286e44363] [群晖ssh] get a user connection [45.93.201.118:53208]

<!-- gh-comment-id:1441447350 --> @shaojs321 commented on GitHub (Feb 23, 2023): 出现同样问题 使用tcp连接ssh，frp服务器是腾讯国内服务器，连接的是老家的nas frp客户端日志： adline reached 2023/02/23 08:45:52 [I] [service.go:174] [3ff048e286e44363] try to reconnect to server... 2023/02/23 08:46:02 [W] [service.go:177] [3ff048e286e44363] reconnect to server error: i/o deadline reached frp服务器日志： 363] 2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [xx.xx.xx.xx5:5291] 2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5293] 2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5297] 2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5299] 2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5301] 2023/02/23 08:46:52 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5303] 2023/02/23 08:46:53 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5305] 2023/02/23 08:46:56 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [218.79.149.165:5307] 2023/02/23 08:47:05 [I] [proxy.go:179] [3ff048e286e44363] [群晖ssh] get a user connection [xx.xx.xx.xx:59726] 2023/02/23 08:47:16 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [45.79.168.172:38668] 2023/02/23 08:47:22 [I] [service.go:500] [3ff048e286e44363] client login info: ip [183.209.92.53:20982] version [0.38.0] hostname [] os [linux] arch [amd64] 2023/02/23 08:47:22 [I] [control.go:280] [3ff048e286e44363] Replaced by client [3ff048e286e44363] 2023/02/23 08:47:25 [I] [proxy.go:179] [7a1bdcce92c6ff79] [openwrt.logic] get a user connection [45.79.168.172:38669] 2023/02/23 08:47:35 [I] [proxy.go:179] [3ff048e286e44363] [群晖ssh] get a user connection [xx,xx,xx.xx8:42566] 2023/02/23 08:47:52 [I] [service.go:500] [3ff048e286e44363] client login info: ip [183.209.92.53:21228] version [0.38.0] hostname [] os [linux] arch [amd64] 2023/02/23 08:47:52 [I] [control.go:280] [3ff048e286e44363] Replaced by client [3ff048e286e44363] 2023/02/23 08:48:09 [I] [proxy.go:179] [3ff048e286e44363] [群晖ssh] get a user connection [45.93.201.118:53208]
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#888
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?