[GH-ISSUE #128] K8S: Create wildcard SSL using acmedns provider #49

New issue

Closed

opened 2026-03-13 15:33:03 +03:00 by kerem · 2 comments

kerem commented

2026-03-13 15:33:03 +03:00

Owner

Originally created by @basheer-urolime on GitHub (Nov 30, 2018).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/128

I have tried to create wildcard SSL certificate using k8s certmanager and issuer. I have created the credentials by POST requesting to /register URL and tested the acmedns successfully. However I am unable to create new wildcard SSL certificate using the k8s issuer. I am adding my issuer YAML file below

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

I have created the secret acme-dns using the json output got from the /register output.
Also, adding the k8s certificate YAML here

apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: wildcard-mydomain.com
  namespace: default
spec:
  acme:
    config:
    - dns01:
        provider: acmedns
      domains:
      - '*.mydomain.com'
  commonName: '*.mydomain.com'
  dnsNames:
  - '*.mydomain.com'
  issuerRef:
    kind: Issuer
    name: letsencrypt-wildcard-prod
  secretName: wildcard-mydomain.com-tls

I am getting the following error from the cert-manager:
###############################################################################
E1129 16:30:31.881025 1 reflector.go:205] github.com/jetstack/cert-manager/pkg/client/informers/externalversions/factory.go:71: Failed to list *v1alpha1.Issuer: v1alpha1.IssuerList: Items: []v1alpha1.Issuer: v1alpha1.Issuer: Spec: v1alpha1.IssuerSpec: IssuerConfig: ACME: v1alpha1.ACMEIssuer: DNS01: v1alpha1.ACMEIssuerDNS01Config: Providers: []v1alpha1.ACMEIssuerDNS01Provider: ReadArrayCB: expect [ or n, but found {, error found in #10 byte of ...|oviders":{"acmedns":|..., bigger context ...|81551da95"},"spec":{"acme":{"dns01":{"providers":{"acmedns":{"accountSecretRef":{"key":"acmedns.json|...
E1129 16:30:32.887374 1 reflector.go:205] github.com/jetstack/cert-manager/pkg/client/informers/externalversions/factory.go:71: Failed to list *v1alpha1.Issuer: v1alpha1.IssuerList: Items: []v1alpha1.Issuer: v1alpha1.Issuer: Spec: v1alpha1.IssuerSpec: IssuerConfig: ACME: v1alpha1.ACMEIssuer: DNS01: v1alpha1.ACMEIssuerDNS01Config: Providers: []v1alpha1.ACMEIssuerDNS01Provider: ReadArrayCB: expect [ or n, but found {, error found in #10 byte of ...|oviders":{"acmedns":|..., bigger context ...|81551da95"},"spec":{"acme":{"dns01":{"providers":{"acmedns":{"accountSecretRef":{"key":"acmedns.json|...
########################################################################

Originally created by @basheer-urolime on GitHub (Nov 30, 2018). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/128 I have tried to create wildcard SSL certificate using k8s certmanager and issuer. I have created the credentials by POST requesting to /register URL and tested the acmedns successfully. However I am unable to create new wildcard SSL certificate using the k8s issuer. I am adding my issuer YAML file below ``` apiVersion: certmanager.k8s.io/v1alpha1 kind: Issuer metadata: annotations: name: letsencrypt-wildcard-prod namespace: default spec: acme: dns01: providers: acmedns: accountSecretRef: key: acmedns.json name: acme-dns host: http://auth.mydomain.com email: info@mydomain.com privateKeySecretRef: name: letsencrypt-prod server: https://acme-v02.api.letsencrypt.org/directory ``` I have created the secret acme-dns using the json output got from the /register output. Also, adding the k8s certificate YAML here ``` apiVersion: certmanager.k8s.io/v1alpha1 kind: Certificate metadata: name: wildcard-mydomain.com namespace: default spec: acme: config: - dns01: provider: acmedns domains: - '*.mydomain.com' commonName: '*.mydomain.com' dnsNames: - '*.mydomain.com' issuerRef: kind: Issuer name: letsencrypt-wildcard-prod secretName: wildcard-mydomain.com-tls ``` I am getting the following error from the cert-manager: ############################################################################### E1129 16:30:31.881025 1 reflector.go:205] github.com/jetstack/cert-manager/pkg/client/informers/externalversions/factory.go:71: Failed to list *v1alpha1.Issuer: v1alpha1.IssuerList: Items: []v1alpha1.Issuer: v1alpha1.Issuer: Spec: v1alpha1.IssuerSpec: IssuerConfig: ACME: v1alpha1.ACMEIssuer: DNS01: v1alpha1.ACMEIssuerDNS01Config: Providers: []v1alpha1.ACMEIssuerDNS01Provider: ReadArrayCB: expect [ or n, but found {, error found in #10 byte of ...|oviders":{"acmedns":|..., bigger context ...|81551da95"},"spec":{"acme":{"dns01":{"providers":{"acmedns":{"accountSecretRef":{"key":"acmedns.json|... E1129 16:30:32.887374 1 reflector.go:205] github.com/jetstack/cert-manager/pkg/client/informers/externalversions/factory.go:71: Failed to list *v1alpha1.Issuer: v1alpha1.IssuerList: Items: []v1alpha1.Issuer: v1alpha1.Issuer: Spec: v1alpha1.IssuerSpec: IssuerConfig: ACME: v1alpha1.ACMEIssuer: DNS01: v1alpha1.ACMEIssuerDNS01Config: Providers: []v1alpha1.ACMEIssuerDNS01Provider: ReadArrayCB: expect [ or n, but found {, error found in #10 byte of ...|oviders":{"acmedns":|..., bigger context ...|81551da95"},"spec":{"acme":{"dns01":{"providers":{"acmedns":{"accountSecretRef":{"key":"acmedns.json|... ########################################################################

kerem closed this issue

2026-03-13 15:33:09 +03:00

kerem commented

2026-03-13 15:33:15 +03:00

Author

Owner

@Ajedi32 commented on GitHub (Nov 30, 2018):

This sounds like a problem with cert-manager, not with ACME-DNS. You're getting a stack trace from cert-manager, so it seems like that add-on is crashing.

@Ajedi32 commented on GitHub (Nov 30, 2018): This sounds like a problem with [cert-manager](https://github.com/jetstack/cert-manager), not with ACME-DNS. You're getting a stack trace from cert-manager, so it seems like that add-on is crashing.

kerem commented

2026-03-13 15:33:20 +03:00

Author

Owner

@joohoi commented on GitHub (Dec 5, 2018):

Yup, looks like cert-manager issue, closing accordingly. Feel free to comment if it's not the case and we'll reopen the issue.

@joohoi commented on GitHub (Dec 5, 2018): Yup, looks like cert-manager issue, closing accordingly. Feel free to comment if it's not the case and we'll reopen the issue.

kerem referenced this issue

2026-03-13 16:14:24 +03:00

[PR #49] [MERGED] return cname if requested RR was not found and cname exists (fixes #48) #263