Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-19646

Firewall Check Error in Certificate Manager

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 15
    • Fix Version/s: None
    • Component/s: Certificate Manager
    • Labels:
      None
    • Asterisk Version:
      16
    • Distro Version:
      15
    • Distro:
      FreePBX Distro

      Description

      Related somewhat to other issue reported (FREEPBX-19644) where fix firewall option on Let's Encrypt will replace rather than append to trusted networks.  This error manifests itself as:

      Unless outbound1.letsencrypt.org, outbound2.letsencrypt.org, mirror1.freepbx.org, and mirror2.freepbx.org are the FIRST entries in the trusted network list New Certificate will throw the warning.  However, as long as the servers are in the list, the certificate will go ahead and issue.  Routine needs to check the entire list, not just first entries.  Confirmed by comparing server where these were listed first (after restoring the almost 200 entries deleted reported in other error) vs three other servers where required servers were added with fwconsole firewall add trusted and they appear at the end of the list.  Tried fwconsole reload and restart on two servers and a hard reboot on another server.  Results the same on all.  Unless the entries are first, the warning is presented.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  chriskinsey Chris Kinsey
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:

                    NextupJiraPlusStatus

                    Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.