Certbot error: the identifiers are not all linked to the same preauthorized Subject organization name/address

Help
1

When I try to request a certificate from the Sectigo ACME service, I get the error below.
I have followed the necessary steps from their documentation in setting up an ACME account, including adding the domain. I also registered the account using certbot register and it shows up correctly using certbot show_account.

My domain is: irrelevant, the problem occurs with any domain name

I ran this command: sudo certbot certonly --webroot -w /home/bitnami/htdocs -d some.domain.eu

It produced this output:
An unexpected error occurred:
The identifiers are not all linked to the same preauthorized Subject organization name/address

My web server is (include version): apache 2.4.57

The operating system my web server runs on is (include version): Debian 11.10

My hosting provider, if applicable, is: MS Azure

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): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.11.0

2

Does this help?

Sectigo Hacker Guardian KnowledgeBase: Sectigo Certificate Manager (SCM) ACME error: "The client lacks sufficient authorization..." (Second Google hit when searching for the error message.)

2 Likes
3

Unfortunately not. I came across this post too, when I searched Google for the error.

The domain was in the list of allowed domains on the account (the Sectigo UI looks a little different nowadays) before I even ran the command.

4

Well, in any case, the error comes from the Sectigo ACME server, not from Certbot (it just passes it along). Thus, the problem and solution would also need to be searched at Sectigo.

If that guide doesn't help, perhaps you can ask Sectigos support how to fix it.

3 Likes
5

I'll be contacting them for help.
Thanks for your effort!

3 Likes
6

For anyone running into the same issue: I made a mistake when I added the domain to the ACME account in the Sectigo portal. I added *.domain.eu, but adding the wildcard domain does nothing. Adding the "regular" domain domain.eu solved the issue.
This is kind of confusing and particularly, it's not mentioned in the SCM admin guide.

7

From the link I posted earlier:

  • Please only assign non-wildcard domains
  • Adding * before the domain in ACME does not relate to Wild card domains
  • The domain domain.com will issue certificates for "Any FQDN (wildcard or non-wildcard) under that domain, plus that domain itself"
2 Likes
8

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