Synology/Docker - Caddy ogging seems to freeze

[LowerHater]

1. The problem I’m having:

Running Caddy on a Synology NAS, using a Docker container; trying to do the usual troubleshooting of connections; but the Caddy logging seems to stop updating logs with events after a very short while.

Caddy itself continues to run and seems to be functioning (ie. forwarding ports). etc.

Typical output just before it events stop generating here below:

2. Error messages and/or full log output:

{"level":"warn","ts":1738848898.1162095,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":777"}
{"level":"info","ts":1738848898.116231,"logger":"http.log","msg":"server running","name":"srv2","protocols":["h1","h2","h3"]}
{"level":"debug","ts":1738848898.116314,"logger":"http","msg":"starting server loop","address":"[::]:64463","tls":false,"http3":false}
{"level":"warn","ts":1738848898.116352,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":64463"}
{"level":"warn","ts":1738848898.1163745,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":64463"}
{"level":"info","ts":1738848898.1163957,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
{"level":"info","ts":1738848898.2429154,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"}
{"level":"info","ts":1738848898.242995,"msg":"serving initial configuration"}
{"level":"info","ts":1738848898.5164871,"logger":"tls","msg":"storage cleaning happened too recently; skipping for now","storage":"FileStorage:/data/caddy","instance":"9254f734-b765-4629-bac0-36b8b873c21e","try_again":1738935298.5164793,"try_again_in":86399.999997815}
{"level":"info","ts":1738848898.5168884,"logger":"tls","msg":"finished cleaning storage units"}

3. Caddy version:

Caddy 2.91

4. How I installed and ran Caddy:

Installed via Synology Container Manager from Docker Hub

a. System environment:

Synology DS220j - AARM
Running in Docker (Container Manager)

b. Command:

Started in Container Manager

caddy run --config /etc/caddy/Caddyfile --adapter caddyfile

c. Service/unit/compose file:

Created via Synology Container Manager UI

d. My complete Caddy config:

{
  email david@coolvibe.se
  log {
    output file /data/caddy/logs/caddy.log 
    level debug
  }
  admin localhost:2019
}

:777 {
    reverse_proxy 100.111.116.28:777
}

:64463 {
    reverse_proxy 100.111.116.28:64463
}

:64466 {
    reverse_proxy 100.111.116.28:64466
}

5. Links to relevant resources:

[TheRettom (Riley M)]

You need to add debug to your global parameters. Like this:

{
  debug
  email david@coolvibe.se
  log {
    output file /data/caddy/logs/caddy.log 
    level debug
  }
  admin localhost:2019
}

If the log isn’t updating after startup, then it may not be receiving any requests because it’s being dropped before it hits Caddy. A firewall could do that.