port range proxies definition partly gives "start error: status not wait start" after frpc is connected

[ByteCrunch]

Bug Description

I have an issue after frpc is connected to the server with the following configuration:

[...]

[[visitors]]
name = "prdkeycloak"
type = "stcp"
secretKey = "1234567890foobarUser"
serverName = "prdkeycloak"
bindAddr = "0.0.0.0"
bindPort = 5443

{{- range $i, $port := parseNumberRange "49500-50500" }}
[[proxies]]
name = "zzdynprt-test-{{ $port }}"
type = "stcp"
secretKey = "srEbpntamhrlCE5d1TBj1ZHweVSq1QMhSRznshdle-Y"
localIP = "192.168.5.13"
localPort = {{ $port }}
{{- end }}

After successful connection to the frps, I get partly success logs for the port range definition, and also lots of errors:

[...]
2025-11-28 09:02:24.227 [I] [client/control.go:172] [1e63172435c75768] [zzdynprt-test-50498] start proxy success                                                                                   
2025-11-28 09:02:24.227 [I] [client/control.go:172] [1e63172435c75768] [zzdynprt-test-50496] start proxy success                                                                                   
2025-11-28 09:02:24.227 [I] [client/control.go:172] [1e63172435c75768] [zzdynprt-test-50499] start proxy success                                                                                   
2025-11-28 09:02:24.227 [I] [client/control.go:172] [1e63172435c75768] [zzdynprt-test-50500] start proxy success                                                                                   
2025-11-28 09:02:24.227 [W] [client/control.go:170] [1e63172435c75768] [zzdynprt-test-50407] start error: status not wait start, ignore start message                                              
2025-11-28 09:02:24.227 [W] [client/control.go:170] [1e63172435c75768] [zzdynprt-test-50424] start error: status not wait start, ignore start message                                              
2025-11-28 09:02:24.227 [W] [client/control.go:170] [1e63172435c75768] [zzdynprt-test-50438] start error: status not wait start, ignore start message                                              
2025-11-28 09:02:24.227 [W] [client/control.go:170] [1e63172435c75768] [zzdynprt-test-50435] start error: status not wait start, ignore start message
[...]

If I comment out the range definition block at startup, start frpc and let it connect, uncomment the block again and reload the configuration with /opt/frp/bin/frpc reload -c /opt/frp/etc/frpc.toml I don't see any errors.

Is there a general limitation how big a port range can be at startup?

Kind regards
Manuel

frpc Version

v0.65.0

frps Version

v0.64.0

System Architecture

linux/amd64

Configurations

serverAddr = "x.x.x.x"
serverPort = 9000
transport.tcpMux = true # multiplex connections

log.level = "debug"

# webserver needed for hot reload feature
webServer.addr = "127.0.0.1"
webServer.port = 7400

auth.method = "token"
auth.tokenSource.type = "file"
auth.tokenSource.file.path = "/mnt/secrets/token"

loginFailExit = false

[[visitors]]
name = "test"
type = "stcp"
secretKey = "1234567890foobarUser"
serverName = "test"
bindAddr = "0.0.0.0"
bindPort = 5443

{{- range $i, $port := parseNumberRange "49500-50500" }}
[[proxies]]
name = "zzdynprt-test-{{ $port }}"
type = "stcp"
secretKey = "srEbpntamhrlCE5d1TBj1ZHweVSq1QMhSRznshdle-Y"
localIP = "192.168.5.13"
localPort = {{ $port }}
{{- end }}

Steps to reproduce

1. Startup frpc and wait for connection to frps
2. after lots of "start proxy success" messages for the defined range, lots of error lines will appear
   ...

Affected area

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

[fatedier]

When a large number of proxies start simultaneously, there may be some delays and errors, but they should eventually recover automatically.