No connection could be made because the target machine actively refused it #4970
Description
Bug Description
I think the parameters of this configuration file really need to be sorted out. The complete configuration update was two years ago. Or because it is a window, the parameters are not recognized in camel case naming
It's really misleading
frpc Version
0.64.0
frps Version
0.64.0
System Architecture
window server 2025
Configurations
Misconfiguration：
[common]
serverAddr = "47.x.x.x"
serverPort = 7000
loginFailExit = false
log.to = "./frpc.log"
log.level = "debug"
log.maxDays = 3
auth.method = "token"
token = "1K02kgan"
[web1]
name = "web1"
type = "tcp"
localIP = "192.168.0.101"
localPort = 8080
remotePort = 3001
Correct configuration:
[common]
server_addr = "47.238.x.x"
server_port = 7000
loginFailExit = false
log.to = "./frpc.log"
log.level = "debug"
log.maxDays = 3
auth.method = "token"
token = "1K02kgan"
[web1]
name = "web1"
type = "tcp"
local_ip = "127.0.0.1"
local_port = 8080
remote_port = 3001
Logs
No connection could be made because the target machine actively refused it.. 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