惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
V
V2EX
Jina AI
Jina AI
爱范儿
爱范儿
M
MIT News - Artificial intelligence
量子位
L
LangChain Blog
Google DeepMind News
Google DeepMind News
酷 壳 – CoolShell
酷 壳 – CoolShell
罗磊的独立博客
腾讯CDC
MongoDB | Blog
MongoDB | Blog
P
Proofpoint News Feed
宝玉的分享
宝玉的分享
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Last Week in AI
Last Week in AI
H
Hackread – Cybersecurity News, Data Breaches, AI and More
F
Fortinet All Blogs
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
博客园 - 聂微东
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Vercel News
Vercel News
T
The Blog of Author Tim Ferriss

Let's Encrypt Community Support - Latest topics

New Certificate Fails with Unauthorized 403 Seeking Clarity and Consistency on Configuring HTTP-01 challenge for multiple domains Certifiate failing renewal Letsencrypt blocked in Iran Problem with http verification Cyber-attacks from the secondary verification source addresses Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems: How will clients handle X2 by X1 cross certificate revocation HTTPS Certificate Renewal and Mixed Content Issues Affecting My Real-Time Morse Code Website Using Let’s Encrypt .conf Files and Nginx along with Certbot Forbidden by policy error generating the let’s encrypt certificate SSL Certificate installed for 1 of 2 domains Certificate apparently not working Certbot 5.6.0 Release Would signing the key authorization with the ACME private key increase security? Lego 5.0.0 Release Certificate renewal incomplete: missing domains beeandlunetrading.com We can’t renew your Let’s Encrypt certificate automatically until the issue is resolved Is using preferred-chain "ISRG Root X2" still a good idea? Crypt::LE --delayed not being honored Expressway certificate renewal error even after upgrading to the latest version Yocto Bitbake install of Certbot luadns fails with 'NoneType' object is not callable Intended audience for "tlsserver" profile Trouble finding Charter Communications as Web Hoster 2026.05.08 Gen Y Cross-Certified Subordinate CAs missing serverAuth EKU Certbot deploy-hook Obtaining account ID from xmox.nl email server SSL Certificate Expired - pwgroup.plabcapy.com More cultural recognition of HTTPS adoption Certificado certbot Upcoming Let’s Encrypt Profile Changes On May 13
Posh-acme db_error submitting renewal
joe.roberts · 2026-04-16 · via Let's Encrypt Community Support - Latest topics

April 15, 2026, 10:45pm 1

We have run this command with PowerShell with the url matched to the server on several servers for the past 5+ years with no issues. Now it fails and am unable to determine the cause.

My domain is:
https://agdev05.esmsportal.com

I ran this command:
Submit-Renewal agdev05.esmsportal.com

It produced this output:

Submit-ChallengeValidation : {"error": "db_error"}
At C:\Program Files\WindowsPowerShell\Modules\Posh-ACME\4.31.0\Public\New-PACertificate.ps1:275 char:9

  •     Submit-ChallengeValidation
    
  •     ~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Submit-ChallengeValidation
      ], WebException
    • FullyQualifiedErrorId : WebCmdletWebResponseException,Submit-ChallengeValidation

Here is the result when executing Submit-ChallengeValidation -verbose

image

dextercd April 15, 2026, 11:17pm 3

The {"error": "db_error"} string in the error message there is probably coming from acme-dns.

When I try to invoke the /register endpoint I get the following error back from auth.acme-dns.io:

{"error": "database or disk is full"}

You could try opening an issue on their issue tracker, but note that they actually recommend hosting your own instance of acme-dns instead of relying on auth.acme-dns.io. Clarification on usage of https://auth.acme-dns.io · Issue #120 · acme-dns/acme-dns · GitHub

3 Likes

Do you have a link to information on hosting our own instance of acme-dns?

dextercd April 15, 2026, 11:42pm 5

There's the installation section in the README: GitHub - acme-dns/acme-dns: Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely. · GitHub

The Docker (compose) instructions seem pretty easy. You also have to setup the DNS as per the 'DNS Records' instructions.

I've never hosted this software myself so I can't help more with this.

I would recommend making sure you actually need acme-dns. If your DNS provider has an API then you might be able to use that. If you don't need wildcard certs then you can instead use the HTTP-01 challenge.

1 Like

MikeMcQ April 16, 2026, 1:36am 6

@joe.roberts Looks like you have GoDaddy as your DNS provider. Their API was restricted but recently opened up again. @rmbolger posted about this here: GoDaddy API access policy update As Dexter noted this may be a better option than acme-dns.

Looks like Ryan could update his docs here :slight_smile: GoDaddy - Posh-ACME

2 Likes

I appreciate the info! I am also looking for other CNAME redirect providers. I found Certify DNS as a possible option. As that post pointed out GoDaddy's pricing are rising while the service and support are dropping. We have several servers that prepaid for another year so we are working to move away from them. 10+ years ago, I thought they were going to be a great partner that offered many of the products that we needed, I was WRONG. I need to just find a alternative to "auth.acme-dns.io" for redirection since we have a lot of automation built around Posh-ACME. If you know of other options, I'd be grateful for any insights.

1 Like

MikeMcQ April 16, 2026, 3:15am 8

There is a new challenge type called dns-persist-01 in the works. It is currently in Let's Encrypt Staging system with plans for production this quarter.

I am very sure posh-acme will support that as soon as LE production is ready (as will Certify).

The idea is you create a TXT record once and that persists for as long you like to satisfy cert renewals. That avoids needing a DNS API, acme-dns, and similar.

See: DNS-PERSIST-01: A New Model for DNS-based Challenge Validation - Let's Encrypt

Perhaps the dreaded manual DNS Challenge to get a fresh cert now to carry you until LE has production dns-persist ready? I say dreaded b/c automation is far better but perhaps to avoid having to setup a very temporary new DNS infrastructure it is worth it?

1 Like

Yes, that would provide some better options. DNS management can be a challenge when the provider doesn't provide the necessary tools!

Thanks again for information

1 Like

Certify DNS (which I develop, and which can be cheaply licensed month-to-month via Azure marketplace) is an option but as @MikeMcQ mentioned the upcoming dns-persist-01 looks like it's going to be a simpler overall option for DNS based validation.

[Edit: I see we have support ticket from you, will investigate that myself]

You do also have the option of self-hosting acme-dns (many people do) but that's an administrative/maintenance/hosting overhead.

The GoDaddy API would be theoretically ideal but it's had a checkered history and it's confusing to know if you do or don't have access. Note that your domain registrar does not need to be your DNS host and there are many good large scale DNS hosts that are low cost or free (e.g. AWS Route 53, Cloudflare). Cloudflare in particular offers a lot of features in their free tier.

2 Likes

rmbolger April 16, 2026, 4:53am 11

Docs are updated in the dev branch already :wink: along with a GoDaddy plugin update to support corporate accounts. Just waiting for the next module release to push the doc updates live.

3 Likes

@rmbolger btw with Posh-ACME, if a user opts for a new acme-dns service and has previously completed an order using a different service I don't think it has a way to switch to the new acme-dns registration details (without passing them in manually). Perhaps it needs an option to clear existing reg for an order. Certify also has this issue,

2 Likes