Problem binding to port 80: Could not bind to IPv4 or IPv6

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. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
I ran this command:
certbot renew
It produced this output:

Processing C:\Certbot\renewal\

Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for
Cleaning up challenges
e[31mAttempting to renew cert ( from C:\Certbot\renewal\ produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.e[0m
e[31mAll renewal attempts failed. The following certs could not be renewed:e[0m
e[31m C:\Certbot\live\\fullchain.pem (failure)e[0m

All renewal attempts failed. The following certs could not be renewed:
C:\Certbot\live\\fullchain.pem (failure)

e[31m1 renew failure(s), 0 parse failure(s)e[0m
My web server is (include version):
Apache tomcat 8.5
The operating system my web server runs on is (include version):
Windows 2009 Server
My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or 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):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):


Hello all,
You see the information provided. The problem is, that no matter that the tomcat is stopped, still this issue appears, which should appear, when port 80 is running. I executed the following command:
netstat -aon | findstr 80 and i see, that the port 80 is still used:

:\Users\y509110>netstat -aon | findstr 80
TCP [::]:80 [::]:0 LISTENING 4
TCP [::]:49665 [::]:0 LISTENING 1280

and i was wondering whether another port could be specified to generate the certificates?
The authenticator is standalone.

Hi @Ivaylo.Iliev

there answers an IIS, not an Apache.

D:\temp>download -h
Error (1): Der Remoteserver hat einen Fehler zurückgegeben: (404) Nicht gefunden.
Content-Length: 0
Date: Thu, 15 Apr 2021 13:18:11 GMT
Server: Microsoft-IIS/10.0

Status: 404 NotFound

No, port 80 is required, may be with a redirect to domain name + port 443.

If you already have a web server running, you probably want to use a certbot plugin that integrates with it, rather than using the standalone plugin. The standalone plugin is designed for when there isn't a web server so it will start a mini-server up for you for answering the challenge, but as you see it can't run if there's already a web server running on the server.

Hi Jurgen,

Thank you for your response and your cooperation.
The site is available under:


That's unrelevant. Please read the basics:


Your port 80 is checked, nothing else.

If there runs something else, that will fail -> your configuration is wrong.

Hello Peter,

Thank you for your response and your cooperation.
Yes, you are absolutely correct, but i am not sure what i have to do in order to use the webserver and certbot simultaneously? I read about the different options - another option is "apache" as described here-
User Guide — Certbot 1.11.0.dev0 documentation (
should i use it?
These are the renewals params in the C:\Certbot\renewal\
account = <some_account_info_here>
authenticator = standalone
server =

Also my problem was, that no matter that i stopped the apache server, the certificates did not renew.

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