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.
My domain is:rpstpa.com
I ran this command: certbot certonly --standalone
It produced this output: cert.pem chain.pem fullchain.pem privkey.pem
My web server is (include version): IIS 10
The operating system my web server runs on is (include version): Server 2016
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know): Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
I can get as far as getting the pem files created but when I import the private key isn't attached.
I tried running:
openssl pkcs12 -export -out "certificate_combined.pfx" -inkey "privkey.pem" -in "cert.pem" -certfile bundle.pem
I tried this with and without an export password
This creates the combined file but when I try to import this into certificates it asks for the private key password. From what I understand this shouldn't have a password so I'm stuck.