[GH-ISSUE #3479] Connection reset by peer

gitea-mirror commented

2026-05-05 13:47:35 -06:00

Owner

Copy link

Originally created by @liunx7594 on GitHub (Jun 6, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3479

Bug Description

When I run the client, I always report an error.
The following is the output result of the running client

2023/06/06 10:49:26 [W] [service.go:132] login to server failed: read tcp 192.168.1.116:48200->202.111.16.100:7000: read: connection reset by peer
read tcp 192.168.1.116:48200->202.111.16.100:7000: read: connection reset by peer

2023/06/06 10:56:01 [W] [service.go:132] login to server failed: read tcp 192.168.1.116:46766->202.111.16.100:7000: read: connection reset by peer
read tcp 192.168.1.116:46766->202.111.16.100:7000: read: connection reset by peer

frpc Version

0.45.0

frps Version

0.45.0

System Architecture

linux/amd64 ubuntu

Configurations

[common]
server_addr = 202.111.16.100
server_port = 7000
tls_enable = true

[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 6000

Logs

Steps to reproduce

No response

Affected area

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

Originally created by @liunx7594 on GitHub (Jun 6, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3479 ### Bug Description When I run the client, I always report an error. The following is the output result of the running client 2023/06/06 10:49:26 [W] [service.go:132] login to server failed: read tcp 192.168.1.116:48200->202.111.16.100:7000: read: connection reset by peer read tcp 192.168.1.116:48200->202.111.16.100:7000: read: connection reset by peer 2023/06/06 10:56:01 [W] [service.go:132] login to server failed: read tcp 192.168.1.116:46766->202.111.16.100:7000: read: connection reset by peer read tcp 192.168.1.116:46766->202.111.16.100:7000: read: connection reset by peer ### frpc Version 0.45.0 ### frps Version 0.45.0 ### System Architecture linux/amd64 ubuntu ### Configurations [common] server_addr = 202.111.16.100 server_port = 7000 tls_enable = true [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000 ### Logs 2023/06/06 10:49:26 [W] [service.go:132] login to server failed: read tcp 192.168.1.116:48200->202.111.16.100:7000: read: connection reset by peer read tcp 192.168.1.116:48200->202.111.16.100:7000: read: connection reset by peer 2023/06/06 10:56:01 [W] [service.go:132] login to server failed: read tcp 192.168.1.116:46766->202.111.16.100:7000: read: connection reset by peer read tcp 192.168.1.116:46766->202.111.16.100:7000: read: connection reset by peer ### Steps to reproduce _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [X] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:47:35 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:47:38 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Jun 6, 2023):

Check your firewall.

@Becods commented on GitHub (Jun 6, 2023): ![image](https://github.com/fatedier/frp/assets/35525491/3cf58077-2a17-4bb5-99a5-5c96d3327828) Check your firewall.

gitea-mirror commented

2026-05-05 13:47:39 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jul 7, 2023):

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 (Jul 7, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified