Unable to Create Wildcard Let's Encrypt using ACME DNS01 Challenge provider in Kubernetes

up vote
-1
down vote

favorite

I am trying to create wildcard let's encrypt SSL certificate in Kubernetes. I tried the the ACME-DNS DNS01 challenge and it not creating the SSL certificates.

Error preparing issuer for certificate default/wildcard-test-tk: ACME server does not allow selected challenge type or no provider is configured for domain "domtest.tk"

I have referred this link and used this acme-dns for creating credentials to verify the domain authority.

asked Nov 7 at 7:40

Basheer.O

16717

Can you share Kubernetes object configs for Certificate and ClusterIssuer?
– mk_sta
Nov 7 at 11:35

This is the Issuer condig apiVersion: certmanager.k8s.io/v1alpha1 kind: Issuer metadata: name: letsencrypt-testdom-prod namespace: default spec: acme: email: myemail@mydomain.com server: "https://acme-staging-v02.api.letsencrypt.org/directory" privateKeySecretRef: name: letsencrypt-test-prod dns01: providers: - name: dns-wildcard acmedns: host: https://auth.acme-dns.io accountSecretRef: name: acme-test-dns key: acmedns.json
– Basheer.O
Nov 7 at 12:07

And this is the Certificate config apiVersion: certmanager.k8s.io/v1alpha1 kind: Certificate metadata: name: wildcard-test-tk namespace: default spec: secretName: wildcard-test-tk-tls issuerRef: name: letsencrypt-testdom-prod kind: Issuer dnsNames: - '*.testdom.tk' acme: config: - dns01: provider: dns-wildcard domains: - '*.testdom.tk'
– Basheer.O
Nov 7 at 12:09

The issue corresponds to the different domain domtest.tk against testdom.tk that you've declared. Have you tried to add domtest.tk domain to your configuration?
– mk_sta
Nov 9 at 12:09

It is the typo when replacing the real domain.
– Basheer.O
Nov 9 at 13:07

add a comment |

up vote
-1
down vote

favorite

I am trying to create wildcard let's encrypt SSL certificate in Kubernetes. I tried the the ACME-DNS DNS01 challenge and it not creating the SSL certificates.

Error preparing issuer for certificate default/wildcard-test-tk: ACME server does not allow selected challenge type or no provider is configured for domain "domtest.tk"

I have referred this link and used this acme-dns for creating credentials to verify the domain authority.

asked Nov 7 at 7:40

Basheer.O

16717

Can you share Kubernetes object configs for Certificate and ClusterIssuer?
– mk_sta
Nov 7 at 11:35

This is the Issuer condig apiVersion: certmanager.k8s.io/v1alpha1 kind: Issuer metadata: name: letsencrypt-testdom-prod namespace: default spec: acme: email: myemail@mydomain.com server: "https://acme-staging-v02.api.letsencrypt.org/directory" privateKeySecretRef: name: letsencrypt-test-prod dns01: providers: - name: dns-wildcard acmedns: host: https://auth.acme-dns.io accountSecretRef: name: acme-test-dns key: acmedns.json
– Basheer.O
Nov 7 at 12:07

And this is the Certificate config apiVersion: certmanager.k8s.io/v1alpha1 kind: Certificate metadata: name: wildcard-test-tk namespace: default spec: secretName: wildcard-test-tk-tls issuerRef: name: letsencrypt-testdom-prod kind: Issuer dnsNames: - '*.testdom.tk' acme: config: - dns01: provider: dns-wildcard domains: - '*.testdom.tk'
– Basheer.O
Nov 7 at 12:09

The issue corresponds to the different domain domtest.tk against testdom.tk that you've declared. Have you tried to add domtest.tk domain to your configuration?
– mk_sta
Nov 9 at 12:09

It is the typo when replacing the real domain.
– Basheer.O
Nov 9 at 13:07

add a comment |

up vote
-1
down vote

favorite

I am trying to create wildcard let's encrypt SSL certificate in Kubernetes. I tried the the ACME-DNS DNS01 challenge and it not creating the SSL certificates.

Error preparing issuer for certificate default/wildcard-test-tk: ACME server does not allow selected challenge type or no provider is configured for domain "domtest.tk"

I have referred this link and used this acme-dns for creating credentials to verify the domain authority.

asked Nov 7 at 7:40

Basheer.O

16717

I am trying to create wildcard let's encrypt SSL certificate in Kubernetes. I tried the the ACME-DNS DNS01 challenge and it not creating the SSL certificates.

Error preparing issuer for certificate default/wildcard-test-tk: ACME server does not allow selected challenge type or no provider is configured for domain "domtest.tk"

I have referred this link and used this acme-dns for creating credentials to verify the domain authority.

dns kubernetes lets-encrypt certbot

asked Nov 7 at 7:40

Basheer.O

16717

asked Nov 7 at 7:40

Basheer.O

16717

asked Nov 7 at 7:40

Basheer.O

16717

asked Nov 7 at 7:40

Basheer.O

16717

asked Nov 7 at 7:40

Basheer.O

16717

Can you share Kubernetes object configs for Certificate and ClusterIssuer?
– mk_sta
Nov 7 at 11:35

