Certbot Windows Renewal error binding to port 80

Failed to renew certificate fxw.systems with error: Problem binding to port 80: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions

My domain is: fxw.systems

I ran this command: certbot -renew

It produced this output: Failed to renew certificate fxw.systems with error: 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): nginx

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

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

Certbot on Windows was never really a good idea, and is now deprecated--it's much better to use some Windows-native client for this purpose. But with that said, if certbot is trying to bind to port 80, that suggests it's being run in standalone mode, which doesn't seem appropriate if you're running a nginx web server.

7 Likes

He could try DNS authentication

2 Likes

If you're running ngnix that will hold onto port 80, if you're using certbot standalone you'd need to stop nginx and run certbot (as admin, with elevated privileges so you can use port 80).

As a possible alternative see Using with Apache, nginx or Other Web Servers | Certify The Web Docs

3 Likes

I was able to bind to port 80. Now getting this result:

2024-08-15 21:01:09,229:DEBUG:acme.client:Storing nonce: Xt09NNgJLpAtZ7usR0esTtqOoMN84kE1_X9iezjkus7F8gIp4q4
2024-08-15 21:01:09,230:INFO:certbot._internal.auth_handler:Challenge failed for domain fxw.systems
2024-08-15 21:01:09,230:INFO:certbot._internal.auth_handler:http-01 challenge for fxw.systems
2024-08-15 21:01:09,230:DEBUG:certbot._internal.display.obj:Notifying user:
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: fxw.systems
Type: connection
Detail: 20.241.88.218: Fetching http://fxw.systems/.well-known/acme-challenge/Fbd5x1DjfWAI9GMg8QAOJ5-bsQe4x0QmlTI39V5rqS4: Connection refused

So if you try that link yourself from a phone etc (external to your network) you should see that it fails to connect. Check that Windows firewall has TCP port 80 (http) open on the public network, if you are using a cloud VM host (e.g. Azure) also check the http (tcp port 80) is open in the network security settings in the cloud control panel for that VM.

5 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.