# Certbot doesn't create an IPv6 socket

**URL:** <https://community.letsencrypt.org/t/certbot-doesnt-create-an-ipv6-socket/74385>\
**Category:** Help\
**Created:** [October 9, 2018, 8:32pm UTC](https://community.letsencrypt.org/t/certbot-doesnt-create-an-ipv6-socket/74385 "2018-10-09T20:32:10Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [October 10, 2018, 5:36am UTC](https://community.letsencrypt.org/t/certbot-doesnt-create-an-ipv6-socket/74385/6 "2018-10-10T05:36:11Z")

</div>

Yeah, the standalone plugin has supported IPv6 since Certbot 0.15.0.

> [@Certbot 0.15.0 has been released](https://community.letsencrypt.org/t/certbot-0-15-0-has-been-released/35783):
>
> T…

> <https://github.com/certbot/certbot/issues/1466>
>
> As far as I can tell, the letsencrypt client does not bind to ipv6 in standalone… mode nor do the commands given in manual mode. While this may not seem too significant, but for people with ipv6 only machines (like me) this is quite a big problem. My suggestion would be to somehow bind to both ipv4 and ipv6 at the same time.
> 
> Either way, what you're doing is a great service to the global internet community, keep on rocking!

This is an awkward situation. 😬 Upgrading Certbot is the "right" thing to do, but using certbot-auto on an RPi is probably painful.

---

_[View the full topic](https://community.letsencrypt.org/t/certbot-doesnt-create-an-ipv6-socket/74385)._