HTTP & HTTPS
FRP Auto Deploy publishes HTTP and HTTPS as TCP services. It is not an application-layer reverse proxy for the published service.
HTTP path
Example targets:
HTTPS path: TLS stays encrypted through FRP
FRP Auto Deploy does not terminate, replace, or automatically issue the target application’s TLS certificate.
DNS hostname and certificate
Suppose:
Users connect to:
The certificate presented by the target application must be valid for fw.example.com where hostname verification applies.
Multiple web services on one client
Give each service a stable Service ID so later lifecycle and target changes remain unambiguous.
Common failure patterns
First prove the target is reachable from the FRP client. Then prove the public service port is reachable. Treat DNS and TLS hostname validation as later layers.