This is the Issuer condig apiVersion: certmanager.k8s.io/v1alpha1 kind: Issuer metadata: name: letsencrypt-testdom-prod namespace: default spec: acme: email: myemail@mydomain.com server: "https://acme-staging-v02.api.letsencrypt.org/directory" privateKeySecretRef: name: letsencrypt-test-prod dns01: providers: - name: dns-wildcard acmedns: host: https://auth.acme-dns.io accountSecretRef: name: acme-test-dns key: acmedns.json
– Basheer.O
Nov 7 at 12:07

And this is the Certificate config apiVersion: certmanager.k8s.io/v1alpha1 kind: Certificate metadata: name: wildcard-test-tk namespace: default spec: secretName: wildcard-test-tk-tls issuerRef: name: letsencrypt-testdom-prod kind: Issuer dnsNames: - '*.testdom.tk' acme: config: - dns01: provider: dns-wildcard domains: - '*.testdom.tk'
– Basheer.O
Nov 7 at 12:09

The issue corresponds to the different domain domtest.tk against testdom.tk that you've declared. Have you tried to add domtest.tk domain to your configuration?
– mk_sta
Nov 9 at 12:09

It is the typo when replacing the real domain.
– Basheer.O
Nov 9 at 13:07

add a comment |

Can you share Kubernetes object configs for Certificate and ClusterIssuer?
– mk_sta
Nov 7 at 11:35

This is the Issuer condig apiVersion: certmanager.k8s.io/v1alpha1 kind: Issuer metadata: name: letsencrypt-testdom-prod namespace: default spec: acme: email: myemail@mydomain.com server: "https://acme-staging-v02.api.letsencrypt.org/directory" privateKeySecretRef: name: letsencrypt-test-prod dns01: providers: - name: dns-wildcard acmedns: host: https://auth.acme-dns.io accountSecretRef: name: acme-test-dns key: acmedns.json
– Basheer.O
Nov 7 at 12:07

And this is the Certificate config apiVersion: certmanager.k8s.io/v1alpha1 kind: Certificate metadata: name: wildcard-test-tk namespace: default spec: secretName: wildcard-test-tk-tls issuerRef: name: letsencrypt-testdom-prod kind: Issuer dnsNames: - '*.testdom.tk' acme: config: - dns01: provider: dns-wildcard domains: - '*.testdom.tk'
– Basheer.O
Nov 7 at 12:09

The issue corresponds to the different domain domtest.tk against testdom.tk that you've declared. Have you tried to add domtest.tk domain to your configuration?
– mk_sta
Nov 9 at 12:09

It is the typo when replacing the real domain.
– Basheer.O
Nov 9 at 13:07

Can you share Kubernetes object configs for Certificate and ClusterIssuer?
– mk_sta
Nov 7 at 11:35

This is the Issuer condig

apiVersion: certmanager.k8s.io/v1alpha1 kind: Issuer metadata:   name: letsencrypt-testdom-prod   namespace: default spec:   acme:     email: myemail@mydomain.com     server: "https://acme-staging-v02.api.letsencrypt.org/directory"     privateKeySecretRef:       name: letsencrypt-test-prod       dns01:         providers:         - name: dns-wildcard           acmedns:             host: https://auth.acme-dns.io             accountSecretRef:               name: acme-test-dns               key: acmedns.json

– Basheer.O
Nov 7 at 12:07

This is the Issuer condig

apiVersion: certmanager.k8s.io/v1alpha1 kind: Issuer metadata:   name: letsencrypt-testdom-prod   namespace: default spec:   acme:     email: myemail@mydomain.com     server: "https://acme-staging-v02.api.letsencrypt.org/directory"     privateKeySecretRef:       name: letsencrypt-test-prod       dns01:         providers:         - name: dns-wildcard           acmedns:             host: https://auth.acme-dns.io             accountSecretRef:               name: acme-test-dns               key: acmedns.json

– Basheer.O
Nov 7 at 12:07

And this is the Certificate config

apiVersion: certmanager.k8s.io/v1alpha1 kind: Certificate metadata:  name: wildcard-test-tk  namespace: default spec:  secretName: wildcard-test-tk-tls  issuerRef:    name: letsencrypt-testdom-prod    kind: Issuer  dnsNames:    - '*.testdom.tk'  acme:    config:      - dns01:          provider: dns-wildcard        domains:          - '*.testdom.tk'

– Basheer.O
Nov 7 at 12:09

And this is the Certificate config

apiVersion: certmanager.k8s.io/v1alpha1 kind: Certificate metadata:  name: wildcard-test-tk  namespace: default spec:  secretName: wildcard-test-tk-tls  issuerRef:    name: letsencrypt-testdom-prod    kind: Issuer  dnsNames:    - '*.testdom.tk'  acme:    config:      - dns01:          provider: dns-wildcard        domains:          - '*.testdom.tk'

– Basheer.O
Nov 7 at 12:09

The issue corresponds to the different domain domtest.tk against testdom.tk that you've declared. Have you tried to add domtest.tk domain to your configuration?
– mk_sta
Nov 9 at 12:09

It is the typo when replacing the real domain.
– Basheer.O
Nov 9 at 13:07

add a comment |

active

oldest

votes

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53185240%2funable-to-create-wildcard-lets-encrypt-using-acme-dns01-challenge-provider-in-k%23new-answer', 'question_page');
}
);

Post as a guest

Name

active

oldest

votes

draft saved

draft discarded

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Name

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Wsrtjtyk