[GH-ISSUE #2710] frps frpc tcp_mux=false An existing connection was forcibly closed by the remote host

gitea-mirror commented

2026-05-05 13:23:37 -06:00

Owner

Copy link

Originally created by @Florance3055 on GitHub (Dec 20, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2710

Bug Description

[W] [service.go:104] login to server failed: read tcp 10.9.5.2:1868->...:60019: wsarecv: An existing connection was forcibly closed by the remote host.
read tcp 10.9.5.2:1868->...**:: wsarecv: An existing connection was forcibly closed by the remote host.

frpc Version

0.38

frps Version

0.38

System Architecture

linux/amd64 windows/amd64

Configurations

#frps.ini
[common]
bind_port = 60019
tcp_mux = false

#frpc.ini
[common]
server_addr = ...*:
server_port = 60019
tcp_mux = false

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @Florance3055 on GitHub (Dec 20, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2710 ### Bug Description [W] [service.go:104] login to server failed: read tcp 10.9.5.2:1868->**.***.**.**:60019: wsarecv: An existing connection was forcibly closed by the remote host. read tcp 10.9.5.2:1868->**.***.**.**:: wsarecv: An existing connection was forcibly closed by the remote host. ### frpc Version 0.38 ### frps Version 0.38 ### System Architecture linux/amd64 windows/amd64 ### Configurations #frps.ini [common] bind_port = 60019 tcp_mux = false #frpc.ini [common] server_addr = **.***.**.**: server_port = 60019 tcp_mux = false ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:23:37 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:23:41 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 20, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 20, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:43:35 -06:00

[PR #2165] [MERGED] Reduced log level of "get hostname error" #4516

No Branch/Tag specified