I have remove my certbot ssl using this command certbot delete --cert-name (because i must change the ssl with new wildcard) but i have ran the command, my site is still running using ssl from letsencrypt. How i can fully removed and start using new SSL ?
To fully remove certbot you uninstall the app and delete the schedule task but this will not affect your actual Apache web server config.
To remove the certificate from Apache, edit the SSL config in your apache config file for this site. It will have a line mentioning SSLCertificateFile, you need to repoint the SSL related config to your new certificate as provided by the alternative app you have chosen. [Then restart apache]
I have to try what are you tell it, but like not working. I have configure the new SSL from httpd-ssl.conf from the path SSLCertificateFile and restart the apache , but still the SSL status is using Letsencrypt not the new one. Any solution sir?
Search your C: drive for all files containing SSLCertificateFile, either one of them is pointing to the wrong place, your certificate files are the wrong files, or your Apache has not properly restarted. There's no magic involved, just configuration
I have check all of files containing SSLCertificateFile but still no luck. I have tried on 2nd server (I haven't installed letsencrypt or other SSL before) i just configure what inside httpd-ssl.conf same like in 1st server, i restart the apache, and it's working normally started with new SSL . But in the 1st server still no luck, always pointing to Letsencrypt SSL . @webprofusion
I have try rebooting the machine, and check the certificate is valid & same like my domain. But still nothing happend, still pointing to Letsencrypt SSL
My 1st server belongs to xxxx.domain.com , my 2nd server is belong to another domain.
For the 2nd server is normally setup with my new SSL , but my 1st server is still stuck pointing to Letsencrypt SSL.
And you're absolutely sure the server you are changing is the 103.40.55.191 one that serves this site? It's fairly common to find you are making changes on your development server instead of your production server. A good test is to temporarily stop Apache, then try accessing your website again and if it still works then you're definitely working on the wrong server.
Apache just picks up the cert file that the config points to, so if it's still serving the wrong thing (and you have restarted) then the config simply points to the wrong file. You may be editing a different config file to the one that actually applies.