Ferron 3 automatic tls issues

[DoctorRainer]

cache "/var/cache/ferron-acme" is not set by default anymore, this led me to hitting rate limit and unable to get the new certificates in a week. This was unexpected and let to a bit of frustration.

Also, I have a question:

*.domain.com {
    tls {
        provider acme
        challenge http-01
        contact "drryner@icloud.com"
        cache "/var/cache/ferron-acme"
    }
}

Will this work as I expect it to work? Or do I have to copy this for each and ever example1, example2.domain.com?

[DoctorRainer]

Also, the error "[2026-05-24 20:14:58.097 WARN] Error during TLS handshake: unexpected error: no server certificate chain resolved" is not really helpful, caddy includes the response from the provider if they refuse a certificate

[xaner4]

I'm using snippets to get automatic TLS for each single endpoints, like this:

snippet cf_tls {
    tls {
        provider "acme"
        challenge "dns-01"
        contact "post@example.com"
        dns {
            provider cloudflare
            api_key "cf_APIKEY............."
        }
        cache "/var/cache/ferron-acme/"
    }
}

todo.example.com {
  use cf_tls
  proxy {
    upstream "http://vikunja:3456"
  }
}

[DorianNiemiecSVRJS]

cache "/var/cache/ferron-acme" is not set by default anymore, this led me to hitting rate limit and unable to get the new certificates in a week. This was unexpected and let to a bit of frustration.

I think if you're running Ferron 3 as an user with home directory (like root), /var/cache/ferron-acme isn't set by default... I'm be going to fix that...

[DorianNiemiecSVRJS]

*.domain.com {
    tls {
        provider acme
        challenge http-01
        contact "drryner@icloud.com"
        cache "/var/cache/ferron-acme"
    }
}

For this, HTTP-01 isn't going to work (wildcard domains aren't supported by this challenge). I recommend using DNS-01 challenge instead...

[DorianNiemiecSVRJS]

I just added the automatic TLS-related fixes (default cache path prioritization, TLS resolver error reporting) to the development branch of Ferron 3 (develop-3.x), so the fixes will be available in the next release of Ferron 3.