Can't renew LetsEncrypt Docker

    Hi,

    Not sure what happened with the new LE docker, but I no longer can renew due to the port 80 conflict.

    Both LE and Nextcloud are using Bridge mode.




    Code
    Attempting to renew cert (cloud.xxy.com) from /etc/letsencrypt/renewal/cloud.xxy.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
  /etc/letsencrypt/live/cloud.xxy.com/fullchain.pem (failure)



    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    Your LE container is mapping port 80:80. This is the source of the conflict. Is OMV running on port 80? If so change that.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Hi,


    Both OMV http and https ports are not using port 80.

    When I changed LE network to 'host', I got error:


    Code
    2020-03-16 22:43:18,787 fail2ban                [532]: ERROR   Failed during configuration: Have not found any log file for nextcloud jail,
2020-03-16 22:43:20,773 fail2ban                [544]: ERROR   Failed during configuration: Have not found any log file for nextcloud jail,
[16-Mar-2020 22:43:21] ERROR: unable to bind listening socket for address '127.0.0.1:9000': Address in use (98),
[16-Mar-2020 22:43:24] ERROR: unable to bind listening socket for address '127.0.0.1:9000': Address in use (98),
2020-03-16 22:43:24,777 fail2ban                [568]: ERROR   Failed during configuration: Have not found any log file for nextcloud jail,
2020-03-16 22:43:27,813 fail2ban                [586]: ERROR   Failed during configuration: Have not found any log file for nextcloud jail

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    What do you see when you go to your OMV IP address in a web browser?

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    If there is a port 80 conflict you need to connect to your OMV IP address in a web browser on port 80 and see if anything there responds.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Go back to your first post. Your letsencrypt container is set to map port 80 host to port 80 container. The error message "Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping" suggests that that port 80 may already be in use.


    What you need to do is determine whether or not port 80 is or is not in use at the time you are attempting to start the container. You can do that by visiting the IP address of the OMV machine in a web browser and see what if anything responds.


    Until you do this I have no other suggestions.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    This is the error I got when tried to access port 80, it automatically redirect to https.

    I also have Graphite docker port forwarding: 90>80, not sure if this cause conflict.




    Code
    tcp6       0      0 :::80                   :::*                    LISTEN      11624/docker-proxy

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    Einmal editiert, zuletzt von tinh_x7 ()

    Run this command in the shell and post the results.


    sudo lsof -i -P -n | grep *:80

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    I don't see anything running on IPV4 TCP Port 80. But something has to be listening on that port if you were redirected from it.


    I have no other ideas.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    I’m using reverse proxy.

    I don’t see any other sevice or app use port 80 or 443.

    Stopped Nginx service and tried the renewal, but error persist.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    Einmal editiert, zuletzt von tinh_x7 ()

    If there was nothing using port 80 then connecting to it with a web browser would give you a connection refused error. It would not redirect you elsewhere. Whatever is running on that port is doing that redirection.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    I ended up removed and re-installed the LE docker, and it worked.

    However, I keep getting this fail2ban error in the container:


    Code
    2020-03-18 22:27:05,681 fail2ban                [1066]: ERROR   Failed during configuration: Have not found any log file for nextcloud jail,
2020-03-18 22:25:56,601 fail2ban                [859]: ERROR   Failed during configuration: Have not found any log file for nextcloud jail

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden