Suddenly the Let's Encrypt is not working

N

needforspeed

Verified User
Joined
Sep 17, 2021
Messages
11
When I Opened :


Suddenly the Certificate is no longer working...

I've tried to type :

/usr/local/directadmin/scripts/letsencrypt.sh request 'primary.nirwana.co'

and the result is :

/usr/local/directadmin/scripts/letsencrypt.sh request 'primary.nirwana.co'
Setting up certificate for a hostname: primary.nirwana.co
Requesting new certificate order...
Processing authorization for primary.nirwana.co...
Challenge is valid.
Generating 4096 bit RSA key for primary.nirwana.co...
openssl genrsa 4096 > "/usr/local/directadmin/conf/cakey.pem.new"
Generating RSA private key, 4096 bit long modulus
........++
.........................................++
e is 65537 (0x10001)
Checking Certificate Private key match... Match!
DirectAdmin certificate has been setup.
Setting up cert for Exim...
Setting up cert for WWW server...
Setting up cert for FTP server...
The services will be restarted in about 1 minute via the dataskq.
Certificate for primary.nirwana.co has been created successfully!

####

but still not working...
can you guys help me out ?
 
Seems you fixed it already? If I click on your link I get a nice https protected connection, so it looks working to me.
Tried with Chrome and Firefox.
 
yay I did it... it looked like just my cookies...

thanks

but how do you enable the auto renew when it expired ?
 
The auto renew is enabled automaticallyl. It only doesn't renew if something goes wrong for some reason. Could be several things, also an LE script which was present when you updated and the new LE script working, outage on the LE update server.... hard to say.

If all is well it will keep renewing now.
 
Hi...

after long time this problem suddenly happens again to me..

and when I tried to type :

/usr/local/directadmin/scripts/letsencrypt.sh request 'nirwana.co'

there is 1 subdomain is not detected and not given cerfiticate
also certificate no longer working

how to fix this ?
 
also when I opened my another domain :

This server could not prove that it is domain.com; its security certificate is from primary.nirwana.co. This may be caused by a misconfiguration or an attacker intercepting your connection.
 
Ah oke that's another domain then what you pointed to in the first post.
What happens when you request a wildcard ssl certificate, not via SSH but via the panel?
 
here is the output :

2021/12/25 08:22:55 [INFO] [mail.wallpapergordyn.com, pembukuan.wallpapergordyn.com, wallpapergordyn.com, www.pembukuan.wallpapergordyn.com, www.wallpapergordyn.com] acme: Validations succeeded; requesting certificates
2021/12/25 08:23:08 [INFO] [mail.wallpapergordyn.com] Server responded with a certificate for the preferred certificate chains "ISRG Root X1".
Certificate for mail.wallpapergordyn.com,wallpapergordyn.com,www.wallpapergordyn.com has been created successfully!


I think the problem is the certificate it used is 'ISRG Root X1' maybe that's why it's not working
it should be Let's Encrypt right ?

how to fix this ?
 
yes ive changed it but the another subdomain is not affected

v2.wallpapergordyn.com

Still not working how to fix it
 
No I don't use ZeroSSL. Seems that Zero SSL did not add the v2 to the SSL certificate.
Only www, mail and pempukan and the domain itself. Maybe you need to create a new wildcard certificate by ZeroSSL.
I don't know how to create a single one.
 
Richard G said:
No I don't use ZeroSSL. Seems that Zero SSL did not add the v2 to the SSL certificate.
Only www, mail and pempukan and the domain itself. Maybe you need to create a new wildcard certificate by ZeroSSL.
I don't know how to create a single one.
Click to expand...
how to create this ?
 
You must log in or register to reply here.
Back
Top