tls2raw plugin doesn't work, getting remotePort isn't defined during startup.

[JiachenRen]

Bug Description

In order to use the new tls2raw plugin, you would have to specify remotePort under [[proxies]] session, however during config validation it complains that remotePort isn't defined.

frpc Version

0.60.0

frps Version

0.60.0

System Architecture

linux/amd64

Configurations

frpc.toml

serverAddr = "..."
serverPort = "..."

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

transport.poolCount = 5

transport.tls.enable = true
transport.tls.certFile = "..."
transport.tls.keyFile = "..."
transport.tls.disableCustomTLSFirstByte = false

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

[[proxies]]
name = "..."
type = "https"
remotePort = 11001

[proxies.plugin]
type = "tls2raw"
localAddr = "127.0.0.1:11001"
crtPath = "..."
keyPath = "..."

[[proxies]]
name = "..."
type = "tcp"
localIP = "127.0.0.1"
localPort = 3478
remotePort = 3478

[[proxies]]
name = "..."
type = "udp"
localIP = "127.0.0.1"
localPort = 3478
remotePort = 3478

[[proxies]]
name = "nextcloud"
type = "https"
customDomains = ["..."]

[proxies.plugin]
type = "https2http"
localAddr = "127.0.0.1:11000"
crtPath = "..."
keyPath = "..."
hostHeaderRewrite = "127.0.0.1"
requestHeaders.set.x-from-where = "frp"

Logs

frp ./frpc verify -c frpc.toml

unmarshal ProxyConfig error: json: unknown field "remotePort"

Steps to reproduce

1. Write a https proxy with tls2raw plugin and custom remotePort (as specified in https:/fatedier/frp/blob/2855ac71e3fc3fb2859f4c75f97f97e99f131f1b/conf/frpc_full_example.toml)
2. frpc complains that remotePort isn't defined.

Affected area

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

[fatedier]

remotePort not for https proxy