ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Error generating Certificate with Lets Encrypt

    IT Discussion
    7
    22
    1.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dbeatoD
      dbeato @Dashrender
      last edited by

      @Dashrender said in Error generating Certificate with Lets Encrypt:

      @scottalanmiller said in Error generating Certificate with Lets Encrypt:

      @Dashrender said in Error generating Certificate with Lets Encrypt:

      @dbeato said in Error generating Certificate with Lets Encrypt:

      @harshmehta said in Error generating Certificate with Lets Encrypt:

      Hi All,

      When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

      Any help on this would be really great

      Please find below the error for same

      Waiting for verification...
      Cleaning up challenges
      Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

      IMPORTANT NOTES:

      • The following errors were reported by the server:

        Domain: gitlab.binex.cc
        Type: connection
        Detail: Fetching
        http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
        Timeout during connect (likely firewall problem)

        To fix these errors, please make sure that your domain name was
        entered correctly and the DNS A/AAAA record(s) for that domain
        contain(s) the right IP address. Additionally, please check that
        your computer has a publicly routable IP address and that no
        firewalls are preventing the server from communicating with the
        client. If you're using the webroot plugin, you should also verify
        that you are serving files from the webroot path you provided.
        root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

      Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

      This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

      You could open it.

      I do, manually then update then close it.
      I need to find out how to fix it right.

      Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @dbeato
        last edited by

        @dbeato said in Error generating Certificate with Lets Encrypt:

        @Dashrender said in Error generating Certificate with Lets Encrypt:

        @scottalanmiller said in Error generating Certificate with Lets Encrypt:

        @Dashrender said in Error generating Certificate with Lets Encrypt:

        @dbeato said in Error generating Certificate with Lets Encrypt:

        @harshmehta said in Error generating Certificate with Lets Encrypt:

        Hi All,

        When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

        Any help on this would be really great

        Please find below the error for same

        Waiting for verification...
        Cleaning up challenges
        Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

        IMPORTANT NOTES:

        • The following errors were reported by the server:

          Domain: gitlab.binex.cc
          Type: connection
          Detail: Fetching
          http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
          Timeout during connect (likely firewall problem)

          To fix these errors, please make sure that your domain name was
          entered correctly and the DNS A/AAAA record(s) for that domain
          contain(s) the right IP address. Additionally, please check that
          your computer has a publicly routable IP address and that no
          firewalls are preventing the server from communicating with the
          client. If you're using the webroot plugin, you should also verify
          that you are serving files from the webroot path you provided.
          root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

        Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

        This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

        You could open it.

        I do, manually then update then close it.
        I need to find out how to fix it right.

        Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

        It is not the PBX firewall. It is his router.

        dbeatoD DashrenderD 2 Replies Last reply Reply Quote 1
        • dbeatoD
          dbeato @JaredBusch
          last edited by

          @JaredBusch said in Error generating Certificate with Lets Encrypt:

          @dbeato said in Error generating Certificate with Lets Encrypt:

          @Dashrender said in Error generating Certificate with Lets Encrypt:

          @scottalanmiller said in Error generating Certificate with Lets Encrypt:

          @Dashrender said in Error generating Certificate with Lets Encrypt:

          @dbeato said in Error generating Certificate with Lets Encrypt:

          @harshmehta said in Error generating Certificate with Lets Encrypt:

          Hi All,

          When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

          Any help on this would be really great

          Please find below the error for same

          Waiting for verification...
          Cleaning up challenges
          Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

          IMPORTANT NOTES:

          • The following errors were reported by the server:

            Domain: gitlab.binex.cc
            Type: connection
            Detail: Fetching
            http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
            Timeout during connect (likely firewall problem)

            To fix these errors, please make sure that your domain name was
            entered correctly and the DNS A/AAAA record(s) for that domain
            contain(s) the right IP address. Additionally, please check that
            your computer has a publicly routable IP address and that no
            firewalls are preventing the server from communicating with the
            client. If you're using the webroot plugin, you should also verify
            that you are serving files from the webroot path you provided.
            root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

          Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

          This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

          You could open it.

          I do, manually then update then close it.
          I need to find out how to fix it right.

          Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

          It is not the PBX firewall. It is his router.

          Oh I see, makes sense now...

          1 Reply Last reply Reply Quote 0
          • wirestyle22W
            wirestyle22 @Dashrender
            last edited by

            @Dashrender said in Error generating Certificate with Lets Encrypt:

            @scottalanmiller said in Error generating Certificate with Lets Encrypt:

            @Dashrender said in Error generating Certificate with Lets Encrypt:

            @dbeato said in Error generating Certificate with Lets Encrypt:

            @harshmehta said in Error generating Certificate with Lets Encrypt:

            Hi All,

            When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

            Any help on this would be really great

            Please find below the error for same

            Waiting for verification...
            Cleaning up challenges
            Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

            IMPORTANT NOTES:

            • The following errors were reported by the server:

              Domain: gitlab.binex.cc
              Type: connection
              Detail: Fetching
              http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
              Timeout during connect (likely firewall problem)

              To fix these errors, please make sure that your domain name was
              entered correctly and the DNS A/AAAA record(s) for that domain
              contain(s) the right IP address. Additionally, please check that
              your computer has a publicly routable IP address and that no
              firewalls are preventing the server from communicating with the
              client. If you're using the webroot plugin, you should also verify
              that you are serving files from the webroot path you provided.
              root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

            Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

            This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

            You could open it.

            I do, manually then update then close it.
            I need to find out how to fix it right.

            I thought you were going to use dns to renew. Did that not work?

            JaredBuschJ 1 Reply Last reply Reply Quote 1
            • JaredBuschJ
              JaredBusch @wirestyle22
              last edited by

              @wirestyle22 said in Error generating Certificate with Lets Encrypt:

              @Dashrender said in Error generating Certificate with Lets Encrypt:

              @scottalanmiller said in Error generating Certificate with Lets Encrypt:

              @Dashrender said in Error generating Certificate with Lets Encrypt:

              @dbeato said in Error generating Certificate with Lets Encrypt:

              @harshmehta said in Error generating Certificate with Lets Encrypt:

              Hi All,

              When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

              Any help on this would be really great

              Please find below the error for same

              Waiting for verification...
              Cleaning up challenges
              Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

              IMPORTANT NOTES:

              • The following errors were reported by the server:

                Domain: gitlab.binex.cc
                Type: connection
                Detail: Fetching
                http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                Timeout during connect (likely firewall problem)

                To fix these errors, please make sure that your domain name was
                entered correctly and the DNS A/AAAA record(s) for that domain
                contain(s) the right IP address. Additionally, please check that
                your computer has a publicly routable IP address and that no
                firewalls are preventing the server from communicating with the
                client. If you're using the webroot plugin, you should also verify
                that you are serving files from the webroot path you provided.
                root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

              Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

              This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

              You could open it.

              I do, manually then update then close it.
              I need to find out how to fix it right.

              I thought you were going to use dns to renew. Did that not work?

              Not with FreePBX you are not.

              1 Reply Last reply Reply Quote 0
              • dbeatoD
                dbeato
                last edited by

                There is a feature request for FreePBX but not implemented yet
                https://issues.freepbx.org/browse/FREEPBX-17843

                1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender @JaredBusch
                  last edited by

                  @JaredBusch said in Error generating Certificate with Lets Encrypt:

                  @dbeato said in Error generating Certificate with Lets Encrypt:

                  @Dashrender said in Error generating Certificate with Lets Encrypt:

                  @scottalanmiller said in Error generating Certificate with Lets Encrypt:

                  @Dashrender said in Error generating Certificate with Lets Encrypt:

                  @dbeato said in Error generating Certificate with Lets Encrypt:

                  @harshmehta said in Error generating Certificate with Lets Encrypt:

                  Hi All,

                  When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

                  Any help on this would be really great

                  Please find below the error for same

                  Waiting for verification...
                  Cleaning up challenges
                  Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

                  IMPORTANT NOTES:

                  • The following errors were reported by the server:

                    Domain: gitlab.binex.cc
                    Type: connection
                    Detail: Fetching
                    http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                    Timeout during connect (likely firewall problem)

                    To fix these errors, please make sure that your domain name was
                    entered correctly and the DNS A/AAAA record(s) for that domain
                    contain(s) the right IP address. Additionally, please check that
                    your computer has a publicly routable IP address and that no
                    firewalls are preventing the server from communicating with the
                    client. If you're using the webroot plugin, you should also verify
                    that you are serving files from the webroot path you provided.
                    root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

                  Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

                  This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

                  You could open it.

                  I do, manually then update then close it.
                  I need to find out how to fix it right.

                  Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

                  It is not the PBX firewall. It is his router.

                  what? This is hosted by Vultr - I have no router in place.

                  JaredBuschJ 1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch @Dashrender
                    last edited by

                    @Dashrender said in Error generating Certificate with Lets Encrypt:

                    @JaredBusch said in Error generating Certificate with Lets Encrypt:

                    @dbeato said in Error generating Certificate with Lets Encrypt:

                    @Dashrender said in Error generating Certificate with Lets Encrypt:

                    @scottalanmiller said in Error generating Certificate with Lets Encrypt:

                    @Dashrender said in Error generating Certificate with Lets Encrypt:

                    @dbeato said in Error generating Certificate with Lets Encrypt:

                    @harshmehta said in Error generating Certificate with Lets Encrypt:

                    Hi All,

                    When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

                    Any help on this would be really great

                    Please find below the error for same

                    Waiting for verification...
                    Cleaning up challenges
                    Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

                    IMPORTANT NOTES:

                    • The following errors were reported by the server:

                      Domain: gitlab.binex.cc
                      Type: connection
                      Detail: Fetching
                      http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                      Timeout during connect (likely firewall problem)

                      To fix these errors, please make sure that your domain name was
                      entered correctly and the DNS A/AAAA record(s) for that domain
                      contain(s) the right IP address. Additionally, please check that
                      your computer has a publicly routable IP address and that no
                      firewalls are preventing the server from communicating with the
                      client. If you're using the webroot plugin, you should also verify
                      that you are serving files from the webroot path you provided.
                      root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

                    Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

                    This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

                    You could open it.

                    I do, manually then update then close it.
                    I need to find out how to fix it right.

                    Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

                    It is not the PBX firewall. It is his router.

                    what? This is hosted by Vultr - I have no router in place.

                    Ah was thinking of some one else

                    DashrenderD 1 Reply Last reply Reply Quote 0
                    • DashrenderD
                      Dashrender @JaredBusch
                      last edited by

                      @JaredBusch said in Error generating Certificate with Lets Encrypt:

                      @Dashrender said in Error generating Certificate with Lets Encrypt:

                      @JaredBusch said in Error generating Certificate with Lets Encrypt:

                      @dbeato said in Error generating Certificate with Lets Encrypt:

                      @Dashrender said in Error generating Certificate with Lets Encrypt:

                      @scottalanmiller said in Error generating Certificate with Lets Encrypt:

                      @Dashrender said in Error generating Certificate with Lets Encrypt:

                      @dbeato said in Error generating Certificate with Lets Encrypt:

                      @harshmehta said in Error generating Certificate with Lets Encrypt:

                      Hi All,

                      When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

                      Any help on this would be really great

                      Please find below the error for same

                      Waiting for verification...
                      Cleaning up challenges
                      Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

                      IMPORTANT NOTES:

                      • The following errors were reported by the server:

                        Domain: gitlab.binex.cc
                        Type: connection
                        Detail: Fetching
                        http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                        Timeout during connect (likely firewall problem)

                        To fix these errors, please make sure that your domain name was
                        entered correctly and the DNS A/AAAA record(s) for that domain
                        contain(s) the right IP address. Additionally, please check that
                        your computer has a publicly routable IP address and that no
                        firewalls are preventing the server from communicating with the
                        client. If you're using the webroot plugin, you should also verify
                        that you are serving files from the webroot path you provided.
                        root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

                      Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

                      This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

                      You could open it.

                      I do, manually then update then close it.
                      I need to find out how to fix it right.

                      Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

                      It is not the PBX firewall. It is his router.

                      what? This is hosted by Vultr - I have no router in place.

                      Ah was thinking of some one else

                      LOL - must have been - you were there when I build this one.

                      JaredBuschJ 1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch @Dashrender
                        last edited by

                        @Dashrender said in Error generating Certificate with Lets Encrypt:

                        @JaredBusch said in Error generating Certificate with Lets Encrypt:

                        @Dashrender said in Error generating Certificate with Lets Encrypt:

                        @JaredBusch said in Error generating Certificate with Lets Encrypt:

                        @dbeato said in Error generating Certificate with Lets Encrypt:

                        @Dashrender said in Error generating Certificate with Lets Encrypt:

                        @scottalanmiller said in Error generating Certificate with Lets Encrypt:

                        @Dashrender said in Error generating Certificate with Lets Encrypt:

                        @dbeato said in Error generating Certificate with Lets Encrypt:

                        @harshmehta said in Error generating Certificate with Lets Encrypt:

                        Hi All,

                        When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

                        Any help on this would be really great

                        Please find below the error for same

                        Waiting for verification...
                        Cleaning up challenges
                        Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

                        IMPORTANT NOTES:

                        • The following errors were reported by the server:

                          Domain: gitlab.binex.cc
                          Type: connection
                          Detail: Fetching
                          http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                          Timeout during connect (likely firewall problem)

                          To fix these errors, please make sure that your domain name was
                          entered correctly and the DNS A/AAAA record(s) for that domain
                          contain(s) the right IP address. Additionally, please check that
                          your computer has a publicly routable IP address and that no
                          firewalls are preventing the server from communicating with the
                          client. If you're using the webroot plugin, you should also verify
                          that you are serving files from the webroot path you provided.
                          root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

                        Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

                        This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

                        You could open it.

                        I do, manually then update then close it.
                        I need to find out how to fix it right.

                        Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

                        It is not the PBX firewall. It is his router.

                        what? This is hosted by Vultr - I have no router in place.

                        Ah was thinking of some one else

                        LOL - must have been - you were there when I build this one.

                        Is your system fully updated? Because I haven’t had any issues with cert renewals for a year now.

                        DashrenderD 1 Reply Last reply Reply Quote 1
                        • DashrenderD
                          Dashrender @JaredBusch
                          last edited by

                          @JaredBusch said in Error generating Certificate with Lets Encrypt:

                          @Dashrender said in Error generating Certificate with Lets Encrypt:

                          @JaredBusch said in Error generating Certificate with Lets Encrypt:

                          @Dashrender said in Error generating Certificate with Lets Encrypt:

                          @JaredBusch said in Error generating Certificate with Lets Encrypt:

                          @dbeato said in Error generating Certificate with Lets Encrypt:

                          @Dashrender said in Error generating Certificate with Lets Encrypt:

                          @scottalanmiller said in Error generating Certificate with Lets Encrypt:

                          @Dashrender said in Error generating Certificate with Lets Encrypt:

                          @dbeato said in Error generating Certificate with Lets Encrypt:

                          @harshmehta said in Error generating Certificate with Lets Encrypt:

                          Hi All,

                          When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

                          Any help on this would be really great

                          Please find below the error for same

                          Waiting for verification...
                          Cleaning up challenges
                          Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

                          IMPORTANT NOTES:

                          • The following errors were reported by the server:

                            Domain: gitlab.binex.cc
                            Type: connection
                            Detail: Fetching
                            http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                            Timeout during connect (likely firewall problem)

                            To fix these errors, please make sure that your domain name was
                            entered correctly and the DNS A/AAAA record(s) for that domain
                            contain(s) the right IP address. Additionally, please check that
                            your computer has a publicly routable IP address and that no
                            firewalls are preventing the server from communicating with the
                            client. If you're using the webroot plugin, you should also verify
                            that you are serving files from the webroot path you provided.
                            root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

                          Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

                          This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

                          You could open it.

                          I do, manually then update then close it.
                          I need to find out how to fix it right.

                          Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

                          It is not the PBX firewall. It is his router.

                          what? This is hosted by Vultr - I have no router in place.

                          Ah was thinking of some one else

                          LOL - must have been - you were there when I build this one.

                          Is your system fully updated? Because I haven’t had any issues with cert renewals for a year now.

                          I haven't done what I think are called firmware updates in over 6 months.

                          JaredBuschJ 1 Reply Last reply Reply Quote 0
                          • JaredBuschJ
                            JaredBusch @Dashrender
                            last edited by

                            @Dashrender said in Error generating Certificate with Lets Encrypt:

                            @JaredBusch said in Error generating Certificate with Lets Encrypt:

                            @Dashrender said in Error generating Certificate with Lets Encrypt:

                            @JaredBusch said in Error generating Certificate with Lets Encrypt:

                            @Dashrender said in Error generating Certificate with Lets Encrypt:

                            @JaredBusch said in Error generating Certificate with Lets Encrypt:

                            @dbeato said in Error generating Certificate with Lets Encrypt:

                            @Dashrender said in Error generating Certificate with Lets Encrypt:

                            @scottalanmiller said in Error generating Certificate with Lets Encrypt:

                            @Dashrender said in Error generating Certificate with Lets Encrypt:

                            @dbeato said in Error generating Certificate with Lets Encrypt:

                            @harshmehta said in Error generating Certificate with Lets Encrypt:

                            Hi All,

                            When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

                            Any help on this would be really great

                            Please find below the error for same

                            Waiting for verification...
                            Cleaning up challenges
                            Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

                            IMPORTANT NOTES:

                            • The following errors were reported by the server:

                              Domain: gitlab.binex.cc
                              Type: connection
                              Detail: Fetching
                              http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                              Timeout during connect (likely firewall problem)

                              To fix these errors, please make sure that your domain name was
                              entered correctly and the DNS A/AAAA record(s) for that domain
                              contain(s) the right IP address. Additionally, please check that
                              your computer has a publicly routable IP address and that no
                              firewalls are preventing the server from communicating with the
                              client. If you're using the webroot plugin, you should also verify
                              that you are serving files from the webroot path you provided.
                              root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

                            Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

                            This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

                            You could open it.

                            I do, manually then update then close it.
                            I need to find out how to fix it right.

                            Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

                            It is not the PBX firewall. It is his router.

                            what? This is hosted by Vultr - I have no router in place.

                            Ah was thinking of some one else

                            LOL - must have been - you were there when I build this one.

                            Is your system fully updated? Because I haven’t had any issues with cert renewals for a year now.

                            I haven't done what I think are called firmware updates in over 6 months.

                            Still on 13? Because FreePBX 14 no longer has them.

                            scottalanmillerS 1 Reply Last reply Reply Quote 1
                            • scottalanmillerS
                              scottalanmiller @JaredBusch
                              last edited by

                              @JaredBusch said in Error generating Certificate with Lets Encrypt:

                              @Dashrender said in Error generating Certificate with Lets Encrypt:

                              @JaredBusch said in Error generating Certificate with Lets Encrypt:

                              @Dashrender said in Error generating Certificate with Lets Encrypt:

                              @JaredBusch said in Error generating Certificate with Lets Encrypt:

                              @Dashrender said in Error generating Certificate with Lets Encrypt:

                              @JaredBusch said in Error generating Certificate with Lets Encrypt:

                              @dbeato said in Error generating Certificate with Lets Encrypt:

                              @Dashrender said in Error generating Certificate with Lets Encrypt:

                              @scottalanmiller said in Error generating Certificate with Lets Encrypt:

                              @Dashrender said in Error generating Certificate with Lets Encrypt:

                              @dbeato said in Error generating Certificate with Lets Encrypt:

                              @harshmehta said in Error generating Certificate with Lets Encrypt:

                              Hi All,

                              When I am trying to generate a certificate for my fqdn domain name I am unable to do so , looks like a bug to me but not really sure

                              Any help on this would be really great

                              Please find below the error for same

                              Waiting for verification...
                              Cleaning up challenges
                              Failed authorization procedure. gitlab.binex.cc (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ: Timeout during connect (likely firewall problem)

                              IMPORTANT NOTES:

                              • The following errors were reported by the server:

                                Domain: gitlab.binex.cc
                                Type: connection
                                Detail: Fetching
                                http://gitlab.binex.cc/.well-known/acme-challenge/xZk9yy56AiTn1bmyTC4GZZW0GAja5qiKwqem4ejVbjQ:
                                Timeout during connect (likely firewall problem)

                                To fix these errors, please make sure that your domain name was
                                entered correctly and the DNS A/AAAA record(s) for that domain
                                contain(s) the right IP address. Additionally, please check that
                                your computer has a publicly routable IP address and that no
                                firewalls are preventing the server from communicating with the
                                client. If you're using the webroot plugin, you should also verify
                                that you are serving files from the webroot path you provided.
                                root@gitlab:/var/opt/gitlab/nginx/www/.well-known/acme-challenge#

                              Basically your Gitlab Server doesn't have port 80 open so Let's Encrypt cannot validate it. What ports are you allowing through your firewall right now?

                              This is my problem with my FreePBX. port 80 isn't open to the world, so it won't auto-renew.

                              You could open it.

                              I do, manually then update then close it.
                              I need to find out how to fix it right.

                              Why not have the firewall in the server open port 80 before at the script start and closes it after the script ends?

                              It is not the PBX firewall. It is his router.

                              what? This is hosted by Vultr - I have no router in place.

                              Ah was thinking of some one else

                              LOL - must have been - you were there when I build this one.

                              Is your system fully updated? Because I haven’t had any issues with cert renewals for a year now.

                              I haven't done what I think are called firmware updates in over 6 months.

                              Still on 13? Because FreePBX 14 no longer has them.

                              Yeah, I've not done one in a long time.

                              1 Reply Last reply Reply Quote 0
                              • DashrenderD
                                Dashrender
                                last edited by

                                I'm on
                                FreePBX 14.0.5.2 (this is probably a bit behind)
                                Asterisk 13.19.1 (also behind)

                                JaredBuschJ 1 Reply Last reply Reply Quote 0
                                • JaredBuschJ
                                  JaredBusch @Dashrender
                                  last edited by

                                  @Dashrender said in Error generating Certificate with Lets Encrypt:

                                  I'm on
                                  FreePBX 14.0.5.2 (this is probably a bit behind)
                                  Asterisk 13.19.1 (also behind)

                                  Run your yum update and then fwconsole ma upgradeall and fwconsole reload

                                  1 Reply Last reply Reply Quote 2
                                  • 1
                                  • 2
                                  • 1 / 2
                                  • First post
                                    Last post