With using authtoken,it cloud be link failure in version 0.57.0

[Jiale23]

Bug Description

When i using such as this config .toml

auth.method = "token"
auth.token = "vMCMpebGdfQiQSyzfjsyCOKh"

it will be connect a crash like this

2024-05-06 21:57:53.813 [I] [sub/root.go:142] start frpc service for config file [frpc.toml]
2024-05-06 21:57:53.824 [I] [client/service.go:294] try to connect to server...
2024-05-06 21:57:53.873 [W] [client/service.go:297] connect to server error: read tcp 192.168.31.140:62182->xx.xx.xx.xx:xxxx: wsarecv: An existing connection was forcibly closed by the remote host.
2024-05-06 21:57:53.873 [I] [sub/root.go:160] frpc service for config file [frpc.toml] stopped
login to the server failed: read tcp 192.168.31.140:62182->xx.xx.xx.xx:xxxx:: wsarecv: An existing connection was forcibly closed by the remote host.. With loginFailExit enabled, no additional retries will be attempted

frpc Version

0.57.0

frps Version

0.57.0

System Architecture

frps:linux/amd64,frpc:windows/amd64

Configurations

serverAddr = "xx.xx.xx.xx"
serverPort = xxxx
auth.method = "token"
auth.token = "vMCMpebGdfQiQSyzfjsyCOKh" #it is random generate

[[proxies]]
name = "test-tcp"
type = "tcp"
localIP = "127.0.0.1"
localPort = 22
remotePort = 6000

Logs

D:\Download\frp_0.57.0_windows_amd64>frpc.exe -c frpc.toml
2024-05-06 21:57:53.813 [I] [sub/root.go:142] start frpc service for config file [frpc.toml]
2024-05-06 21:57:53.824 [I] [client/service.go:294] try to connect to server...
2024-05-06 21:57:53.873 [W] [client/service.go:297] connect to server error: read tcp 192.168.31.140:62182->xx.xx.xx.xx:xxxx: wsarecv: An existing connection was forcibly closed by the remote host.
2024-05-06 21:57:53.873 [I] [sub/root.go:160] frpc service for config file [frpc.toml] stopped
login to the server failed: read tcp 192.168.31.140:62182->xx.xx.xx.xx:xxxx: wsarecv: An existing connection was forcibly closed by the remote host.. With loginFailExit enabled, no additional retries will be attempted

Steps to reproduce

...

Affected area

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

[Jiale23]

I try use log.level to show more detail.
It return logs like that

2024-05-06 22:13:48.711 [T] [server/service.go:494] start check TLS connection...
2024-05-06 22:13:48.711 [T] [server/service.go:504] check TLS connection success, isTLS: true custom: false internal: false
2024-05-06 22:13:48.713 [D] [server/service.go:524] Accept new mux stream error: write tcp 172.24.70.133:3834->xx.xx.xx.xx:5223: write: connection reset by peer
2024-05-06 22:14:18.811 [T] [server/service.go:494] start check TLS connection...
2024-05-06 22:14:18.811 [T] [server/service.go:504] check TLS connection success, isTLS: true custom: false internal: false
2024-05-06 22:14:18.814 [D] [server/service.go:524] Accept new mux stream error: write tcp 172.24.70.133:3834->xx.xx.xx.xx:5324: write: connection reset by peer

[xqzr]

#4195