You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
time="2018-08-24T13:10:46Z" level=error msg="Unable to obtain ACME certificate for domains \"foo.com\" detected thanks to rule \"Host:foo.com\" : unable to generate a certificate for the domains [foo.com]: acme: Error -> One or more domains had a problem:\n[foo.com] invalid KeyType: \n"
Output of traefik version: (What version of Traefik are you using?)
17.0.rc3
What is your environment & configuration (arguments, toml, provider, platform, ...)?
kubernetes helm chart with acme.json config. Single instance
ACME enabled, challenge type: http-01
The issue is related to #3319. In my acme.json my KeyType string was empty (as expected). This should default correctly due to but its somehow getting through to lego causing this log
I think this line should probabably do a check for an empty key and probably panic with a message to the user that the Key Type is missing. I am not sure if it is safe to default to 4096.
As I workaround I manually set the key type to 4096 inside my acme.json.
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Bug
What did you do?
Upgraded to traefik 16.6.5 from 17.0.rc3
What did you expect to see?
ACME certificates renewing as expected.
What did you see instead?
Output of
traefik version
: (What version of Traefik are you using?)What is your environment & configuration (arguments, toml, provider, platform, ...)?
kubernetes helm chart with acme.json config. Single instance
ACME enabled, challenge type: http-01
The issue is related to #3319. In my acme.json my KeyType string was empty (as expected). This should default correctly due to but its somehow getting through to lego causing this log
I think this line should probabably do a check for an empty key and probably panic with a message to the user that the Key Type is missing. I am not sure if it is safe to default to 4096.
As I workaround I manually set the key type to 4096 inside my acme.json.
The text was updated successfully, but these errors were encountered: