[GH-ISSUE #855] i/o deadline reached ( the client did not exit correctly ) #674

New issue

Closed

opened 2026-05-05 12:26:14 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 12:26:14 -06:00

Owner

Originally created by @ZhangGaoxing on GitHub (Jul 17, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/855

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

What operating system and processor architecture are you using (go env)?
frpc : Windows 10 1803
frps : Windows Server 2016 Datacenter

Configures you used:
frpc.ini
[common]
server_addr = *
server_port = 7000
token = *

[RDP]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 7002
custom_domains = *

frps.ini
[common]
bind_port = 7000
dashboard_user = admin
dashboard_pwd = *
dashboard_port = 7500
token = *

Steps to reproduce the issue:

Run frpc.exe in the background
Shutdown or restart the client
After that, run frpc.exe again

Describe the results you received:
In frps logs, the client did not exit, so it reconnected failed.

Describe the results you expected:
When frpc.exe runs in the background, shutdown or reboot the client, frpc.exe can exit correctly.

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

Can you point out what caused this issue (optional)

Originally created by @ZhangGaoxing on GitHub (Jul 17, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/855 **What version of frp are you using (./frpc -v or ./frps -v)?** 0.20 **What operating system and processor architecture are you using (`go env`)?** frpc : Windows 10 1803 frps : Windows Server 2016 Datacenter **Configures you used:** frpc.ini [common] server_addr = * server_port = 7000 token = * [RDP] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 7002 custom_domains = * frps.ini [common] bind_port = 7000 dashboard_user = admin dashboard_pwd = * dashboard_port = 7500 token = * **Steps to reproduce the issue:** 1. Run frpc.exe in the background 2. Shutdown or restart the client 3. After that, run frpc.exe again **Describe the results you received:** In frps logs, the client did not exit, so it reconnected failed. **Describe the results you expected:** When frpc.exe runs in the background, shutdown or reboot the client, frpc.exe can exit correctly. **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**