Maximum requests received for domain

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain

I ran this command:Synology renew request from control panel

It produced this output:maximal (sic) certificate requests reached for this domain

My web server is (include version):Synology NAS DSM 6.2.2-24922 Update 4

The operating system my web server runs on is (include version): DSM 6.2.2-24922 Update 4

My hosting provider, if applicable, is:N/A

I can login to a root shell on my machine (yes or no, or I don’t know):Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):N/A

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):Built into control panel for DSM

1 Like

Hi @v8gaz

there is a blog, not a DSM.

And there is only one - very old and expired - Letsencrypt certificate ( ):

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2018-06-04 2018-09-02
1 entries

There is a DSM -

Looks like you have hitted the failed validation limit.

The basics are ok, port 80 is open and answers with the expected result http status 404 - Not Found checking a file in /.well-known/acme-challenge.

So only option (DSM is a closed world): Check, if there is an update of your DSM.

1 Like

Blog is not hosted on the Synology, so you’re looking at the wrong thing.

Sorry, don’t know why I would have hot the failed validation limit, DSM is at the latest version. There is no LE cert installed right now, as it was expired and causing issues.

Any further ideas? And thanks for the quick response.

1 Like

The check shows a (good looking) TXT entry.

May be that DSM uses dns validation.

But it's really a problem: The DSM Letsencrypt client is unknown.

So if there isn't a "great error" (wrong dns, port 80 closed), normally the DSM client should work. Sometimes there are problems with older versions, but if the version is up to date ...?

Isn't there a better protocol you can share?

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.