[GH-ISSUE #2600] [Feature Request] Make Frps behind Nginx for HTTPS connections.

gitea-mirror commented

2026-05-05 13:20:06 -06:00

Owner

Copy link

Originally created by @zhrtc on GitHub (Oct 4, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2600

Describe the feature request

My working environment only allows normal HTTP and HTTPS connections (Firewall has connect filters) to connect port 80 and 443 whereas my server's port 443 had already been occupied by Nginx so that I had to add an extra proxy layer by V2ray via WebSocket with TLS to proxy the frp data stream.

It would be appreciated if the Author could add an option for this in the config file to disable this"0x17" feature.

Thanks.

Describe alternatives you've considered

I understood that Frp also use normal https connections but an extra byte of 0x17 would be added as the first byte of the TLS stream for its own port multiplexing. I've tried to the remove this feature in the source code (3 locations I found) but the connection had been broken and could not connect anymore so I'm not sure whether there any other modifications were required to get this available.

Affected area

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

Originally created by @zhrtc on GitHub (Oct 4, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2600 ### Describe the feature request My working environment only allows normal HTTP and HTTPS connections (Firewall has connect filters) to connect port 80 and 443 whereas my server's port 443 had already been occupied by Nginx so that I had to add an extra proxy layer by V2ray via WebSocket with TLS to proxy the frp data stream. It would be appreciated if the Author could add an option for this in the config file to disable this"0x17" feature. Thanks. ### Describe alternatives you've considered I understood that Frp also use normal https connections but an extra byte of 0x17 would be added as the first byte of the TLS stream for its own port multiplexing. I've tried to the remove this feature in the source code (3 locations I found) but the connection had been broken and could not connect anymore so I'm not sure whether there any other modifications were required to get this available. ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [X] Extensions - [X] Others

gitea-mirror

2026-05-05 13:20:06 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:20:09 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Nov 4, 2021):

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

@github-actions[bot] commented on GitHub (Nov 4, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified