Closed bpolaszek closed 9 months ago
Hi @bpolaszek
I will have to check if the addon is able to reach the /usr folder at all. Until that check is done, could you try the following?
/usr/local/bin/caddy
to /share/caddy/caddy
From your provided logs I can see that the custom caddy binary hasn't been picked up at all. Plus, using the provided path, the add-on may look into the add-on /usr folder, which doesn't hold your custom binary.
Hi @einschmidt,
Thanks for your quick reply.
Indeed after rebooting the /usr/local/bin/caddy
file was removed anyway.
Your solution works! Putting the real caddy
binary at /share/caddy/caddy
did the trick.
Sorry for disturbing. Have a nice day! Ben
Hello there! 👋
I have set up a new HA instance using Home Assistant OS on a RPI4. I'd like to use a custom binary (already built on that same RPI4 using another image and xcaddy) which notably uses the
dns.providers.cloudflare
module but it doesn't seem to be picked by the addon. This binary is located in/usr/local/bin/caddy
and I also symlinked it within/share/caddy/caddy
.Here's the configuration:
And here are the logs (I'm using a custom
Caddyfile
with cloudflare TLS directives):It gets a caddy
2.7.6
which doesn't find thedns.providers.cloudflare
module. However, here's what I get from my terminal:I probably set something wrong, could you help me spot what?