I noticed that you are using manual. Did you add the challenge file to your webroot/.well-known/acme-challenge/ with the right filename and contents? Usually you don't want to do this manually and instead specify your webroot to wacs.
I'm not seeing any redirects from http to https. Without those your site will be accessible insecurely.
I highly recommend that you follow the apache directions here:
I think [Manual] in WACS has a different meaning from --manual in Certbot, although I don't know exactly what it means. For example, I think it might just be referring to the fact that the renewal was requested on the command line. The FileSystem method sounds like it might be doing what Certbot's --webroot does.
I have checked for the pem files and i see foour of them in the apache\conf folder. I checked the https-ssl file and i see them being called for in that file.
The server was working fine with the cert unitl recently. I assume it is because it cannot renew the cert.
That is why i tried to run it manually in cmd window and noticed that it did not work. This is where i am stuck. Not sure what the original error means.
I ran your command and it looks like it worked, here is the results
A simple Windows ACMEv2 client (WACS)
Software version 2.1.12.943 (RELEASE, PLUGGABLE, 64-bit)
ACME server https://acme-v02.api.letsencrypt.org/
IIS not detected
Running with administrator credentials
Scheduled task looks healthy
Please report issues at https://github.com/win-acme/win-acme
Running in mode: Unattended
Target generated using plugin Manual: crm.nardellagroup.com
Overwriting previously created renewal
OK, i found the problem, there was a virtual host defined with 443 in httpd-ssl.conf, I changed the parameters in there, commented out the virtual host in httpd.con file, restarted appache and it is now working.
Thanks for all your help.
I guess the question do i leave the entries in httpd-ssl.conf or should i put them in httpd.conf. Or does it matter?
