1. Caddy version (caddy version): v2.3.0 2. How I run Caddy: I run Caddy with docker, both Caddys. a. System environment: Docker b. Command: does not apply c. Service/unit/compose file: Caddy, proxy server services: caddy: image: caddy/caddy:alpine volumes: - /opt/docker-co…

[image] kunago: As I said, you were right - there is no domain, hence Caddy cannot ask for a certificate. It should be the Caddy behind proxy quering for the certificates. That’s not really possible with vanilla Caddy. Caddy is an HTTP server, it can’t proxy raw TCP by default. You would need…

I tried something similar like in this case but catch-all simply does not work. [image] Catch-all configuration for unlimited custom domains? Help Thanks for getting back to me. I have changed my config to this: :80,:443 { reverse_proxy https://myapp.herokuapp.com { …

This post is also related, as I see it. [image] What is the order of server parsing Help 1. Caddy version (caddy version): 2.1 2. How I run Caddy: CaddyFile a. System environment: Ubuntu 16.04 3. The problem I’m having: I need to resolve some uncertain do…

[image] kunago: image: caddy/caddy:alpine You should use caddy:2.3.0-alpine, not caddy/caddy. The latter is not the official image, but rather our CI artifacts. [image] kunago: - /opt/docker-common/data/caddy:/data/caddy You should persist /data, not /data/caddy. See the doc…

[image] francislavoie: You should use caddy:2.3.0-alpine, not caddy/caddy. The latter is not the official image, but rather our CI artifacts. You are right, did not know that though. So this is fixed now. [image] francislavoie: You should persist /data, not /data/caddy. See the docs on D…

Oh, thanks for the information. I tried to use Traefik just before but I could not do it either. It does TCP and UDP, but Caddy does not seem to care about the headers. I had it pass the headers over to Caddy. Obviously it would receive it, but with Host empty, while X-Forwarded-Host was properly f…

[image] kunago: header_up Host {http.reverse_proxy.upstream.hostport} This line will set the Host to docker-hosting_caddy_1 [image] kunago: header_up X-Forwarded-Host {host} This line will set X-Forwarded-Host to whatever was originally in the request. If you omit the header_up line …

Alright, thank you very much for explanation and help. As it stands, the best way is not to complicate it, so one Caddy - for proxy and websites. All that is needed, no extra hopping, no extra header issues … I forgot about the KISS concept.

Definitely best to keep it simple here. :+1:

Caddy behind caddy proxy

Help

kunago (Miroslav Abrahám) March 17, 2021, 11:40am 3

This post is also related, as I see it.