Attempting to renew cert from /etc/letsencrypt/renewal/somedomain.com.conf produced an unexpected error: Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.This is running on an AWS ubuntu 14.04 instance. All ports are open outgoing and 443 is open incoming.

You are watching: Problem binding to port 80: could not bind to ipv4 or ipv6.


*

*

you probably run the script with (preconfigurated) --standalone when your server is already running at port 443.

You can stop server before renew and start them after.

man says:

--apache Use the Apache plugin for authentication & installation--standalone Run a standalone webserver for authentication--nginx Use the Nginx plugin for authentication & installation--webroot Place files in a server"s webroot folder for authentication--manual Obtain certificates interactively, or using shell script hooksIf I run renew with --apache I can"t get any error.


Share
Follow
answered Sep 17 "17 at 17:48
*

JKLIRJKLIR
89888 silver badges1111 bronze badges
4
Add a comment |
66
You just need to stop all running servers like Apache, nginx or OpenShift before doing this.

See more: Watch Rick And Morty Season 3 Episode 5 Streaming Online, Watch Rick And Morty On Adult Swim

Stop Nginx

sudo systemctl stop nginxStop Apache2

sudo systemctl stop apache2
Share
Follow
edited Nov 7 "20 at 0:33

*

Promise Preston
12.5k88 gold badges6868 silver badges9191 bronze badges
answered Dec 3 "17 at 9:32
*

shadaï ALIshadaï ALI
1,09788 silver badges1111 bronze badges
6
| Show 1 more comment
11
As hinted in the other answers, you need to pass the option for your running webserver, for example:

Without webserver param:

sudo certbot renew Cert is due for renewal, auto-renewing... Renewing an existing certificate Performing the following challenges:tls-sni-01 challenge for example.com Cleaning up challenges Attempting to renew cert (example.com) from /etc/letsencrypt/renewal/example.com.conf produced an unexpected error: Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.

Then, again with the webserver param (success):

sudo certbot renew --nginx Cert is due for renewal, auto-renewing... Renewing an existing certificate Performing the following challenges: tls-sni-01 challenge for example.com Waiting for verification... Cleaning up challenges

new certificate deployed with reload of nginx server; fullchain is /etc/letsencrypt/live/example.com/fullchain.pem

Congratulations, all renewals succeeded. The following certs have been renewed: /etc/letsencrypt/live/example.com/fullchain.pem (success)