Repository navigation
Closed
Labels
backendServer-side codeServer-side codecaddyCaddy-specificCaddy-specificcrowdsecCrowdSec integrationCrowdSec integrationsslSSL/TLS certificatesSSL/TLS certificatestestingTest suiteTest suite
Description
Here are the logs from my container -
Charon v0.51.0 (commit d034513951edebbdb2840e1e5bbd51b3b8491799, built 2026-11-16T21:15:57Z)
Docker Compose, non-root container, CrowdSec disabled in settings
--- startup ---
{"level":"info","msg":"starting Charon backend on version 0.51.0 (commit: d034513951edebbdb2840e1e5bbd51b3b8491799, built: 2026-11-16T21:15:57.152Z)","time":"2026-11-17T00:41:55Z"}
{"level":"warning","msg":"CHARON_EMERGENCY_TOKEN not set - emergency bypass disabled","time":"2026-11-17T00:41:55Z"}
{"level":"info","msg":"auth throttle: login 10/600s, session 60/60s per client; trusted proxies: 0","time":"2026-11-17T00:41:55Z"}
--- every proxy host is skipped (repeated ~70 times, one per host UUID) ---
{"host":"689cdc87-xxxx-xxxx-xxxx-xxxxxxxxxxxx","level":"warning","msg":"Skipping proxy host: its forward target is not permitted by this proxy","time":"2026-11-17T00:41:57Z"}
{"host":"8810016e-xxxx-xxxx-xxxx-xxxxxxxxxxxx","level":"warning","msg":"Skipping proxy host: its forward target is not permitted by this proxy","time":"2026-11-17T00:41:57Z"}
{"host":"29806fcb-xxxx-xxxx-xxxx-xxxxxxxxxxxx","level":"warning","msg":"Skipping proxy host: its forward target is not permitted by this proxy","time":"2026-11-17T00:41:57Z"}
... (same message for all remaining hosts)
--- resulting Caddy config is tiny ---
{"level":"info","ts":1794876117.2874544,"logger":"admin.api","msg":"received request","method":"POST","host":"localhost","uri":"/load","headers":{"Content-Length":["11991"],"Content-Type":["application/json"]}}
{"level":"info","ts":1794876117.2998126,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["svc1.example.com","svc2.example.com","svc3.example.com","svc4.example.net","site.example.org","apprise.example.net","svc5.example.com","svc6.example.net","svc7.example.net","www.site.example.org"]}
{"level":"info","msg":"Successfully applied initial Caddy config","time":"2026-11-17T00:41:57Z"}
--- sample 502 from the one remaining host (upstream is 127.0.0.1) ---
{"level":"error","ts":1794876143.2258716,"logger":"http.log.error.access_log","msg":"dial tcp 127.0.0.1:3038: connect: connection refused","request":{"remote_ip":"203.0.113.10","client_ip":"203.0.113.10","proto":"HTTP/2.0","method":"GET","host":"apprise.example.net","uri":"/notify/[REDACTED]"},"duration":0.000485083,"status":502,"err_id":"mzitq3rh2"}
Going back to v0.50.0 instantly fixes it for me, so it is def a latest version problem
Metadata
Metadata
Assignees
Labels
backendServer-side codeServer-side codecaddyCaddy-specificCaddy-specificcrowdsecCrowdSec integrationCrowdSec integrationsslSSL/TLS certificatesSSL/TLS certificatestestingTest suiteTest suite
Projects
- StatusShow more project fieldsDone
Activity
Wikid82 commentedon Nov 17, 2026
Thanks for the report, and for including the logs. They point at the cause.
v0.51.0 added a check on forward targets when the Caddy config is built. A host whose target fails the check is left out of the config, with the warning you're seeing. The check doesn't stop at the host you were working on. One refused target leaves out just that host, and the rest still load. Seeing about 70 hosts skipped at once means something they share is being refused. I can't tell what from the logs, because they only show host UUIDs.
A forward target is refused in these cases:
orthrus:...).To narrow it down, could you tell me:
host.docker.internal, or the Docker gateway IP.172.17.0.1orhost.docker.internal, on port 8080 or another common port?If you can, run this against the data directory with the container stopped, or through
docker execwith a SQLite client. It lists the stored targets without the domains:Rolling back to v0.50.0 was the right workaround for now. I'll keep this open and look into it once I have those details.
driftywinds commentedon Nov 17, 2026
almost all of my proxy hosts use
0.0.0.0as the forward host with a per-service port, for example:0.0.0.0:30380.0.0.0:[port]0.0.0.0:[port]no Docker container names, no
host.docker.internal, and no172.17.0.1. The services run on the same machine as Charon and publish their ports on the host.Forwarding to the Docker host itself?
no. everything is
0.0.0.0:<port>. There might be some using 127.0.0.1Advanced Config
nope
Host types
plain proxy hosts only, no Orthrus agents.
Docker network mode
host
Wikid82 commentedon Nov 17, 2026
That explains it, thank you.
0.0.0.0is the "unspecified" address, and the v0.51.0 forward target check treats it as a blocked address. The check allows loopback (127.0.0.1) and private LAN ranges, but0.0.0.0isn't in either group. So every host using it is left out. Any host on127.0.0.1stays, which matches your single remaining host. On Linux, connecting to0.0.0.0reaches this machine, so it behaved like loopback before, and this is a regression rather than intended behaviour.Workaround until a fix ships: change the forward host on those hosts from
0.0.0.0to127.0.0.1(same ports). Or stay on v0.50.0.I'm working on a fix that treats
0.0.0.0the same as loopback for forward targets. I'll link the PR here.driftywinds commentedon Nov 17, 2026
Can I update freely, will it auto handle 0.0.0.0
Wikid82 commentedon Nov 17, 2026
Yes, you can update freely. v0.51.1 includes the fix (#2000), so
0.0.0.0forward targets are handled automatically. Your stored hosts don't need editing, and you can keep0.0.0.0as the forward host. After the upgrade, all your hosts should load again on startup and the "Skipping proxy host" warnings should be gone.Two things to know:
0.0.0.0like127.0.0.1, so it is still refused on ports Charon keeps for itself (the Caddy admin port, the emergency server port, the bundled CrowdSec port and agent proxy ports). A service on one of those ports would still be skipped. If you see any "Skipping" warnings after upgrading, tell me the port.0.0.0.0. If you use them on these hosts, use127.0.0.1for the monitor target.Thanks for the clear logs and for answering so quickly. Let me know if anything is still skipped after the upgrade.