Problem binding to port 80: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions

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:api.arcohes.com

I ran this command:certbot certonly (on windows server)

It produced this output:- Problem binding to port 80: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions

My web server is (include version): Windows server 2019 standard

The operating system my web server runs on is (include version): Windows 17763.2452

My hosting provider, if applicable, is:goDaddy
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):No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):1.32.0

Welcome to the community @geetas

I assume you tried to use the certbot --standalone method? It needs access to port 80 and that error is saying port 80 was already in use.

You could try a different certbot method, like --webroot, but, you might find an ACME client designed for Windows easier to use.

Certify The Web (CTW) is a gui which is very popular and easy to use. You can see its link in the Let's Encrypt list for Windows ACME clients (see here). Your server's http response headers say it is "Microsoft-HTTPAPI/2.0". If its cert requirements are similar to IIS a Windows specific client like CTW will be easier.

3 Likes