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

Activation does not work after update to FreePBX16 for non eth0 interface

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 16
    • Fix Version/s: 16.0.5.81
    • Component/s: None
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      Asterisk 16.20.0
    • Distro Version:
      FreePBX 16.0.10.34
    • Distro:
      FreePBX Distro
    • Module Fix Version:

      Description

      I just updated our freePBX-Server to FreePBX 16.0.10.34 using the integrated update tool. Everything worked well and the system is running fine. Just one problem…

      System Overview tells me that the server is not registered. So I head to Admin -> System Admin to activate it. When I click on “Activation” I am asked to activate this machine. When I do so, there are different results I get.

      The usual message I get is “Activation Error” Unable to display activation page. Error returned was: Operation timed out after 30000 milliseconds with 0 out of -1 bytes received.

      Sometimes, usually about every 5th time (approx.) something else happend. The system shows me popups about phones, etc. which I can skip with a button at the bottom. After about 2 to 5 of these popups I get either a window that asks me to enter my portal email-adress (most of the time) and after this, I get a window that tells me that a deployment id exists and asks me if I want to activate the system with this ID or I get the message regarding the deploymend id without the system asking for my portal adress. When I click on “activate” all that happens is, I get the message: “failed to restart apache”.

      I checked the web and someone mentioned that it could be a problem with the dns not correctly configured in resolv.conf. I checked the file and added 127.0.0.1 and 8.8.8.8 as nameserver in addition to the ones already there. Did not work…

      Someone else mentioned it could be a chown problem, so I ran “fwconsole chown”. Didn’t solve anything.
      When I try to restart the apache server manually by entering “/var/html/admin/modules/sysadmin/hooks/restart-apache” I get the following result:

      AH00558: httpd: Could not reliably determin the server’s fully qualified domain name, using freepbx.sangoma.local. Set the ‘ServerName’ directive globally to supress this message.

      I don’t get a permission denied, but I don’t get a correct “Stopping httpd / Starting httpd” either.

      When I activate the system via SSH by running fwconsole sysadmin activate XXXXXXXX I get this:

      Attempting to activate against deployment ‘XXXXXXXX’
      Running /var/www/html/admin/modules/sysadmin/bin/activate_existing XXXXXXXX
      Asking for deployment XXXXXXXX…Success!
      Array
      (
      [Hardware-Locked] => Yes
      [Produced-By] => Schmooze Communications
      [Product-Name] => PBXact
      [Registered-To] => XXXXXXXX
      [branding] => FreePBXDistro
      [deploy_type] => OSS
      [deployment_id] => XXXXXXXX
      [deploymentid] => XXXXXXXX
      [distributor] => No
      [global_lic_exp] => 2045-09-25
      [license_version] => 2
      [machineid] => 8ecX9c2X955X8a7Xba8X533Xfd3X431Xd5cXe24X6e5XfceXea0X1f9Xb0fXe4eX
      [Expires] => 28-Sep-2030
      [deployment_name] => XXXXXXXX
      )
      Setting permissions…
      Restarting httpd…
      Done

       

      but when I open the GUI in browser, I get a system not activated message in system overview.

       

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                kgupta Kapil Gupta
                Reporter:
                ChrisL ChrisL
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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