That depends on what your error is. It’s not a magic process, it just tries to help you with formatting. The validate is the magic, it helps you spot errors as you make them.

If you’re using git to version Caddy configuration, you can use a pre-commit hook to test it, ensuring that you’ll never have invalid configuration. That’s what I do.

caddy validate

There’s some extra command args that may be necessary but that should be an adequate first step.

Did you have a mistake in your caddyfile? Or, what led to this? I'm using caddy as well and could be good to know, though I don't recall seeing that warning.

I have switched production to Caddy before V2 and haven't looked back ever since. During my Apache era, always had to keep a eye on stuff and deal when things decided to break With caddy? I just throw the config and it just works without complaining at all

I did some bad formatting during my initial setup of caddy. Having the formater is really handy.

Been using nginx, probably should change just because my mail uses letsencyrot while my http uses bought certs.

Letsencrypt has gone far enough that we can just rely on it now apparently.

I like to use a justfile to do this all in one fell swoop;

default:
  just --list

caddy-refresh:
  caddy fmt --overwrite ~/.caddy
  caddy validate --config /etc/caddy/Caddyfile -a caddyfile
caddy-reload: caddy-refresh
  doas docker exec -it caddy caddy reload --config /etc/caddy/Caddyfile

~/.caddy is my caddyfile, which is system linked to /etc/caddy/Caddyfile. Doing it this way ensures there are no permission issues, and you don't need sudo to edit your caddyfile. So you simply nvim ~/.caddy, make your changes, and then run just caddy-reload, which runs caddy-refresh before reloading the caddy config via docker.

Works great, and only involves one command.

Thank you! I've been ignoring that error, assuming that it was just about indentation.

Also I appreciate your use of the word "thusly" immediately after the word "tho."

Wait. I got the format warning in caddy, so does this mean it could contain substantial error? I gotta check

My ingress firewall blocks the cert renewal challenge requests because they always come from countries that I blanket block, which requires me to keep an eye on it and disable blocking on certain countries to allow the renewals to happen, then re-enable blocking.. Let's Encrypt (somewhat understandably) doesn't publish the list of IPs that they will use for the challenge requests, so I'm not sure if there's a better solution. Anyone dealt with this?

Cool. You got lucky. This is covered in the docs and is normal behavior.

The problems arise when this exchange doesn't happen without issue though.