Working with caddy behind another proxy

Developer help Self-hosting
1

How can I circumvent Caddy trying to get a TLS certificate for my domain? I already have a proxy handling HTTPS. Will the ghost container accept HTTP traffic on port 2368?

I am using cloudflared to route from my domain to my server and to proxy HTTPS into HTTP traffic. My server runs my HTTPS proxy cloudflared and the ghost containers on a virtual bridge network.

While setting up my blog, when visiting my domain, I get an error presented by Firefox:
”
The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

  • This problem can sometimes be caused by disabling or refusing to accept cookies.

“

I notice in my Caddy container’s log file

{“level”:“error”,“ts”:1764155076.2586575,“logger”:“tls.obtain”,“msg”:“could not get certificate from issuer”,“identifier”:“blogadmin.fetzner.me”,“issuer”:“acme-v02.api.letsencrypt.org-directory”,“error”:“HTTP 429 urn:ietf:params:acme:error:rateLimited - too many failed authorizations (5) for “blogadmin.fetzner.me” in the last 1h0m0s, retry after 2025-11-26 11:13:12 UTC: see Rate Limits - Let's Encrypt}

I see Caddy is trying to get a TLS certificate for my domain and failing.
Since I already have proxying handled by another service, can I just router HTTP traffic directly into ghost on port 2368 I see listed in the caddyfile?

2

I determined that yes, the ghost container will accept HTTP traffic on port 80 if I route it so; on both the primary domain and the admin domain.
I also noticed the routing for the admin domain and primary domain go to the same port, so I am under the assumption there are no concerns there, but I’m curious if this is best practice.

3

Best practice is for the admin domain to be at a separate URL. This provides added protection against javascript injection that might otherwise allow a low-level staff member to cause the site owner’s browser to take an unexpected admin action.