Project

General

Profile

Actions

Bug #8126

closed

ACME standalone HTTP not listening on IPv6

Added by Pim Pish about 7 years ago. Updated about 7 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
ACME
Target version:
-
Start date:
11/25/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.4.2
Affected Plus Version:
Affected Architecture:

Description

When I try to register a certificate via the ACME service I have a DNS name that only has an IPv6 record (AAAA). When I chose the "standalone HTTP server" method though mc is only listening on tcp4 instead of also tcp6.

I consider this to be a bug.
Link to my topic on the forum:
https://forum.pfsense.org/index.php?topic=140458.0

Script: /usr/local/pkg/acme/acme.sh

It might be a possibility to enter an IP address for the nc to listen on. Then it could decide by itself if it runs nc -4 or nc -6. Such a textfield should be optional though. IMO when nothing is given it should listen on any address for both IPv4 and IPv6.

Actions #1

Updated by Jim Pingle about 7 years ago

  • Project changed from pfSense to pfSense Packages
  • Category changed from Certificates to ACME
  • Status changed from New to Duplicate
  • Target version deleted (2.4.3)

Duplicate of #7519

Actions #2

Updated by David Summers about 7 years ago

I'm having the exact same problem.

I only have an IPv6 address for the DNS name of my pfsense router.

Once I hacked the script to add the --listen-ipv6 then it worked fine.

It needs to either listen on both IPv4 and IPv6 or at least add an option to listen on IPv6.

Other than this problem, everything worked great.

Actions

Also available in: Atom PDF