I’m new to Caddy and have been trying to install it with a fe plugins for the last 24 hours, to no avail. I’ve finally thoroughly read this post and decided to install it barebones, now with success.
But… Is there a way to know which plugins are compatible with the new requirements (the Go platform) and that we can install right now ?
At the moment, there’s no official list right now of what plugins do or don’t work. All we have are scattered user reports for broken builds, especially by some users with (very) large numbers of plugins.
Your best bet right now is to jump on the download page and do some trial and error.
Better yet, file issues with the plugins that do not build with Caddy 1.0.0, and see if the developers of those plugins will look into it. They might not be aware that something needs to be changed. Might have to do with modules.
There’s a chance it could be a bug in our build server but since some plugins work, it’s hard to tell off-hand.
Thank you, now I’ll test the plugins I want one by one.
Slightly off-topic: could you, by any chance, please point me to a simple and proper way to install extensions after I’ve installed Caddy ? I’ve yet to find a nice tuto somewhere. I’m self-taught in all this and I’m afraid to break things that already work on my VPS;)
You can’t add plugins to an existing Caddy binary, so you’ll need to grab a new binary to replace the old one.
Once you’ve downloaded / built the new binary, you can just put it on top of where the old one was, with the same name. Then, run pkill -SIGUSR2 caddy to tell Caddy to gracefully reload with the updated binary.
I’ve been able to at least build most of my usual Caddy plugins with exception of Azure and Restic Caddy v1.0.0 build minus Azure & Restic plugins - whether they all 100% is another story operation wise. This is outside of caddy’s official download site though by building own custom caddy binaries.