[GH-ISSUE #4936] [Feature Request] HTTPS Load Balancing Support #3893

Closed
opened 2026-05-05 14:29:05 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @jeet0733 on GitHub (Aug 15, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4936

Describe the feature request

Feature Request: HTTPS Load Balancing Support

Description

Add support for load balancing across multiple HTTPS backend services using group-based routing, similar to the existing HTTP load balancing functionality. I have developed it, kindly approve this feature and I will submit the PR.

Currently, frp supports:

  • HTTP load balancing with groups
  • TCP load balancing with groups
  • Basic HTTPS proxy (single backend)
  • HTTPS load balancing with groups (missing)

This feature request adds the missing HTTPS load balancing capability.

Implementation Approach

  • New HTTPS group controller for managing grouped HTTPS proxies
  • Enhanced HTTPS proxy with group registration/load balancing
  • HTTPS reverse proxy for group-based routing with SNI support
  • Integration with existing health check system
  • Round-robin distribution across healthy backends

Use Cases

  • High availability HTTPS services with multiple backends
  • Horizontal scaling of HTTPS applications
  • Load distribution for SSL-terminated services
  • Seamless failover for HTTPS endpoints

Configuration Example

[[proxies]]
name = "https_app_1"
type = "https"
localPort = 443
customDomains = ["app.example.com"]
loadBalancer.group = "https_app"
loadBalancer.groupKey = "secret123"
healthCheck.type = "tcp"

[[proxies]]
name = "https_app_2" 
type = "https"
localPort = 8443
customDomains = ["app.example.com"]
loadBalancer.group = "https_app"
loadBalancer.groupKey = "secret123"
healthCheck.type = "tcp"

Benefits

  • Completes the load balancing feature set (HTTP/TCP/HTTPS/TCPMUX)
  • Maintains consistency with existing HTTP load balancing patterns
  • Enables high availability HTTPS deployments
  • Preserves end-to-end SSL encryption

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @jeet0733 on GitHub (Aug 15, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4936 ### Describe the feature request ## Feature Request: HTTPS Load Balancing Support ### Description Add support for load balancing across multiple HTTPS backend services using group-based routing, similar to the existing HTTP load balancing functionality. **I have developed it, kindly approve this feature and I will submit the PR.** Currently, frp supports: - ✅ HTTP load balancing with groups - ✅ TCP load balancing with groups - ✅ Basic HTTPS proxy (single backend) - ❌ HTTPS load balancing with groups (missing) This feature request adds the missing HTTPS load balancing capability. ### Implementation Approach - New HTTPS group controller for managing grouped HTTPS proxies - Enhanced HTTPS proxy with group registration/load balancing - HTTPS reverse proxy for group-based routing with SNI support - Integration with existing health check system - Round-robin distribution across healthy backends ### Use Cases - High availability HTTPS services with multiple backends - Horizontal scaling of HTTPS applications - Load distribution for SSL-terminated services - Seamless failover for HTTPS endpoints ### Configuration Example ```toml [[proxies]] name = "https_app_1" type = "https" localPort = 443 customDomains = ["app.example.com"] loadBalancer.group = "https_app" loadBalancer.groupKey = "secret123" healthCheck.type = "tcp" [[proxies]] name = "https_app_2" type = "https" localPort = 8443 customDomains = ["app.example.com"] loadBalancer.group = "https_app" loadBalancer.groupKey = "secret123" healthCheck.type = "tcp" ``` ### Benefits - Completes the load balancing feature set (HTTP/TCP/HTTPS/TCPMUX) - Maintains consistency with existing HTTP load balancing patterns - Enables high availability HTTPS deployments - Preserves end-to-end SSL encryption ### Describe alternatives you've considered _No response_ ### Affected area - [x] Docs - [ ] Installation - [x] Performance and Scalability - [ ] Security - [x] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [x] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:29:05 -06:00
  • closed this issue
  • added the
    proposal
    label
Author
Owner

@fatedier commented on GitHub (Aug 15, 2025):

Sounds good, please go ahead and submit the PR referencing this issue.

<!-- gh-comment-id:3190808131 --> @fatedier commented on GitHub (Aug 15, 2025): Sounds good, please go ahead and submit the PR referencing this issue.
Author
Owner

@jeet0733 commented on GitHub (Aug 26, 2025):

@fatedier I have resolved all your and copilot comments on the PR. Kindly review and merge.

<!-- gh-comment-id:3223282014 --> @jeet0733 commented on GitHub (Aug 26, 2025): @fatedier I have resolved all your and copilot comments on the PR. Kindly review and merge.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3893
No description provided.