sencrypt privacy error

[zustudios]

I installed a ssl on my site now it changed tp privacy error. The only ontion on sencrypt is revoke. Is there something I'm doing wrong?

[TGates]

I installed a ssl on my site now it changed tp privacy error. The only ontion on sencrypt is revoke. Is there something I'm doing wrong?

You should be able to delete them also.

What does the privacy notice say? There can be a few reasons why you get this notice.

[zustudios]

Certificate not valid. I'll delete it and see what happens.
Now I have: Oops! Something went wrong. Your Lets Encrypt certificate was not created. Check if your website is LIVE.
The website is live.

[TGates]

Certificate not valid. I'll delete it and see what happens.
Now I have: Oops! Something went wrong. Your Lets Encrypt certificate was not created. Check if your website is LIVE.
The website is live.

Is it just the one site or others also?

You may need to delete it, wait 5 minutes for the daemon to run so it removes the old configuration and then create a new one.

Are the files being created? (/var/sentora/hostdata/[username]/ssl/sencrypt/letsencrypt/)
Should be two folders, _account and domain.tld
_account should have a public.pem and private.pem
domain.tld should have 5 .pem files (and maybe one .csr file)

Also, in the site's root folder there should be a hidden folder: (/var/sentora/hostdata/[username]/public_html/domain_tld/.well-known/acme-challenge/)

What does the SenCrypt log show? (/etc/sentora/panel/modules/sencrypt/sencrypt.log)

[zustudios]

2023-09-07 17:58:07 - DOMAIN: hosting.dukecitysolutions.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-01-21 20:44:59 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-01-21 23:25:01 - DOMAIN: ghettohoods.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-01 00:17:05 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-01 00:18:27 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-01 00:18:37 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-01 00:19:04 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-01 12:46:20 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-01 22:53:42 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-05 00:00:41 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}
2024-05-07 13:09:24 - DOMAIN: bigfatmeat.com
400
{
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Unable to update challenge :: authorization must be pending",
"status": 400
}

[TGates]

2023-09-07 17:58:07 - DOMAIN: hosting.dukecitysolutions.com
400
{
  "type": "urn:ietf:params:acme:error:malformed",
  "detail": "Unable to update challenge :: authorization must be pending",
  "status": 400
}
[...SNIP...]
2024-05-07 13:09:24 - DOMAIN: bigfatmeat.com
400
{
  "type": "urn:ietf:params:acme:error:malformed",
  "detail": "Unable to update challenge :: authorization must be pending",
  "status": 400
}

After viewing the site myself directly and then the cert, the issue is that the cert is being made for:  ns3.bigfatmeat.com and not bigfatmeat.com

There is a problem with your DNS most likely at your domain registrar.