[Feature Request] Allow customization of TLS server name (SNI) in ServersTransport #1647

Closed
opened 2026-04-05 19:38:17 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @4nx on 4/2/2025

Background:
When using Pangolin in setups involving multiple reverse proxies (such as Traefik in a two-tier reverse proxy configuration), the server name used during the TLS handshake (SNI) to backend servers is currently not configurable and not set. As reported in Issue #207, this limitation causes TLS handshake failures because the backend reverse proxy does not receive the correct server name via SNI and thus cannot select the appropriate certificate.

Proposed Enhancement:
Implement an option within Pangolin's configuration to explicitly specify the TLS server name used during the connection establishment with backend services (ServersTransport). This would allow users to define a custom SNI value, ensuring proper TLS handshakes in scenarios involving multiple reverse proxies.

Benefits:

  • Resolves TLS handshake failures by ensuring correct SNI is passed to backend services.
  • Enables smoother integration with multi-layer reverse proxy setups.
  • Provides greater flexibility and robustness for advanced network configurations.

Related Issues:
Directly addresses problems discussed in Issue #207, specifically regarding TLS handshake errors caused by incorrect or missing SNI information.

*Originally created by @4nx on 4/2/2025* **Background:** When using Pangolin in setups involving multiple reverse proxies (such as Traefik in a two-tier reverse proxy configuration), the server name used during the TLS handshake (SNI) to backend servers is currently not configurable and not set. As reported in [Issue #207](https://github.com/fosrl/pangolin/issues/207), this limitation causes TLS handshake failures because the backend reverse proxy does not receive the correct server name via SNI and thus cannot select the appropriate certificate. **Proposed Enhancement:** Implement an option within Pangolin's configuration to explicitly specify the TLS server name used during the connection establishment with backend services (ServersTransport). This would allow users to define a custom SNI value, ensuring proper TLS handshakes in scenarios involving multiple reverse proxies. **Benefits:** * Resolves TLS handshake failures by ensuring correct SNI is passed to backend services. * Enables smoother integration with multi-layer reverse proxy setups. * Provides greater flexibility and robustness for advanced network configurations. **Related Issues:** Directly addresses problems discussed in [Issue #207](https://github.com/fosrl/pangolin/issues/207), specifically regarding TLS handshake errors caused by incorrect or missing SNI information.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1647