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:
adamos-price-calculator.softwareag.com
I ran this command:
certbot renew
It produced this output:
Processing C:\Certbot\renewal\adamos-price-calculator.softwareag.com.conf
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 adamos-price-calculator.softwareag.com
Cleaning up challenges
e[31mAttempting to renew cert (adamos-price-calculator.softwareag.com) from C:\Certbot\renewal\adamos-price-calculator.softwareag.com.conf 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\adamos-price-calculator.softwareag.com\fullchain.pem (failure)e[0m
All renewal attempts failed. The following certs could not be renewed:
C:\Certbot\live\adamos-price-calculator.softwareag.com\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):
no
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot):
1.8.0
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 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING 1280
TCP 193.26.198.18:51907 2.16.186.11:80 TIME_WAIT 0
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.