It produced this output:
[INF] install socat succeed...
Please enter your domain name: drive3000.my.id
[DEG] Your domain is: drive3000.my.id, checking it...
[ERR] System already has certificates for this domain. Cannot issue again. Current certificate details:
[INF] Main_Domain KeyLength SAN_Domains CA Created Renew
185.82.200.145 "ec-256" no LetsEncrypt.org
drive3000.my.id "ec-256" no LetsEncrypt.org 2025-04-23T11:29:05Z 2025-06-21T11:29:05Z
No, nothing about the problem you've said is clear. We have no idea what program you're running that's providing the log output you're showing. We have no idea why it thinks "System already has certificates for this domain" implies "Cannot issue again" (though usually it is unhelpful to just issue again if one already has working certificates). We have no idea what "cert folder" you're looking at that you see is "empty". The more details you provide, the more likely someone here will be able to help you.
And whatever problem you're having, revoking certificates is highly unlikely to be helpful in resolving it. Revoking just adds information that a client can check to find out that a certificate shouldn't be trusted anymore; it doesn't make it any easier to issue another certificate, or make it any easier to find a certificate that you don't know where it is.