[GH-ISSUE #3656] same port for `bindPort` and `vhostHTTPSPort` issue, dashboard https proxy issue #2911

New issue

Closed

opened 2026-05-05 13:52:47 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 13:52:47 -06:00

Owner

Originally created by @abdeldjalil-fellah on GitHub (Oct 10, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3656

# frpc.toml (v0.52.0)

serverAddr = "tunnel.example.com"
serverPort = 5117
user = "user_name"
metadatas.token = "token1"

[[proxies]]
name = "proxy_name"
type = "https"
localIP = "127.0.0.1"
localPort = 3112
subdomain = "test1"
transport.useCompression = false

# frps.toml (v0.52.0)

bindAddr = "0.0.0.0"
bindPort = 5117
vhostHTTPSPort = 5116
subDomainHost = "tunnel.example.com"

webServer.addr = "0.0.0.0"
webServer.port = 5115
webServer.user = "admin"
webServer.password = "admin"

[[httpPlugins]]
name = "client-authenticator"
addr = "https://login.example.com"
path = "/api/tunnel/auth-frpc"
ops = ["Login"]
#tlsVerify = false

1st issue: using the same port for bindPort and vhostHTTPSPort generates:

frpc : 2023/10/10 12:06:17 [W] [service.go:131] login to server failed: session shutdown
frps : 2023/10/10 14:35:08 [D] [vhost.go:216] http request for host [tunnel.example.com] path [] httpUser [] not found

2nd issue: using different ports for bindPort and vhostHTTPSPort fixes the first issue but generates:

frps: 2023/10/10 14:19:11 [W] [dashboard_api.go:214] unmarshal proxy [user_name.proxy_name] conf info error: unknown plugin type:

an open proxy is not listed in the dashboard ui until it is closed

Originally created by @abdeldjalil-fellah on GitHub (Oct 10, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3656 ``` # frpc.toml (v0.52.0) serverAddr = "tunnel.example.com" serverPort = 5117 user = "user_name" metadatas.token = "token1" [[proxies]] name = "proxy_name" type = "https" localIP = "127.0.0.1" localPort = 3112 subdomain = "test1" transport.useCompression = false ``` ``` # frps.toml (v0.52.0) bindAddr = "0.0.0.0" bindPort = 5117 vhostHTTPSPort = 5116 subDomainHost = "tunnel.example.com" webServer.addr = "0.0.0.0" webServer.port = 5115 webServer.user = "admin" webServer.password = "admin" [[httpPlugins]] name = "client-authenticator" addr = "https://login.example.com" path = "/api/tunnel/auth-frpc" ops = ["Login"] #tlsVerify = false ``` - 1st issue: using the same port for `bindPort` and `vhostHTTPSPort` generates: ``` frpc : 2023/10/10 12:06:17 [W] [service.go:131] login to server failed: session shutdown frps : 2023/10/10 14:35:08 [D] [vhost.go:216] http request for host [tunnel.example.com] path [] httpUser [] not found ``` - 2nd issue: using different ports for `bindPort` and `vhostHTTPSPort` fixes the first issue but generates: ``` frps: 2023/10/10 14:19:11 [W] [dashboard_api.go:214] unmarshal proxy [user_name.proxy_name] conf info error: unknown plugin type: ``` an open proxy is not listed in the dashboard ui until it is closed

gitea-mirror closed this issue

2026-05-05 13:52:49 -06:00

gitea-mirror commented

2026-05-05 13:52:50 -06:00

Author

Owner

@fatedier commented on GitHub (Oct 11, 2023):

doc here. If you want to use same port for bindPort and vhostHTTPSPort, you should set transport.tls.disableCustomTLSFirstByte to false. (There is a bug here, I will fix it later)
The issue is same with https://github.com/fatedier/frp/issues/3658, track it there and I will fix it.

@fatedier commented on GitHub (Oct 11, 2023): 1. [doc](https://github.com/fatedier/frp#tls:~:text=For%20port-,multiplexing,-%2C%20frp%20sends%20a) here. If you want to use same port for `bindPort` and `vhostHTTPSPort`, you should set `transport.tls.disableCustomTLSFirstByte` to false. (There is a bug here, I will fix it later) 2. The issue is same with https://github.com/fatedier/frp/issues/3658, track it there and I will fix it.