[GH-ISSUE #1027] [Bug] failed to obtain certificate: provider 'hostingDE' not registered #704

Closed
opened 2026-03-03 01:05:21 +03:00 by kerem · 0 comments
Owner

Originally created by @DumpName on GitHub (Nov 4, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/1027

软件版本 / Release Version

v0.4.3

缺陷描述 / Description

When I try to get a certificate via the dns challenge with the dns provider "hosting.de" I get the error message: failed to obtain certificate: provider 'hostingDE' not registered

复现步骤 / Steps to reproduce

  1. Create a new standard workflow
  2. Set the application to use the DNS-01 challenge with the provider "hosting.de"
  3. Finish configuring the workflow
  4. Run the workflow

日志 / Logs

#Fk4z1GEZgLyMuK2U0D3zj Start
[2025-11-03T22:40:51.007+01:00] [0] the workflow is starting

#DPlABkhErKDsBs3ahKfYC Application
[2025-11-03T22:40:51.012+01:00] [0] ready to request certificate ... {"config":{"domains":["<SUBDOMAIN>.<DOMAIN>","<DOMAIN>"],"contactEmail":"<CONTACT-EMAIL>","challengeType":"dns-01","provider":"hostingDE","providerAccessId":"hn826q8fhi5d4la","caProvider":"letsencryptstaging","keySource":"auto","keyAlgorithm":"RSA2048","skipBeforeExpiryDays":30}}
[2025-11-03T22:40:51.013+01:00] [0] no found last issued certificate, begin to apply
[2025-11-03T22:40:51.017+01:00] [0] acme config initialized {"acmeDirUrl":"https://acme-staging-v02.api.letsencrypt.org/directory"}
[2025-11-03T22:40:51.856+01:00] [0] acme account initialized {"acmeAcctUrl":"https://acme-staging-v02.api.letsencrypt.org/acme/acct/<acctID>"}
[2025-11-03T22:40:52.353+01:00] [4] could not obtain certificate
[2025-11-03T22:40:52.354+01:00] [8] failed to obtain certificate: provider 'hostingDE' not registered

#KOidpmxasitriI1CNyk7Q Notification
[2025-11-03T22:40:52.355+01:00] [0] ready to send notification ... {"config":{"provider":"email","providerAccessId":"gbgfh9sy5gqhr2u","providerConfig":{"receiverAddress":"<CONTACT-EMAIL>"},"subject":"[Certimate] Workflow Failure Alert!","message":"Your workflow \"{{ $workflow.name }}\" run has failed. Please check the details.","skipOnAllPrevSkipped":false}}
[2025-11-03T22:40:54.413+01:00] [0] notification completed

其他 / Miscellaneous

I replaced domains & email information in the log above due to privacy reasons.

贡献 / Contribution

  • 我乐意为此贡献 PR! / I am interested in contributing a PR for this!
Originally created by @DumpName on GitHub (Nov 4, 2025). Original GitHub issue: https://github.com/certimate-go/certimate/issues/1027 ### 软件版本 / Release Version v0.4.3 ### 缺陷描述 / Description When I try to get a certificate via the dns challenge with the dns provider "hosting.de" I get the error message: `failed to obtain certificate: provider 'hostingDE' not registered` ### 复现步骤 / Steps to reproduce 1. Create a new standard workflow 2. Set the application to use the DNS-01 challenge with the provider "hosting.de" 3. Finish configuring the workflow 4. Run the workflow ### 日志 / Logs <details> ```console #Fk4z1GEZgLyMuK2U0D3zj Start [2025-11-03T22:40:51.007+01:00] [0] the workflow is starting #DPlABkhErKDsBs3ahKfYC Application [2025-11-03T22:40:51.012+01:00] [0] ready to request certificate ... {"config":{"domains":["<SUBDOMAIN>.<DOMAIN>","<DOMAIN>"],"contactEmail":"<CONTACT-EMAIL>","challengeType":"dns-01","provider":"hostingDE","providerAccessId":"hn826q8fhi5d4la","caProvider":"letsencryptstaging","keySource":"auto","keyAlgorithm":"RSA2048","skipBeforeExpiryDays":30}} [2025-11-03T22:40:51.013+01:00] [0] no found last issued certificate, begin to apply [2025-11-03T22:40:51.017+01:00] [0] acme config initialized {"acmeDirUrl":"https://acme-staging-v02.api.letsencrypt.org/directory"} [2025-11-03T22:40:51.856+01:00] [0] acme account initialized {"acmeAcctUrl":"https://acme-staging-v02.api.letsencrypt.org/acme/acct/<acctID>"} [2025-11-03T22:40:52.353+01:00] [4] could not obtain certificate [2025-11-03T22:40:52.354+01:00] [8] failed to obtain certificate: provider 'hostingDE' not registered #KOidpmxasitriI1CNyk7Q Notification [2025-11-03T22:40:52.355+01:00] [0] ready to send notification ... {"config":{"provider":"email","providerAccessId":"gbgfh9sy5gqhr2u","providerConfig":{"receiverAddress":"<CONTACT-EMAIL>"},"subject":"[Certimate] Workflow Failure Alert!","message":"Your workflow \"{{ $workflow.name }}\" run has failed. Please check the details.","skipOnAllPrevSkipped":false}} [2025-11-03T22:40:54.413+01:00] [0] notification completed ``` </details> ### 其他 / Miscellaneous I replaced domains & email information in the log above due to privacy reasons. ### 贡献 / Contribution - [ ] 我乐意为此贡献 PR! / I am interested in contributing a PR for this!
kerem 2026-03-03 01:05:21 +03:00
  • closed this issue
  • added the
    bug
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/certimate#704
No description provided.