Unfortunately, yes you’ll need to shut down your Caddy server and start it again with the new binary when upgrading versions. This is something we hope to be able to improve in a future version, making binary hotswaps functional.
As for that specific error message, this should answer your question:
Thanks for getting back to me so promptly guys
Yeah I figured that this would be the case. I kind of thought that there was some Golang magic for inplace upgrades.
I’ll schedule a downtime and then update the binary.
RE the error message: I was expecting that and just put it in here so folks who run the same command to update caddy will end up here trying to reduce dups