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

FreePBX installs partially without error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: 14
    • Fix Version/s: None
    • Component/s: Installation
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      13
    • Distro Version:
      1707-1
    • Distro:
      FreePBX Distro

      Description

      I downloaded the latest ISO today: SNG7-FPBX-64bit-1707-1.iso, copied it to an 8GB USB key and booted it in UEFI mode.  

      During install I chose the VGA version with Asterisk 13.  Other than that all I did (or was asked for) was the root password, which I set.

      On first boot I get a login prompt, I login to determine the ip and it isn't displayed.  There was an error which reads "/usr/sbin/fwconsole file is not accessible".  I checked - it doesn't exist.

      The ethernet interface wasn't up.  The computer has 2 realtek gigabit ports. 

      I ran ifup eth1 and the port came up without issue.

      I then went to the IP in my browser on the same network and all I see is the Apache "Testing 123" page.

      I checked the Apache config and the freepbx config points to /var/www/html - the directory is empty.

      I also tried a yum update, which updated 26 packages.

      I'll probably try a previous version.. but very odd.  Any other suggestions?

      Other details: I'm only using 2.8 of 106GB on the drive.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                cpinfold cpinfold
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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