[GH-ISSUE #4873] Set vhostHTTP(s)Port == bindPort, login failed

gitea-mirror commented

2026-05-05 14:27:26 -06:00

Owner

Originally created by @Streamlet on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4873

Bug Description

Set vhostHTTP(s)Port == bindPort, login failed

frpc Version

0.63

frps Version

0.63

System Architecture

frps:linux/amd64, frpc:windows/amd64

Configurations

frps.toml:

bindPort = 57000
#vhostHTTPPort = 57000
vhostHTTPSPort = 57000

frpc.toml:

serverAddr = "<server ip>"
serverPort = 57000

[[proxies]]
name = "https"
type = "https"
localIP = "<local ip>"
localPort = <local port>
customDomains = ["<domain name>"]

Logs

No response

Steps to reproduce

...

Affected area

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

Originally created by @Streamlet on GitHub (Jul 9, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4873 ### Bug Description Set vhostHTTP(s)Port == bindPort, login failed ### frpc Version 0.63 ### frps Version 0.63 ### System Architecture frps:linux/amd64, frpc:windows/amd64 ### Configurations frps.toml: ```toml bindPort = 57000 #vhostHTTPPort = 57000 vhostHTTPSPort = 57000 ``` frpc.toml: ```toml serverAddr = "<server ip>" serverPort = 57000 [[proxies]] name = "https" type = "https" localIP = "<local ip>" localPort = <local port> customDomains = ["<domain name>"] ``` ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:27:26 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:27:28 -06:00

Author

Owner

@Streamlet commented on GitHub (Jul 9, 2025):

I have found out the reason:

frp control messages are tls encrypted since a certain version,
so the HTTPS mux receives the packets begin with 0x16

@Streamlet commented on GitHub (Jul 9, 2025): I have found out the reason: frp control messages are tls encrypted since a certain version, so the HTTPS mux receives the packets begin with 0x16

gitea-mirror commented

2026-05-05 14:27:30 -06:00

Author

Owner

@fatedier commented on GitHub (Jul 9, 2025):

https://github.com/fatedier/frp?tab=readme-ov-file#tls

@fatedier commented on GitHub (Jul 9, 2025): https://github.com/fatedier/frp?tab=readme-ov-file#tls

gitea-mirror commented

2026-05-05 14:27:30 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 25, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jul 25, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.