Unable to get https reverse tunnel working about frp HOT 3 CLOSED

Kind of solved (hours passed on it...): I needed the frps container with a dns alias to the same as the request hostname, and remote caddy must target this dns alias instead of the IP.

It would be great that frp sets this hostname automagically, because I don't know how to do with wildcards.

from frp.

Obviously, you should configure the correct SNI name (host) for caddy to forward HTTPS requests, rather than using the IP. I think this is a common configuration for reverse proxy functionality.

For https, frps has no modifications to the request.

from frp.

I fixed it with overriding the SNI... The param and the workflow is not that clear when we are new to tls/https world.

from frp.