-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No certificates generated with acme.json from traefik v2.0 #46
Comments
edit: After reading some more it seems to be unrelated to this. Other similiar tools also have the same problem, there seems to be a new format inside the |
Confirming that no certificates are being extracted with an |
@ldez seems like it was this commit (traefik/traefik@c7d336f#diff-153848c6b668f0e912ccbef254a4e23c) that broke the dumper, which still uses Title-Cased keys :P |
This comment has been minimized.
This comment has been minimized.
@ldez Thank you. @timoschwarzer Is it working for you? For me using the newest version still doesn't resolve my issue. Only empty private folder :( |
I'm not really familiar with Go but I think the problem is that the v2 dumper doesn't take multiple certificate resolvers into account. My acme.json looks like this: {
"<certResolverName>": {
"Account": { ... },
"Certificates": [
{"domain": ..., "certificate": ..., "key": ..., "Store": ...},
...
]
}
} It looks like traefik-certs-dumper searches for the |
Fixed in v2.5.6. I will add some non regression tests. |
@ldez Unfortunately, |
There seems to be revision pinned that no longer exists ( |
I tested with real acme.json file without any issues. Could you give me more information? I recommend to use go1.13. |
I installed Go 1.13. I still cannot install all dependencies:
Of course: Traefik version
My acme.json (redacted){
"default": {
"Account": {
"Email": "me@email.com",
"Registration": {
"body": {
"status": "valid",
"contact": [
"mailto:me@email.com"
]
},
"uri": "https://acme-v02.api.letsencrypt.org/acme/acct/12345678"
},
"PrivateKey": "FOOOBAR",
"KeyType": "4096"
},
"Certificates": [
{
"domain": {
"main": "my.domain.com"
},
"certificate": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCkZPT09PT09PTwotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCgotLS0tLUJFR0lOIENFUlRJRklDQVRFLS0tLS0KRk9PT08KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=",
"key": "LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpCQUFBQUFBQVIKLS0tLS1FTkQgUlNBIFBSSVZBVEUgS0VZLS0tLS0K",
"Store": "default"
},
{
"domain": {
"main": "my.domain2.com"
},
"certificate": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCkZPT09PT09PTwotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCgotLS0tLUJFR0lOIENFUlRJRklDQVRFLS0tLS0KRk9PT08KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=",
"key": "LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpCQUFBQUFBQVIKLS0tLS1FTkQgUlNBIFBSSVZBVEUgS0VZLS0tLS0K",
"Store": "default"
}
]
}
} Traefik certificate resolver configcertificatesResolvers:
default:
acme:
email: me@redacted.com
storage: /acme.json
keyType: RSA4096
tlsChallenge: {} CommandI tried version 2.5.6 from both GitHub releases and the Docker image.
|
I found the issue. |
Sorry for the multiple releases, I'm on vacation so I did it a little fast. Fixed in v2.5.7. |
No need to apologize! It works like a charm now, thank you for your time! :) Have a nice vacation! |
It's working now. Thank you so much for fixing it. |
Hi,
first of all thanks for your work and that you are sharing it. I have tried it but I cannot get it to work on my server.
I'm using traefik v2.0 and the docker image ldez/traefik-certs-dumper:latest with the following command:
I'm getting the following log after the acme.json changed:
If I check the output folders they are empty. It would be kind if someone could give me a hint what I'm doing wrong.
Best regards
Originally posted by @rezor92 in #34 (comment)
The text was updated successfully, but these errors were encountered: