Reverse Proxy Config Getting ERR_SSL_PROTOCOL_ERROR

[francislavoie]

@Kidsnd274

I use port 443 for another application, so setting it to port forward to caddy isn’t really an option

You could instead have that other service run on a different port, then proxy to it using Caddy.

I recommend using a subdomain for each service instead of subpaths as you currently have. It’s more flexible and reliable. See:

The "subfolder problem", OR, "why can't I reverse proxy my app into a subfolder?"

Have you ever tried to reverse proxy an app into its own little subfolder of your domain name? Makes things neat, doesn’t it? Using example.com/foo/ for one app, example.com/bar/ for another. If you’re coming here from one of the selfhosted communities, you might be thinking along the lines of example.com/sonarr/, example.com/radarr/ etc. Chances are, you’ve tried some configuration along these lines: example.com { redir /sonarr /sonarr/ handle_path /sonarr/* { reverse_proxy localhost…

@Kidsnd274

Okay nevermind. So my Asus router helps me get a certificate from Let’s Encrypt. All I have to do is use the tls directive to point caddy to the cert.pem and key.pem files.

That’s fine too I guess. But Caddy’s ACME client is probably much higher quality.