Scott Galambos

Well-Known Member
Jul 13, 2016
125
8
68
Canada
cPanel Access Level
Root Administrator
I keep getting this. Its happened 4 days in a row now. Why? cPanel & WHM v102.0.11.

"The system failed to acquire a signed certificate from the cPanel Store because of the following error: (XID 8tgjpf) The cPanel Store returned an error (X::TemporarilyUnavailable) in response to the request “POST ssl/certificate/whm-license/90-day”: We were unable to process your request. Please try again later."
 

kodeslogic

Well-Known Member
PartnerNOC
Apr 26, 2020
542
253
138
IN
cPanel Access Level
Root Administrator
Try the following command with root user:

Code:
# /usr/local/cpanel/bin/checkallsslcerts
 

Scott Galambos

Well-Known Member
Jul 13, 2016
125
8
68
Canada
cPanel Access Level
Root Administrator
Same problem, it finds one domain to update SSL for so it tries:

Requesting certificate from cPStore …
The response to the HTTP (Hypertext Transfer Protocol) “POST” request from “https://store.cpanel.net/json-api/ssl/certificate/whm-license/90-day” indicated an error (500, Internal Server Error): <!DOCTYPE HTML PUBLIC "-//IETF/…
Undoing HTTP DCV setup (/var/www/html/.well-known/pki-validation/0690329D72EAA91D947CD3371ECDCF77.txt) …
… complete.
Enqueueing undo of DNS DCV setup (CNAME _0690329d72eaa91d947cd3371ecdcf77.core.extremehosting.ca) …
Undoing DNS DCV setup …
… done.
[WARN] The system failed to acquire a signed certificate from the cPanel Store because of the following error: (XID axn822) The response to the HTTP (Hypertext Transfer Protocol) “POST” request from “https://store.cpanel.net/json-api/ssl/certificate/whm-license/90-day” indicated an error (500, Internal Server Error): <!DOCTYPE HTML PUBLIC "-//IETF/…

Any idea?
 

Scott Galambos

Well-Known Member
Jul 13, 2016
125
8
68
Canada
cPanel Access Level
Root Administrator
Are you able to reach a test file you create in /var/www/html/.well-known/pki-validation/ when going to your-hostname.com/.well-known/pki-validation/testfile.txt?
No, I do not see /var/www/html/.well-known/pki-validation/0690329D72EAA91D947CD3371ECDCF77.txt.
server$ cd /var/www/html/.well-known/pki-validation
server$ ls -l -a
-rw-r--r-- 1 root root 77 May 31 2018 3703B1C51F95647074D734628D925EE1.txt

Must be an old one. But I can't reach that either no matter where it might be:
 

Scott Galambos

Well-Known Member
Jul 13, 2016
125
8
68
Canada
cPanel Access Level
Root Administrator
No, I do not see /var/www/html/.well-known/pki-validation/0690329D72EAA91D947CD3371ECDCF77.txt.
server$ cd /var/www/html/.well-known/pki-validation
server$ ls -l -a
-rw-r--r-- 1 root root 77 May 31 2018 3703B1C51F95647074D734628D925EE1.txt

Must be an old one. But I can't reach that either no matter where it might be:
Sorry, wrong path, this works:

So it cannot create the new file or something?
 
  • Like
Reactions: cPRex

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
13,450
2,114
363
cPanel Access Level
Root Administrator
Thanks for that. I just wanted to confirm a file placed there could be reached to rule out the 500 error being on the server's side.

I haven't had other reports of 500 errors from our provider today. If it's still not working when running the checkallsslcerts command manually, can you submit a ticket to our team so we can investigate?
 

Scott Galambos

Well-Known Member
Jul 13, 2016
125
8
68
Canada
cPanel Access Level
Root Administrator
Thanks for that. I just wanted to confirm a file placed there could be reached to rule out the 500 error being on the server's side.

I haven't had other reports of 500 errors from our provider today. If it's still not working when running the checkallsslcerts command manually, can you submit a ticket to our team so we can investigate?
ok, will do, thanks.
 
  • Like
Reactions: cPRex

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
13,450
2,114
363
cPanel Access Level
Root Administrator
Thanks for that. Our team determined this was caused by the larger recent issues with Sectigo having connection issues on their end. There wasn't anything wrong with your server's configuration, and just trying at a later date resolved the issue.