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: Saving debug log to C:\Certbot\log\letsencrypt.log
Requesting a certificate for slicoinsurance.com
Problem binding to port 80: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access per
missions
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.lo
g or re-run Certbot with -v for more details.
My web server is (include version): windows server 2019
The operating system my web server runs on is (include version):
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 know port80 is in use. when i do stop or kill the PID using it and re-run the certbot i get
Saving debug log to C:\Certbot\log\letsencrypt.log
Requesting a certificate for slicoinsurance.com
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started b
y Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections fr
om the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.lo
g or re-run Certbot with -v for more details.
By Let's Encrypt policy, wildcard certificates are treated specially and can only be obtained using the DNS-01 method.
That method requires creating (new) DNS TXT records in your DNS zone as requested by the certificate authority, typically every time the wildcard certificate is going to be renewed.
I don't think your current DNS provider (wixdns) supports an API integration that could allow software like Certbot to do this automatically; however, I might be wrong, and other DNS providers do support this.
If you want to keep your DNS hosted at wixdns, I would suggest asking them about API support, or searching this forum to see if anyone else has made that work.
Wildcard will not work so am looking to generate a cert for each subdomain.
but am getting the same error.
certbot certonly --standalone -d portal.slicoinsurance.com --staple-ocsp -m info@slicoinsurance.com --agree-tos
Saving debug log to C:\Certbot\log\letsencrypt.log
Requesting a certificate for portal.slicoinsurance.com
Problem binding to port 80: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.
world wide services is currenting running on that port.
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.
You may want to consider an ACME client designed for Windows. Certify The Web is a popular one with a gui and is especially good with IIS server on Windows. It is on the recommended list by Let's Encrypt for Windows.
The author is a regular helper here and does very good with support at their own website too.
i have tried it with i get Certify The Web
Validation of the required challenges did not complete successfully. Domain validation failed: www.portal.slicoinsurance.com
DNS problem: NXDOMAIN looking up A for www.portal.slicoinsurance.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.portal.slicoinsurance.com - check that a DNS record exists for this domain BadRequest urn:ietf:params:acme:error:dns