Is that all the logs you have? That only looks like the logs from Caddy’s startup, and nothing else after.
Try enabling the debug global option, it might show more.
FYI, Caddy’s reverse_proxy is HTTP by default. If you mean to proxy over HTTPS, you should use the https:// scheme, and also override the Host header. See the docs:
This will make Caddy listen for HTTP on whatever port that is.
(In that case, the email global option doesn’t do anything for you.)
This tells Caddy to try to automate issuance of a certificate for analytics.openfort.xyz.
Which one is your intent? Did you want Caddy to handle TLS? Or just unencrypted HTTP traffic?
I don’t know how Cloud Run works. Does it act as an HTTP proxy itself? Does it handle any of your traffic? Or do they just give you an IP address for your running container that you point your domain to?