Bug 1467100 - certbot --standalone doesn't bind to ipv6, but letsencrypt now prefers to verify over ipv6
Summary: certbot --standalone doesn't bind to ipv6, but letsencrypt now prefers to ver...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: certbot
Version: 26
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: James Hogarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-02 18:55 UTC by Randy Barlow
Modified: 2018-05-29 12:30 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:30:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Randy Barlow 2017-07-02 18:55:18 UTC
Description of problem:
Hello!

I had a hard time renewing my letsencrypt certs today. It turned out to be a combination of things. letsencrypt recently started verifying certificated over ipv6 (awesome). I have been using certbot with the --standalone flag, partly for simplicity (no messing with httpd configs) and partly because I have a few hosts that don't have port 80/443 (XMPP server, for example). I was banging my head for a while trying to figure out why it couldn't connect over v6 to this host because it seemed to work for me otherwise, and I finally thought to check that the client was binding to ipv6 and it wasn't!

Anyways, this was actually recently fixed upstream:

https://github.com/certbot/certbot/issues/1466
https://github.com/certbot/certbot/pull/4773

I'd like to request either a version bump to an upstream release that has that fix, or a backport of the patch if feasible. In the meantime, I will probably just switch to using httpd for verification.


Version-Release number of selected component (if applicable):
certbot-0.14.1-3.fc26.noarch


How reproducible:
Every time.


Steps to Reproduce:
1. Fire up watch on ss -lnp to see the ports that are being used on the host.
2. Use certbot with --standalone to get a cert. You can use the --dry-run flag if you please.


Actual results:
You'll see certbot bind to the ipv4 address, but not the ipv6 address.


Expected results:
It should bind to both v4 and v6.

Comment 1 Fedora End Of Life 2018-05-03 08:10:46 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2018-05-29 12:30:16 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.