PVE 5.2 Lets Encrypt: TASK ERROR: validating challenge failed

Discussion in 'Proxmox VE: Installation and configuration' started by Gunnar, Oct 11, 2018.

  1. Gunnar

    Gunnar New Member

    Joined:
    Oct 11, 2018
    Messages:
    1
    Likes Received:
    0
    I was trying to figure out the new letsencrypt integration, and couldn't get it to work...

    Then i noticed this:

    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    task\x20U 9499 root 3u IPv4 76078 0t0 TCP *:80 (LISTEN)
    task\x20U 9504 root 3u IPv4 76078 0t0 TCP *:80 (LISTEN)

    So that's not going to work for me, proxmox is on an IPv6 only network and that's not changing, so i need that task to listen on both...
     
  2. fabian

    fabian Proxmox Staff Member
    Staff Member

    Joined:
    Jan 7, 2016
    Messages:
    3,283
    Likes Received:
    506
    please file a bug on https://bugzilla.proxmox.com for libpve-common-perl. thank you!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. dotsam

    dotsam New Member

    Joined:
    Apr 15, 2019
    Messages:
    3
    Likes Received:
    1
    I see there's a bug open for this https://bugzilla.proxmox.com/show_bug.cgi?id=2061 and that there are even some recent commits that look to be getting this implemented, but I needed to get this working now, so as a workaround, I set up a quick socat listener to forward connections from IPv6 to IPv4

    Code:
    /usr/bin/socat TCP6-LISTEN:80,fork,ipv6only=1,reuseaddr TCP4:127.0.0.1:80
     
  4. fabian

    fabian Proxmox Staff Member
    Staff Member

    Joined:
    Jan 7, 2016
    Messages:
    3,283
    Likes Received:
    506
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. dotsam

    dotsam New Member

    Joined:
    Apr 15, 2019
    Messages:
    3
    Likes Received:
    1
    Strange, I have that version installed:
    Code:
    root@imbrem:~# apt-cache policy libhttp-daemon-perl
    libhttp-daemon-perl:
      Installed: 6.01-2
      Candidate: 6.01-2
      Version table:
     *** 6.01-2 500
            500 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 Packages
            100 /var/lib/dpkg/status
    
    Yet when I was attempting the certificate order yesterday, I only saw a listener opening on 0.0.0.0:80, not [::]:80, and the verification failed. Using the socat redirect worked right away though, so there were no other issues with the firewall or anything else.

    Does the HTTP server constructor in PVE/ACME/StandAlone.pm need to be changed to ensure it's listening on IPv6 as well perhaps?
     
    networ likes this.
  6. Ronny Aasen

    Ronny Aasen New Member

    Joined:
    Mar 15, 2018
    Messages:
    4
    Likes Received:
    0
    I see the same issue as dotsam.

    the socat trick works, but i assume it will fail on renewals ?
     
  7. dotsam

    dotsam New Member

    Joined:
    Apr 15, 2019
    Messages:
    3
    Likes Received:
    1
    I just made a simple systemd unit to keep socat running:
    Code:
    cat /etc/systemd/system/pve-ipv6-cert-proxy.service
    [Unit]
    Description=Forward IPv6 port 80 to proxomox acme validation server
    
    [Service]
    ExecStart=/usr/bin/socat TCP6-LISTEN:80,fork,ipv6only=1,reuseaddr TCP4:127.0.0.1:80
    
    [Install]
    WantedBy=multi-user.target
    
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice