# Problem binding to port 443: Could not bind to IPv4 or IPv6 (
**URL:** https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098
**Category:** Server
**Created:** [October 12, 2017, 2:17pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098 "2017-10-12T14:17:34Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@MuhammadFayaz](https://community.letsencrypt.org/u/MuhammadFayaz)
#### Post date: [October 12, 2017, 2:17pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/1 "2017-10-12T14:17:34Z")
/opt/eff.org/certbot/venv/lib/python2.6/site-packages/cryptography/ **init**.py:26: DeprecationWarning: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. A future version of cryptography will drop support for Python 2.6
DeprecationWarning
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
/opt/eff.org/certbot/venv/lib/python2.6/site-packages/acme/jose/jwa.py:110: DeprecationWarning: signer and verifier have been deprecated. Please use sign and verify instead.
signer = key.signer(self.padding, self.hash)
Performing the following challenges:
tls-sni-01 challenge for [ABC.com](http://ABC.com)
tls-sni-01 challenge for [www.ABC.com](http://www.ABC.com)
Cleaning up challenges
Problem binding to port 443: Could not bind to IPv4 or IPv6.
---
### Author:  [@MuhammadFayaz](https://community.letsencrypt.org/u/MuhammadFayaz)
#### Post date: [October 12, 2017, 2:18pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/2 "2017-10-12T14:18:19Z")
PLEASE HELP ON THIS MATTER I HAVE ROOT ACCESS OF MY MACHINE .lOOKING FORWARED GOOD RESPONSE. WEBSITE IS WORKING FROM cPANEL
---
### Author:  [@bytecamp](https://community.letsencrypt.org/u/bytecamp)
#### Post date: [October 12, 2017, 2:20pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/3 "2017-10-12T14:20:35Z")
> [@MuhammadFayaz](#):
>
> Problem binding to port 443
Do you have webserver software already running?
You can check that with:
> netstat -tln
---
### Author:  [@MuhammadFayaz](https://community.letsencrypt.org/u/MuhammadFayaz)
#### Post date: [October 12, 2017, 2:22pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/4 "2017-10-12T14:22:33Z")
tcp 0 0 0.0.0.0:443 0.0.0.0:\* LISTEN
---
### Author:  [@bytecamp](https://community.letsencrypt.org/u/bytecamp)
#### Post date: [October 12, 2017, 2:29pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/5 "2017-10-12T14:29:53Z")
Sorry, one parameter was missing:
> netstat -tpln
The argument -p shows the program name which is listening.
---
### Author:  [@MuhammadFayaz](https://community.letsencrypt.org/u/MuhammadFayaz)
#### Post date: [October 12, 2017, 2:30pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/6 "2017-10-12T14:30:40Z")
tcp 0 0 0.0.0.0:443 0.0.0.0:\* LISTEN 13807/httpd
---
### Author:  [@bytecamp](https://community.letsencrypt.org/u/bytecamp)
#### Post date: [October 12, 2017, 2:33pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/7 "2017-10-12T14:33:03Z")
There is already some software (Apache most likely) listening on port 443. You cannot use the standalone authentication then.
---
### Author:  [@MuhammadFayaz](https://community.letsencrypt.org/u/MuhammadFayaz)
#### Post date: [October 12, 2017, 2:33pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/8 "2017-10-12T14:33:48Z")
so now what do ?? in oder to get out from this and renew my ssl certifcate
---
### Author:  [@jsha](https://community.letsencrypt.org/u/jsha)
#### Post date: [October 12, 2017, 4:41pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/9 "2017-10-12T16:41:38Z")
A short term fix: You can briefly stop Apache and run Certbot again in standalone mode to renew your certificate.
A better, long term fix: Switch to using the webroot method in Certbot: [https://certbot.eff.org/docs/using.html#webroot](https://certbot.eff.org/docs/using.html#webroot). This will let Certbot renew your certificates without taking down Apache.
---
### Author:  [@system](https://community.letsencrypt.org/u/system)
#### Post date: [November 11, 2017, 4:41pm UTC](https://community.letsencrypt.org/t/problem-binding-to-port-443-could-not-bind-to-ipv4-or-ipv6/44098/10 "2017-11-11T16:41:41Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.