Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output:
certbot certonly --webroot
My web server is (include version):
apache24
The operating system my web server runs on is (include version):
windows10
My hosting provider, if applicable, is:
AWS
I can login to a root shell on my machine (yes or no, or I don't know):
I don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot-auto
I think I found where it is failing in the logs. I am following the Apache/Windows instructions on from LetsEncrypt.
I can't say really...I'm a novice and was confused about that myself. I thought the SSL cert expiring made my server crash which is why I was seeing that. Are the 500 error and cert expiration two different problems?
I'd say yes.
The error 500 is happening over HTTP [without involving any certificate].
The "other" (third) problem you fail to recognize is that IIS is answering NOT nginxApache.
So, you might not even be on the right system/IP
OR
NAT is misconfigured
OR
something else can explain that difference.
That is saying port 80 is in use by something else. In your case it looks like IIS because that is what responds to HTTP requests right now.
Your first step is to have a site working with HTTP. Once you have that working you can try to get a cert.
If you decide to stay with IIS rather than Apache, I recommend using the acme client Certify The Web. It is one of the recommended clients for Windows. It is popular and an easy to use gui.
Thank you for the advice! My goal is use Apache. That is what the server was running with before it crashed. Do you know how/why IIS would've taken over?