Pak Syafril, Setelah saya coba trial error ekspor certificate valid ke .pfx untuk backup dan kemudian delete dari list SSL lalu create ulang menggunakan let's encrypt ternyata berhasil.
berikut lognya: Starting Script run at 08/03/2022 09:33:10. Get the MDaemon paths. The MDaemon.ini Path is D:\MDaemon\APP\MDaemon.ini. The MDaemon APP Path is D:\MDaemon\APP\. The MDaemon Pem path is D:\MDaemon\PEM\. The MDaemon Log path is D:\MDaemon\Logs\. The MDaemon RAW path is D:\MDaemon\Queues\Raw\. The WorldClient Path is D:\MDaemon\WorldClient. The WorldClient HTML Path is D:\MDaemon\WorldClient\HTML. The well-known path is D:\MDaemon\WorldClient\HTML\.well-known. The Acme-Challenge path is D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge. The State Path is D:\MDaemon\PEM\_LEState. The FQDN is set to mail.richtex.co.id. The email address is set to [email protected]. Setting the system to use the LetsEncrypt Live Service. The certificate thumbrpint in the MDaemon.ini file is B5A5 E418 6DEC 35F9 B7CF B1F3 A4A7 EC95 0CE6 5945. Looking for the local certificate. The certificate is not from LetsEncrypt, requesting a new certificate. Importing the ACMESharp module. Getting an updated state. The account either doesn't exist or is not valid. It will be deleted and recreated. Creating a new AcmeState. Getting service directory. Getting a new Nonce Creating a new Account Key. Creating a new Account. Getting an updated state. Getting service directory. Getting a new Nonce Getting identifier for smtp.richtex.co.id. Getting identifier for smtp.richtex.co.id. Getting identifier for imap.richtex.co.id. Getting identifier for imap.richtex.co.id. Getting identifier for pop3.richtex.co.id. Getting identifier for pop3.richtex.co.id. Getting identifier for mail.richtex.co.id. Getting identifier for mail.richtex.co.id. Creating new certificate. Creating a new order for mail.richtex.co.id using dns:smtp.richtex.co.id dns:imap.richtex.co.id dns:pop3.richtex.co.id dns:mail.richtex.co.id Getting an updated state. Getting service directory. Getting an authorization for the dns:imap.richtex.co.id dns:mail.richtex.co.id dns:pop3.richtex.co.id dns:smtp.richtex.co.id. Getting service directory. Getting an updated state. The .well-known path for is D:\MDaemon\WorldClient\HTML\.well-known The Acme Challenge path for D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge The path D:\MDaemon\WorldClient\HTML\.well-known does not exist, it will be created. The path D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge does not exist, it will be created. Selecting the http-01 challenge and getting challenge data for dns:imap.richtex.co.id. The challenge status URL is https://acme-v02.api.letsencrypt.org/acme/chall-v3/137694941186/m9UFwQ. The challenge identifier is dns:imap.richtex.co.id. The URL to verify the challenge is imap.richtex.co.id/.well-known/acme-challenge/HR3pgYAf4zOLP3BwipgDIZHZfr8bfNnzBQVUT8vrwDs. The Challenge file name for dns:imap.richtex.co.id is HR3pgYAf4zOLP3BwipgDIZHZfr8bfNnzBQVUT8vrwDs The Challenge Content for dns:imap.richtex.co.id is HR3pgYAf4zOLP3BwipgDIZHZfr8bfNnzBQVUT8vrwDs.b-AUUxxpkBAcRRwo8Y162_CQkzgSKeDvTUb115zS9UQ Creating D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge\HR3pgYAf4zOLP3BwipgDIZHZfr8bfNnzBQVUT8vrwDs for dns:imap.richtex.co.id. Submitting the ACME challenge for dns:imap.richtex.co.id for verification. Selecting the http-01 challenge and getting challenge data for dns:mail.richtex.co.id. The challenge status URL is https://acme-v02.api.letsencrypt.org/acme/chall-v3/137694941196/WSX1hg. The challenge identifier is dns:mail.richtex.co.id. The URL to verify the challenge is mail.richtex.co.id/.well-known/acme-challenge/Ihbq9Qu8zsnImpZT44m07DwpxYJz0YBT17Ni9YR7n_g. The Challenge file name for dns:mail.richtex.co.id is Ihbq9Qu8zsnImpZT44m07DwpxYJz0YBT17Ni9YR7n_g The Challenge Content for dns:mail.richtex.co.id is Ihbq9Qu8zsnImpZT44m07DwpxYJz0YBT17Ni9YR7n_g.b-AUUxxpkBAcRRwo8Y162_CQkzgSKeDvTUb115zS9UQ Creating D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge\Ihbq9Qu8zsnImpZT44m07DwpxYJz0YBT17Ni9YR7n_g for dns:mail.richtex.co.id. Submitting the ACME challenge for dns:mail.richtex.co.id for verification. Selecting the http-01 challenge and getting challenge data for dns:pop3.richtex.co.id. The challenge status URL is https://acme-v02.api.letsencrypt.org/acme/chall-v3/137694941206/8iAZiA. The challenge identifier is dns:pop3.richtex.co.id. The URL to verify the challenge is pop3.richtex.co.id/.well-known/acme-challenge/GUrwdEEYmpQFjEh_jKWjcJzxUw9ZYFZkL7VAAyjB8rQ. The Challenge file name for dns:pop3.richtex.co.id is GUrwdEEYmpQFjEh_jKWjcJzxUw9ZYFZkL7VAAyjB8rQ The Challenge Content for dns:pop3.richtex.co.id is GUrwdEEYmpQFjEh_jKWjcJzxUw9ZYFZkL7VAAyjB8rQ.b-AUUxxpkBAcRRwo8Y162_CQkzgSKeDvTUb115zS9UQ Creating D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge\GUrwdEEYmpQFjEh_jKWjcJzxUw9ZYFZkL7VAAyjB8rQ for dns:pop3.richtex.co.id. Submitting the ACME challenge for dns:pop3.richtex.co.id for verification. Selecting the http-01 challenge and getting challenge data for dns:smtp.richtex.co.id. The challenge status URL is https://acme-v02.api.letsencrypt.org/acme/chall-v3/137694941216/Aji6Wg. The challenge identifier is dns:smtp.richtex.co.id. The URL to verify the challenge is smtp.richtex.co.id/.well-known/acme-challenge/83sC9NWzRAuxb3XMDCxgx5z_DhjpB0YwGRLWFZ7owSA. The Challenge file name for dns:smtp.richtex.co.id is 83sC9NWzRAuxb3XMDCxgx5z_DhjpB0YwGRLWFZ7owSA The Challenge Content for dns:smtp.richtex.co.id is 83sC9NWzRAuxb3XMDCxgx5z_DhjpB0YwGRLWFZ7owSA.b-AUUxxpkBAcRRwo8Y162_CQkzgSKeDvTUb115zS9UQ Creating D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge\83sC9NWzRAuxb3XMDCxgx5z_DhjpB0YwGRLWFZ7owSA for dns:smtp.richtex.co.id. Submitting the ACME challenge for dns:smtp.richtex.co.id for verification. Waiting for the order status to update... 0 Order is ready, getting the certificate key. Completing order for dns:imap.richtex.co.id dns:mail.richtex.co.id dns:pop3.richtex.co.id dns:smtp.richtex.co.id The Certificate URL is https://acme-v02.api.letsencrypt.org/acme/cert/04de2f0cd075148e04f2cce61ac16783b87c Exporting the certificate. All done, there's a pfx file at D:\MDaemon\PEM\mail.richtex.co.id_Cert_2022_08_637951159907384240.pfx. The thumbprint of the new certificate is: 78D1791A0B7CD9C3F797EF54CDAB9A9545D3988E Importing the certificate. Setting the certificate hash value in the MDaemon.ini file to 78D1 791A 0B7C D9C3 F797 EF54 CDAB 9A95 45D3 988E. Setting the certificate hash value in the D:\MDaemon\WorldClient\WorldClient.ini file to 78D1 791A 0B7C D9C3 F797 EF54 CDAB 9A95 45D3 988E. Setting the certificate hash value in the D:\MDaemon\WebAdmin\WebAdmin.ini file to 78D1 791A 0B7C D9C3 F797 EF54 CDAB 9A95 45D3 988E. Stopping MDaemon... The MDaemon service has stopped. The MDaemon Remote Administration service has stopped. Starting MDaemon... Starting MDaemon Remote Administration. Cleaning up old files. Checking for PFX files that begin with mail.richtex.co.id and are older than 180 days in the D:\MDaemon\PEM\ directory. Checking for files older than 180 days in the D:\MDaemon\WorldClient\HTML\.well-known\Acme-challenge directory. Checking for certificates that expired more than 30 days ago The script run is complete. Terima kasih pak. -- --[mdaemon-l]---------------------------------------------------------- Milis ini untuk Diskusi antar pengguna MDaemon Mail Server di Indonesia Netiket: https://wiki.openstack.org/wiki/MailingListEtiquette Arsip: http://mdaemon-l.dutaint.com Dokumentasi : http://mdaemon.dutaint.co.id Berlangganan: Kirim mail ke [email protected] Henti Langgan: Kirim mail ke [email protected] Versi terakhir: MDaemon 22.0.2, SecurityGateway 8.5.3
