Automatic HTTPS & Reloads

1. The problem I’m having:

I have a question re: exponential backoffs with SSL certs. I’m trying to clarify the language from this doc: Automatic HTTPS — Caddy Documentation where it says:

“To avoid leaking resources, Caddy aborts in-flight tasks (including ACME transactions) when config is changed. While Caddy is capable of handling frequent config reloads, be mindful of operational considerations such as this, and consider batching config changes to reduce reloads and give Caddy a chance to actually finish obtaining certificates in the background.”

I’m using the API to add new 301s to multiple sites, add new sites, etc. Are these considered a “config reloads”?

It says before that “Caddy aborts in-flight tasks (including ACME transactions) when config is changed.”, does a config being changed include adding new entries via the API?

2. Error messages and/or full log output:

No specific errors.

3. Caddy version:

v2.7.5

4. How I installed and ran Caddy:

a. System environment:

Ubuntu

b. Command:

caddy run --resume

c. Service/unit/compose file:

d. My complete Caddy config:

Caddy is fine, just have the above question.

5. Links to relevant resources:

Yes, any change to the config causes a reload.

Please use the latest version, v2.8.4

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.