[GH-ISSUE #3440] 连接失败会话结束 #2756

Closed
opened 2026-05-05 13:46:33 -06:00 by gitea-mirror · 11 comments
Owner

Originally created by @jsgzsjskj on GitHub (May 13, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3440

Bug Description

frps服务器端正常运行,frpc客户端是Windows 在写好配置后执行:
D:\Software\frp_0.48.0_windows_amd64>frpc -c ./frpc.ini
2023/05/13 23:25:12 [W] [service.go:134] login to server failed: session shutdown
session shutdown
端口放行了的 服务器出入规则为全部 所有来源

frpc Version

0.48.0

frps Version

0.20.0

System Architecture

liux/amd64,windows/amd64

Configurations

[common]
tls_enable = true
server_addr = 52.12.85.198
server_port = 5443
token = 隐藏

[My Home PC]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 3390
custom_domains = frp.jskj.tk

[FTP_server]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 2222
custom_domains = ftp.jskj.tk

Logs

frpc端无法启动
D:\Software\frp_0.48.0_windows_amd64>frpc.exe -c ./frpc.ini
2023/05/14 01:23:34 [W] [service.go:134] login to server failed: session shutdown
session shutdown
D:\Software\frp_0.48.0_windows_amd64>telnet 52.12.85.198 5443
DNS 服务器对区域没有权威。
D:\Software\frp_0.48.0_windows_amd64>curl 52.12.85.198:5443
curl: (52) Empty reply from server

frps服务器:
root@ip-172-31-23-192:# ufw allow 5443
Skipping adding existing rule
Skipping adding existing rule (v6)
root@ip-172-31-23-192:
# ufw allow 3389
Skipping adding existing rule
Skipping adding existing rule (v6)
root@ip-172-31-23-192:# ufw allow 3390
Skipping adding existing rule
Skipping adding existing rule (v6)
root@ip-172-31-23-192:
# ufw allow 22
Skipping adding existing rule
Skipping adding existing rule (v6)
root@ip-172-31-23-192:# ufw allow 2222
Skipping adding existing rule
Skipping adding existing rule (v6)
root@ip-172-31-23-192:
# frps status
Frps (pid 44020) is running...
root@ip-172-31-23-192:~# frps restart

log
2023/05/13 11:32:42 [I] [service.go:128] frps tcp listen on 0.0.0.0:5443
2023/05/13 11:32:42 [I] [service.go:137] frps kcp listen on udp 0.0.0.0:5443
2023/05/13 11:32:42 [I] [service.go:161] http service listen on 0.0.0.0:5000
2023/05/13 11:32:42 [I] [service.go:182] https service listen on 0.0.0.0:5001
2023/05/13 11:32:42 [I] [service.go:205] Dashboard listen on 0.0.0.0:888
2023/05/13 11:32:42 [I] [root.go:190] Start frps success
2023/05/13 11:33:46 [I] [dashboard_api.go:67] Http request: [/api/serverinfo]
2023/05/13 11:33:46 [I] [dashboard_api.go:64] Http response [/api/serverinfo]: code [0]
2023/05/13 11:46:54 [I] [dashboard_api.go:67] Http request: [/api/serverinfo]
2023/05/13 11:46:54 [I] [dashboard_api.go:64] Http response [/api/serverinfo]: code [0]

Steps to reproduce

  1. 打开cmd
  2. 进入frpc目录
  3. 执行frpc -c ./frpc.ini
  4. 校园网切换到手机热点关闭Windows防火墙依然这样

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @jsgzsjskj on GitHub (May 13, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3440 ### Bug Description frps服务器端正常运行,frpc客户端是Windows 在写好配置后执行: D:\Software\frp_0.48.0_windows_amd64>frpc -c ./frpc.ini 2023/05/13 23:25:12 [W] [service.go:134] login to server failed: session shutdown session shutdown 端口放行了的 服务器出入规则为全部 所有来源 ### frpc Version 0.48.0 ### frps Version 0.20.0 ### System Architecture liux/amd64,windows/amd64 ### Configurations [common] tls_enable = true server_addr = 52.12.85.198 server_port = 5443 token = 隐藏 [My Home PC] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 3390 custom_domains = frp.jskj.tk [FTP_server] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 2222 custom_domains = ftp.jskj.tk ### Logs frpc端无法启动 D:\Software\frp_0.48.0_windows_amd64>frpc.exe -c ./frpc.ini 2023/05/14 01:23:34 [W] [service.go:134] login to server failed: session shutdown session shutdown D:\Software\frp_0.48.0_windows_amd64>telnet 52.12.85.198 5443 DNS 服务器对区域没有权威。 D:\Software\frp_0.48.0_windows_amd64>curl 52.12.85.198:5443 curl: (52) Empty reply from server frps服务器: root@ip-172-31-23-192:~# ufw allow 5443 Skipping adding existing rule Skipping adding existing rule (v6) root@ip-172-31-23-192:~# ufw allow 3389 Skipping adding existing rule Skipping adding existing rule (v6) root@ip-172-31-23-192:~# ufw allow 3390 Skipping adding existing rule Skipping adding existing rule (v6) root@ip-172-31-23-192:~# ufw allow 22 Skipping adding existing rule Skipping adding existing rule (v6) root@ip-172-31-23-192:~# ufw allow 2222 Skipping adding existing rule Skipping adding existing rule (v6) root@ip-172-31-23-192:~# frps status Frps (pid 44020) is running... root@ip-172-31-23-192:~# frps restart log 2023/05/13 11:32:42 [I] [service.go:128] frps tcp listen on 0.0.0.0:5443 2023/05/13 11:32:42 [I] [service.go:137] frps kcp listen on udp 0.0.0.0:5443 2023/05/13 11:32:42 [I] [service.go:161] http service listen on 0.0.0.0:5000 2023/05/13 11:32:42 [I] [service.go:182] https service listen on 0.0.0.0:5001 2023/05/13 11:32:42 [I] [service.go:205] Dashboard listen on 0.0.0.0:888 2023/05/13 11:32:42 [I] [root.go:190] Start frps success 2023/05/13 11:33:46 [I] [dashboard_api.go:67] Http request: [/api/serverinfo] 2023/05/13 11:33:46 [I] [dashboard_api.go:64] Http response [/api/serverinfo]: code [0] 2023/05/13 11:46:54 [I] [dashboard_api.go:67] Http request: [/api/serverinfo] 2023/05/13 11:46:54 [I] [dashboard_api.go:64] Http response [/api/serverinfo]: code [0] ### Steps to reproduce 1. 打开cmd 2. 进入frpc目录 3. 执行frpc -c ./frpc.ini 4. 校园网切换到手机热点关闭Windows防火墙依然这样 ### Affected area - [ ] Docs - [X] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:46:33 -06:00
Author
Owner

@jsgzsjskj commented on GitHub (May 14, 2023):

关闭防火墙,第二天校园网来网后尝试login to server failed: EOFEOF

<!-- gh-comment-id:1546801059 --> @jsgzsjskj commented on GitHub (May 14, 2023): 关闭防火墙,第二天校园网来网后尝试login to server failed: EOFEOF
Author
Owner

@jsgzsjskj commented on GitHub (May 14, 2023):

在frps设置kcp_bind_port = 5443
后 frp添加protocol = kcp后启动报错
login to server failed: connection write timeout
connection write timeout

<!-- gh-comment-id:1546805166 --> @jsgzsjskj commented on GitHub (May 14, 2023): 在frps设置kcp_bind_port = 5443 后 frp添加protocol = kcp后启动报错 login to server failed: connection write timeout connection write timeout
Author
Owner

@Becods commented on GitHub (May 15, 2023):

被阻断了

更新frps

https://github.com/fatedier/frp/issues/1992 https://github.com/fatedier/frp/issues/3050

db52f07d34/conf/frpc_full.ini (L118-L119)

da51adc276/pkg/msg/msg.go (L61-L191)

建议不要在公司禁止的情况下使用,安全风险和后果需要自负。

<!-- gh-comment-id:1547538834 --> @Becods commented on GitHub (May 15, 2023): 被阻断了 更新frps https://github.com/fatedier/frp/issues/1992 https://github.com/fatedier/frp/issues/3050 https://github.com/fatedier/frp/blob/db52f07d3492946037d85df7bfbfda0013481a27/conf/frpc_full.ini#L118-L119 https://github.com/fatedier/frp/blob/da51adc27670f495478f50634462954319e4fc14/pkg/msg/msg.go#L61-L191 > 建议不要在公司禁止的情况下使用,安全风险和后果需要自负。
Author
Owner

@jsgzsjskj commented on GitHub (May 15, 2023):

被阻断了

更新frps

#1992 #3050

db52f07d34/conf/frpc_full.ini (L118-L119)

da51adc276/pkg/msg/msg.go (L61-L191)

建议不要在公司禁止的情况下使用,安全风险和结果需要自负。

我在两端都添加过tle_ensble = yes依然不行的 被校园网拦截,这些是会被拦截的内容吗?我该怎样去解决

<!-- gh-comment-id:1548255043 --> @jsgzsjskj commented on GitHub (May 15, 2023): > 被阻断了 > > 更新frps > > [#1992 ](https://github.com/fatedier/frp/issues/1992) #3050 > > https://github.com/fatedier/frp/blob/db52f07d3492946037d85df7bfbfda0013481a27/conf/frpc_full.ini#L118-L119 > > https://github.com/fatedier/frp/blob/da51adc27670f495478f50634462954319e4fc14/pkg/msg/msg.go#L61-L191 > > > 建议不要在公司禁止的情况下使用,安全风险和结果需要自负。 我在两端都添加过tle_ensble = yes依然不行的 被校园网拦截,这些是会被拦截的内容吗?我该怎样去解决
Author
Owner
<!-- gh-comment-id:1550055372 --> @xqzr commented on GitHub (May 16, 2023): https://github.com/fatedier/frp/issues/3193#issuecomment-1332547301
Author
Owner

@jsgzsjskj commented on GitHub (May 17, 2023):

第3193章(评论)

试了还是不行

<!-- gh-comment-id:1550774029 --> @jsgzsjskj commented on GitHub (May 17, 2023): > [第3193章(评论)](https://github.com/fatedier/frp/issues/3193#issuecomment-1332547301) 试了还是不行
Author
Owner

@xqzr commented on GitHub (May 21, 2023):

第3193章(评论)

试了还是不行

protocol = quic

<!-- gh-comment-id:1556137292 --> @xqzr commented on GitHub (May 21, 2023): > > [第3193章(评论)](https://github.com/fatedier/frp/issues/3193#issuecomment-1332547301) > > 试了还是不行 `protocol = quic`
Author
Owner

@jsgzsjskj commented on GitHub (May 22, 2023):

第3193章(评论)

试了还是不行

protocol = quic

加了后是超时login to server failed: timeout: no recent network activity
timeout: no recent network activity

<!-- gh-comment-id:1556997719 --> @jsgzsjskj commented on GitHub (May 22, 2023): > > > [第3193章(评论)](https://github.com/fatedier/frp/issues/3193#issuecomment-1332547301) > > > > > > 试了还是不行 > > `protocol = quic` 加了后是超时login to server failed: timeout: no recent network activity timeout: no recent network activity
Author
Owner

@xqzr commented on GitHub (May 22, 2023):

第3193章(评论)

试了还是不行

protocol = quic

加了后是超时登录到服务器失败:超时:无最近的网络活动超时:没有最近的网络活动

放行 相应 UDP 端口

<!-- gh-comment-id:1557611485 --> @xqzr commented on GitHub (May 22, 2023): > > > > [第3193章(评论)](https://github.com/fatedier/frp/issues/3193#issuecomment-1332547301) > > > > > > > > > 试了还是不行 > > > > > > `protocol = quic` > > 加了后是超时登录到服务器失败:超时:无最近的网络活动超时:没有最近的网络活动 放行 相应 UDP 端口
Author
Owner

@jsgzsjskj commented on GitHub (May 23, 2023):

第3193章(评论)

试了还是不行

protocol = quic

加了后是超时登录到服务器失败:超时:无最近的网络活动超时:没有最近的网络活动

放行 相应 UDP 端口

我是vps出入规则是全部流量

<!-- gh-comment-id:1558395064 --> @jsgzsjskj commented on GitHub (May 23, 2023): > > > > > [第3193章(评论)](https://github.com/fatedier/frp/issues/3193#issuecomment-1332547301) > > > > > > > > > > > > 试了还是不行 > > > > > > > > > `protocol = quic` > > > > > > 加了后是超时登录到服务器失败:超时:无最近的网络活动超时:没有最近的网络活动 > > 放行 相应 UDP 端口 我是vps出入规则是全部流量
Author
Owner

@github-actions[bot] commented on GitHub (Jun 23, 2023):

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

<!-- gh-comment-id:1603477214 --> @github-actions[bot] commented on GitHub (Jun 23, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
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#2756
No description provided.