Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Edd Noman

Pages: [1] 2
1
Hardware / HP Enterprise - HP ProLiant Smart Array Configuration Utility
« on: July 20, 2018, 09:09:37 AM »
The HP Array Configuration Utility is a web-based application that helps you configure HP ProLiant SMART-2 Array Controllers, HP ProLiant Smart Array Controllers, HP ProLiant Integrated Smart Array Controllers, and HP ProLiant StorageWorks RAID Array Controllers. You can use the Array Configuration Utility for several tasks such as configuring the array controller initially, adding disk drives to an existing configuration, or to reconfigure your array controller.

https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_4effd70562304a50b3be5c4b96#tab3

Type:    Software - System Management
Version:    9.40.12.0(19 Feb 2013)

Operating System(s):
Microsoft Windows 7 (64-bit)
Microsoft Windows Server 2003 for 64-bit Extended Systems
Microsoft Windows Server 2008 x64
Microsoft Windows Server 2012
Microsoft Windows Storage Server 2003 x64 Editions
Microsoft Windows Unified Data Storage Server 2003 x64 Edition
Microsoft Windows Vista (64-bit)
Microsoft Windows XP Professional x64 Edition

File name: cp018121.exe (6.0 MB)

Installation:
Download the Smart Component to a directory on your hard drive and change to that directory. The downloaded file is a self-extracting executable with a filename based on the Smart Component Number. From that drive and directory, execute the downloaded file. Click the "Install" button to proceed with the installation. The utility will automatically be installed.
Reboot is not required after installation for updates to take effect and hardware stability to be maintained.

2
Hardware / HP Enterprise - Smart Array, Logical Volume Config Example
« on: July 20, 2018, 09:03:39 AM »

I want to install a SA6402 Smrt Array card and disk drives. But I do not
know how to configure the drives. Is there any document that describes the
installation?

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c00992067

You can use ORCA (Option ROM Configuration for Arrays) for the logical volume
configuration. Below is an operation example of ORCA.

    POST boot message for ORCA. Ignore the message or press F1
    key.

    Note:
    If you access the system console with the Reflection terminal emulator, any
    function keys do not work. In this case use ESC key and numeric key. For
    instance, ESC + 1 works as F1.

    EFI version 1.10 [14.62]
    EFI64 Running on Intel(R) Itanium Processor Family
    EFI 1.10 IPF server rx4640  3.10 [Tue Sep 30 14:14:27 2003] - HP
    0 0 0x0002B9 0x0000000000000013 EFI POST code
    Loading 'SysROM:Floating-Point Software Assistance Handler'...
    -- 'SysROM:Floating-Point Software Assistance Handler' returned Success
    Loading 'SysROM:Broadcom Gigabit Ethernet Driver'...

    Copyright (c) 2000-2004 Broadcom Corporation
    Broadcom NetXtreme Gigabit Ethernet EFI driver v7.0.3

    -- 'SysROM:Broadcom Gigabit Ethernet Driver' returned Success
    0 0 0x0002B9 0x0000000000000014 EFI POST code
    1 0 0x00020B 0x0000000000000006 EFI Launching Boot Manager
    0 0 0x000318 0x0000000000000030 EFI security system initialized
    0 0 0x0002B9 0x0000000000000015 EFI POST code
    0 0 0x0015B2 0x0000000066427668 boot time event
    Scsi(Pun1,Lun0) HP 73.4GST373453LC      HPC3 (160 MBytes/sec)
    Scsi(Pun4,Lun0) HP      SAF-TE          1
    Scsi(Pun0,Lun0) HP 73.4GST373453LC      HPC5 (160 MBytes/sec)
    Scsi(Pun4,Lun0) HP      SAF-TE          1
    Broadcom NetXtreme Gigabit Ethernet (BCM5701) is detected (PCI)

    HP Smart Array 6400-128 Controller       (version 2.34)  0 Logical Drives
    1785-Drive Array Not Configured
         Run Smart Array Configuration Utility


    Press "F1" to continue...

    After
    pressing F1 key, system requests pressing F8 key (or Esc+8) to
       run ORCA.

    Loading 'SysROM:Broadcom Gigabit Ethernet Driver'...

    Copyright (c) 2000-2004 Broadcom Corporation
    Broadcom NetXtreme Gigabit Ethernet EFI driver v7.0.3

    -- 'SysROM:Broadcom Gigabit Ethernet Driver' returned Success
    0 0 0x0002B9 0x0000000000000014 EFI POST code
    1 0 0x00020B 0x0000000000000006 EFI Launching Boot Manager
    0 0 0x000318 0x0000000000000030 EFI security system initialized
    0 0 0x0002B9 0x0000000000000015 EFI POST code
    0 0 0x0015B2 0x0000000065681013 boot time event
    Scsi(Pun1,Lun0) HP 73.4GST373453LC      HPC3 (160 MBytes/sec)
    Scsi(Pun4,Lun0) HP      SAF-TE          1
    Scsi(Pun0,Lun0) HP 73.4GST373453LC      HPC5 (160 MBytes/sec)
    Scsi(Pun4,Lun0) HP      SAF-TE          1
    Broadcom NetXtreme Gigabit Ethernet (BCM5701) is detected (PCI)
    HP Smart Array 6400-128 Controller       (version 2.34)  0 Logical Drives
    1785-Drive Array Not Configured



     Press [F8] to run the Option ROM Configuration for Arrays Utility
     Press [ESC] to skip configuration and continue

    Once ORCA runs, the main menu
    displays as follows.

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage



                        +------------Main Menu---------------+
                        | Create Logical Drive               |
                        | View Logical Drive                 |
                        | Delete Logical Drive               |
                        +------------------------------------+



     [Enter] to create a new logical drive

     [UP/DOWN ARROW] to select main menu option; [ESC] to exit

    View Logical Drive screen output

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage



                      +------------------------------------------+
                      |          There are no available          |
                      |             logical drives.              |
                      |                                          |
                      |  Press [ESC] to return to the main menu. |
                      +------------------------------------------+



     [ESC] to return

    Create Logical Drive screen
       In this case, I selected the only one drive for RAID 0 configuration.
       You can move the cursor with the Up/Down arrow keys and select the
       de-selecting the drives with the space key.

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage
    +----------Available Physical Drives------------+ +---Raid Configurations------+
    | [ ] SCSI Port  2, ID  0, COMPAQ    36.4 GB    | | [ ] RAID ADG               |
    | [ ] SCSI Port  2, ID  1, COMPAQ    36.4 GB    | | [ ] RAID 5                 |
    | [ ] SCSI Port  2, ID  2, COMPAQ    72.8 GB    | | [ ] RAID 1+0               |
    | [X] SCSI Port  2, ID  3, COMPAQ    72.8 GB    | | [X] RAID 0                 |
    +-----------------------------------------------+ +----------------------------+

                                                      +----------Spare-------------+
                                                      | [ ] Use one drive as spare |
                                                      +----------------------------+




     [Enter] to create a logical drive; [Tab] to navigate

     [UP/DOWN ARROW] to scroll; [ESC] to return; [Space Bar] to select

    Once you press [Enter] key, you can save the new configuration.

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage


             +------------------------------------------------------------+
             | You have selected a logical drive with a total             |
             | data size of 69.5 GB and RAID 0 fault tolerance.           |
             |                                                            |
             | Press [F8] to save the configuration                       |
             | Press [ESC] to cancel                                      |
             +------------------------------------------------------------+



     
     [F8] to save the configuration
     [ESC] to cancel 

    Saving configuration

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage



                      +----------------------------------------+
                      | Saving configuration...                |
                      +----------------------------------------+

    Configuration saved

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage




                      +----------------------------------------+
                      |        Configuration saved             |
                      |                                        |
                      |     Press [Enter] to continue          |
                      +----------------------------------------+



     [Enter] to continue

    View Logical Volume (Check the configuration)
        You can review your configuration.

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage


    +--------------------------Available Logical Drives----------------------------+
    | Logical Drive # 1, RAID   0,   69.5 GB,                    OK                |
    +------------------------------------------------------------------------------+



     [Enter] to view logical drive details
     [UP/DOWN ARROW] to select logical drive; [ESC] to return

    View logical drive details.
         If you type Enter key, you can review the drive details.

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage

     Logical Drive # 1, RAID 0, 69.5GB, Status OK


    +--------------------------Assigned Physical Drives----------------------------+
    | SCSI Port # 2, ID  3, COMPAQ       72.8GB Drive  OK                          |
    +------------------------------------------------------------------------------+



    +---------------------------Assigned Spare Drives------------------------------+
    | No Drives Present                                                            |
    +------------------------------------------------------------------------------+


     View Logical Drive
     [UP/DOWN ARROW] to scroll; [ESC] to return; [Tab] to navigate

    Delete logical drive

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage

    +--------------------------Available Logical Drives----------------------------+
    | Logical Drive # 1, RAID   0,   69.5 GB,                    OK                |
    +------------------------------------------------------------------------------+




     [F8] to delete the logical drive   
     [UP/DOWN ARROW] to scroll; [ESC] to return   

    Warning message for the logical drive deletion

     Option Rom Configuration for Arrays, version  2.36
     Copyright 2002 Hewlett-Packard Development Company, L.P.

     Controller: HP Smart Array SA6400
     Direct-Attached Storage


                 +--------------------------------------------------+
                 |                   Warning                        |
                 | This will result in complete data loss           |
                 | for this logical drive.                          |
                 |                                                  |
                 | You have selected to delete logical drive        |
                 | # 1, RAID 0 , 69.5GB with 1 physical drive(s)    |
                 |                                                  |
                 | Press [F3] to delete the logical drive           |
                 | Press [ESC] to cancel                            |
                 +--------------------------------------------------+


      [F3] to delete the logical drive
     [ESC] to cancel

    Before adding a logical drive
    =============================
    Here is the EFI mar output before adding a logical drive.

      fs0  : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part1,SigF5F6C7BA-8A85-11
    D9-8002-D6217B60E588)
      fs1  : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part3,SigF5F6C80A-8A85-11
    D9-8004-D6217B60E588)
      blk0 : Acpi(HWP0002,0)/Pci(3|0)/Ata(Primary,Master)
      blk1 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)
      blk2 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part1,SigF5F6C7BA-8A85-11
    D9-8002-D6217B60E588)
      blk3 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part2,SigF5F6C7E2-8A85-11
    D9-8003-D6217B60E588)
      blk4 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part3,SigF5F6C80A-8A85-11
    D9-8004-D6217B60E588)
      blk5 : Acpi(HWP0002,100)/Pci(1|1)/Scsi(Pun0,Lun0)

    After adding a logical drive
    ==============================
      Device mapping table
      fs0  : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part1,SigF5F6C7BA-8A85-11
    D9-8002-D6217B60E588)
      fs1  : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part3,SigF5F6C80A-8A85-11
    D9-8004-D6217B60E588)
      blk0 : Acpi(HWP0002,0)/Pci(3|0)/Ata(Primary,Master)
      blk1 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)
      blk2 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part1,SigF5F6C7BA-8A85-11
    D9-8002-D6217B60E588)
      blk3 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part2,SigF5F6C7E2-8A85-11
    D9-8003-D6217B60E588)
      blk4 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part3,SigF5F6C80A-8A85-11
    D9-8004-D6217B60E588)
      blk5 : Acpi(HWP0002,100)/Pci(1|1)/Scsi(Pun0,Lun0)
      blk6 : Acpi(HWP0002,400)/Pci(1|0)/Pci(4|0)/Scsi(Pun0,Lun0)

    Device tree
    ===========
    You can verify the EFI path with the devtree command. As you can see
    path Acpi(HWP0002,400) is assigned to the Smart Array 6400 Controller.

    Shell> devtree
    Device Tree
      Ctrl[04]
      Ctrl[06] VenHw(SysROM)
      Ctrl[0B] Acpi(HWP0002,0)
        Ctrl[14] Acpi(HWP0002,0)/Pci(1|0)
        Ctrl[15] Acpi(HWP0002,0)/Pci(1|1)
          Ctrl[3C] 16550 Serial UART Driver
            Ctrl[3D] VT-100+ Serial Console
              Ctrl[3A] Primary Console Input Device
              Ctrl[3B] Primary Console Output Device
              Ctrl[39] Primary Standard Error Device
        Ctrl[16] Usb Open Host Controller
          Ctrl[3E] Generic Usb Keyboard
            Ctrl[3A] Primary Console Input Device
        Ctrl[17] Usb Open Host Controller
          Ctrl[3F] Generic Usb Mouse
            Ctrl[3A] Primary Console Input Device
        Ctrl[18] Acpi(HWP0002,0)/Pci(2|2)
        Ctrl[19] PCI IDE/ATAPI Controller
          Ctrl[4F] DW-224E
        Ctrl[1A] Acpi(HWP0002,0)/Pci(4|0)
          Ctrl[3B] Primary Console Output Device
          Ctrl[39] Primary Standard Error Device
      Ctrl[0C] Acpi(HWP0002,100)
        Ctrl[1D] LSI Logic Ultra160 SCSI Controller
          Ctrl[50] HP 73.4GST373453LC      HPC3
            Ctrl[8E] FAT File System [FAT32] 500 MB
            Ctrl[8F] Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part2,SigF5F6C7E2
    -8A85-11D9-8003-D6217B60E588)
            Ctrl[90] FAT File System [FAT32] 400 MB
          Ctrl[51] HP      SAF-TE          1
        Ctrl[1E] LSI Logic Ultra160 SCSI Controller
          Ctrl[52] HP 73.4GST373453LC      HPC5
          Ctrl[53] HP      SAF-TE          1
        Ctrl[1F] Acpi(HWP0002,100)/Pci(2|0)
          Ctrl[54] Broadcom NetXtreme Gigabit Ethernet (BCM5701)
      Ctrl[0D] Acpi(HWP0002,200)
      Ctrl[0E] Acpi(HWP0002,400)
        Ctrl[22] Acpi(HWP0002,400)/Pci(1|0)
        Ctrl[23] Smart Array 6400 Controller
        Ctrl[24] LSI Logic Ultra160 SCSI Controller
      Ctrl[0F] Acpi(HWP0002,500)
      Ctrl[10] Acpi(HWP0002,600)
        Ctrl[25] Acpi(HWP0002,600)/Pci(1|0)
          Ctrl[55] Broadcom NetXtreme Gigabit Ethernet (BCM5701)
      Ctrl[4D] VenHw(D65A6B8C-71E5-4DF0-A909-F0D2992B5AA9)

    Once you configure logical drives, system won't prompt for ORCA
        during POST. In this case, press F8 key immediately after the
        smart array banner is displayed.

    EFI version 1.10 [14.62]
    EFI64 Running on Intel(R) Itanium Processor Family
    EFI 1.10 IPF server rx4640  3.10 [Tue Sep 30 14:14:27 2003] - HP
    0 0 0x0002B9 0x0000000000000013 EFI POST code
    Loading 'SysROM:Floating-Point Software Assistance Handler'...
    -- 'SysROM:Floating-Point Software Assistance Handler' returned Success
    Loading 'SysROM:Broadcom Gigabit Ethernet Driver'...

    Copyright (c) 2000-2004 Broadcom Corporation
    Broadcom NetXtreme Gigabit Ethernet EFI driver v7.0.3

    -- 'SysROM:Broadcom Gigabit Ethernet Driver' returned Success
    0 0 0x0002B9 0x0000000000000014 EFI POST code
    1 0 0x00020B 0x0000000000000006 EFI Launching Boot Manager
    0 0 0x000318 0x0000000000000030 EFI security system initialized
    0 0 0x0002B9 0x0000000000000015 EFI POST code
    0 0 0x0015B2 0x0000000066565549 boot time event
    Broadcom NetXtreme Gigabit Ethernet (BCM5701) is detected (PCI)
    Scsi(Pun4,Lun0) HP      SAF-TE          1



    HP Smart Array 6400-128 Controller       (version 2.34)
    1 Logical Drives

3
Hardware / HP Enterprise - Smart Update Firmware DVD 10.10
« on: July 20, 2018, 08:57:38 AM »
The Smart Update Firmware DVD delivers a collection of firmware for your ProLiant servers and options. Update your ProLiant firmware using one of the following methods; HP Smart Update Manager, ROMPaq (iLO only), or Online ROM flash components

https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=1121413&swItemId=MTX_4372f442c3424063809e3d9198&swEnvOid=4184#

This is the final version of the Smart Update Firmware DVD. The HP Service Pack for ProLiant (SPP) will replace the Smart Update Firmware DVD later this year. During this transition period, both products are released concurrently for this final time. The SPP 2012.06.0 contains the same content and functionality as the following products:

    Smart Update Firmware DVD version 10.10
    ProLiant Support Pack for Windows version 9.10
    ProLiant Support Pack for Linux version 9.10

After this release, the SPP will be the only product delivering components for HP ProLiant servers, options, and BladeSystems in a single package.

Type: Firmware (Entitlement Required) - DVD
Version: 10.10(4 Jun 2012)

Operating System(s):    
Microsoft Windows HPC Server 2008 R2 | Hide all
Microsoft Windows Server 2008 Foundation Edition
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 R2 Foundation Edition
Microsoft Windows Server 2008 W32
Microsoft Windows Server 2008 x64
Microsoft Windows Small Business Server 2011 Standard and Essentials
Red Hat Enterprise Linux 5 Server (x86)
Red Hat Enterprise Linux 5 Server (x86-64)
Red Hat Enterprise Linux 6 Server (x86)
Red Hat Enterprise Linux 6 Server (x86-64)
SUSE Linux Enterprise Server 10 (AMD64/EM64T)
SUSE Linux Enterprise Server 10 (x86)
SUSE Linux Enterprise Server 11 (AMD64/EM64T)
SUSE Linux Enterprise Server 11 (x86)
VMware ESX/ESXi 4.1
VMware ESXi 5.0

File name:    firmware-10.10-0.zip (1.4 GB)
Unsecured link to file: http://www.mediafire.com/file/9m4rhs9mny15da4/firmware-10.10-0.zip (only use this if you are out of support entitlement whit HPE and you are in a test environment)

4
Hardware / HP Enterprise - Smart Update Firmware DVD 9.30
« on: July 20, 2018, 08:33:16 AM »
The Smart Update Firmware DVD delivers a collection of firmware for your ProLiant servers and options. Update your ProLiant firmware using one of the following methods; HP Smart Update Manager, ROMPaq (iLO only), or Online ROM flash components

https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=1121413&swItemId=MTX_42012d3b9e264bfdbc1ba78f7b&swEnvOid=4184#

Type: Firmware (Entitlement Required) - DVD
Version: 9.30(5 May 2011)

Operating System(s):    
Microsoft Windows Server 2003 | Hide all
Microsoft Windows Server 2003 for 64-bit Extended Systems
Microsoft Windows Server 2008 Essential Business
Microsoft Windows Server 2008 Foundation Edition
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 R2 Foundation Edition
Microsoft Windows Server 2008 Small Business
Microsoft Windows Server 2008 W32
Microsoft Windows Server 2008 x64
Microsoft Windows Small Business Server 2011 Standard and Essentials
Novell NetWare 6.5
Red Hat Enterprise Linux 5 Server (x86)
Red Hat Enterprise Linux 5 Server (x86-64)
Red Hat Enterprise Linux 6 Server (x86)
Red Hat Enterprise Linux 6 Server (x86-64)
SCO Open UNIX 8
SCO UnixWare 7
SUSE Linux Enterprise Server 10 (AMD64/EM64T)
SUSE Linux Enterprise Server 10 (x86)
SUSE Linux Enterprise Server 11 (AMD64/EM64T)
SUSE Linux Enterprise Server 11 (x86)
VMware ESX/ESXi 4.0
VMware ESX/ESXi Server 3.5

File name:    firmware-9.30-0.zip (1.0 GB)


 Supported Hardware

    HP ProLiant BL685c G7 Server
    HP ProLiant BL685c G6 Server
    HP ProLiant BL685c G5 Server
    HP ProLiant BL685c Server
    HP ProLiant BL680c G7 Server
    HP ProLiant BL680c G5 Server
    HP ProLiant BL620c G7 Server
    HP ProLiant BL495c G6 Server
    HP ProLiant BL495c G5 Server
    HP ProLiant BL490c G6 Server
    HP ProLiant BL480c Server
    HP ProLiant BL465c G7 Server
    HP ProLiant BL465c G6 Server
    HP ProLiant BL465c G5 Server
    HP ProLiant BL465c Server
    HP ProLiant BL460c G7 Server
    HP ProLiant BL460c G6 Server
    HP ProLiant BL460c G5 Server
    HP ProLiant BL460c Server
    HP ProLiant BL280c G6 Server
    HP ProLiant BL260c G5 Server
    HP ProLiant BL2x220c G6 Server
    HP ProLiant BL2x220c G5 Server
    HP ProLiant DL980 G7 Server
    HP ProLiant DL785 G6 Server
    HP ProLiant DL785 G5 Server
    HP ProLiant DL585 G7 Server
    HP ProLiant DL585 G6 Server
    HP ProLiant DL585 G5 Server
    HP ProLiant DL585 G2 Server
    HP ProLiant DL580 G7 Server
    HP ProLiant DL580 G5 Server
    HP ProLiant DL385 G7 Server
    HP ProLiant DL385 G6 Server
    HP ProLiant DL385 G5p Server
    HP ProLiant DL385 G5 Server
    HP ProLiant DL385 G2 Server
    HP ProLiant DL380 G7 Server
    HP ProLiant DL380 G6 Server
    HP ProLiant DL380 G5 Server
    HP ProLiant DL370 G6 Server
    HP ProLiant DL365 G5 Server
    HP ProLiant DL365 Server
    HP ProLiant DL360 G7 Server
    HP ProLiant DL360 G6 Server
    HP ProLiant DL360 G5 Server
    HP ProLiant DL320 G6 Server
    HP ProLiant DL320 G5p Server
    HP ProLiant DL320 G5 Server
    HP ProLiant DL320s Server
    HP ProLiant DL180 G6 Server
    HP ProLiant DL4x170h G6 Server
    HP ProLiant DL2x170h G6 Server
    HP ProLiant DL170h G6 Server
    HP ProLiant DL165 G7 Server
    HP ProLiant DL160se G6 Server
    HP ProLiant DL160 G6 Server
    HP ProLiant DL120 G7 Server
    HP ProLiant DL120 G6 Server
    HP ProLiant ML370 G6 Server
    HP ProLiant ML370 G5 Server
    HP ProLiant ML350 G6 Server
    HP ProLiant ML350 G5 Server
    HP ProLiant ML330 G6 Server
    HP ProLiant ML310 G5p Server
    HP ProLiant ML310 G5 Server
    HP ProLiant ML150 G6 Server
    HP ProLiant ML110 G7 Server
    HP ProLiant ML110 G6 Server
    HP ProLiant SL390s G7 Server
    HP ProLiant SL2x170z G6 Server
    HP ProLiant SL170z G6 Server
    HP ProLiant SL170s G6 Server
    HP ProLiant SL165z G7 Server
    HP ProLiant SL165z G6 Server
    HP ProLiant SL165s G7 Server
    HP ProLiant SL160z G6 Server
    HP ProLiant SL160s G6 Server

5
Hardware / HP Enterprise - USB Key Utility
« on: July 20, 2018, 08:27:00 AM »
The HPE USB Key Utility is a Windows application that will allow the user to copy the ISO and CD contents to a USB memory key using SmartStart CD, Firmware Maintenance CD, Smart Update Firmware DVD, Intelligent Provisioning Recovery DVD, Service Pack for ProLiants or other supported products. Users may then run the ISO and CD applications from a USB key.

https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_357c87ee9b054ad7a631d9eaba#tab2

Type: Utility - Tools
Version:    2.1.0.0 (1 Apr 2016)

Operating System(s):
Microsoft Windows 7 (64-bit)
Microsoft Windows 7 Enterprise (64-bit)
Microsoft Windows 7 Professional (64-bit)
Microsoft Windows 8 (64-bit)
Microsoft Windows 8.1 (64-bit)
Microsoft Windows HPC Server 2008 R2
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2012
Microsoft Windows Server 2012 Essentials
Microsoft Windows Server 2012 R2
Microsoft Windows Storage Server 2008 R2
Microsoft Windows Storage Server 2008 x64 Editions
Microsoft Windows Storage Server 2012
Microsoft Windows Storage Server 2012 R2

File name:    cp028009.exe (2.1 MB)

Prerequisites:

One or more of the following:

    HP Service Pack for ProLiant
    HP SmartStart CD version 7.5x and greater.
    HP Firmware Maintenance CD version 7.5x and greater.
    HP Smart Update Firmware DVD version 9.00 and greater.
    HP Easy Set-Up CD version with G6 servers and greater.

And:

    Minimum 1GB USB 2.0 flash drive (maximum size is 32GB).

After successful installation of the HPE USB Key Utility, the USB flash drive can be used on supported ProLiant servers.

6
Linux and BSD / [How-To] Install OwnCloud on FreeBSD FAMP
« on: March 29, 2018, 03:23:13 PM »
[How-To] Install OwnCloud on FreeBSD FAMP

In this tutorial or guide I will show you how to setup and install the needed components for running your own private cloud server based on FreeBSD and OwnCloud, I will also attach the session log output of my own install at the bottom so you can read the proper output of the server install in full.

This guide is based on personal experience whit the different components and are also based on OwnClouds own documentation found at: https://doc.owncloud.org/server/latest/admin_manual/contents.html

One thing to note before beginning, this write up was done by request by a user, and while working on this project OwnCloud had several updates, and in the latest version decided to drop official support for FreeBSD installs, so if that is an issue for you then I suggest using a Linux flavor, you can still follow this guide for setting it up but you need to adjust some of the commands and folder loactions to mach your Linux system.

What is OwnCloud
OwnCloud is a PHP and MySQL based free and open source file sharing application platform which allows us to create our very own cloud storage platform. The OwnCloud server which is a free edition is released under GNU AGPLv3 license whereas the Enterprise edition is under OwnCloud Commercial license. It is a client-server architectural software in which, the files are stored on the server whereas the clients are used to access and share the files. The client for OwnCloud is available for every platform making it easy to manage and access the files from every devices.

Why FreeBSD
FreeBSD is a free and open source Unix-like operating system based on BSD systems. Unlike Linux, FreeBSD is developed as an entire operating system from kernel, device drivers to the userland utilities whereas Linux is a kernel with device drivers.

Currently while writing this article, the latest release of OwnCloud is 10.0.7 so, we'll be performing its setup on our freshly installed FreeBSD 11 server. I will only cover the minimal settings for getting OwnCloud up and running on FreeBSD with the basic configuration of FAMP stack

Some useful environment information:
Server Hostname: server
Server IP: 192.168.55.30
Server Netmask \ CIDR: 255.255.255.0 /24
Web address: http://server.it-monkey.lan/owncloud/

Routing and DNS information is handled by the pfSense network server where DNS Resolver is set whit Host Override for domain it-monkey.lan and server.it-monkey.lan pointing to IP 192.168.55.30 and this IP address is set to be staticly assign to the MAC Addr of the FreeBSD server through DHCP Static mapping.

I suggest you check if your router support this as it will make your access to the server much easier and cleaner

All configuration is done remotely over SSH connection using Putty from a Windows 7 client, as this is a headless server build from random parts I had available to use for this project, and to make it as common for most people that want to try something new.

Installing FAMP Stack
FAMP Stack is the combination of Apache web server, MySQL/MariaDB database server and PHP modules running on a FreeBSD server. FAMP is one of the widely used stack for hosting websites and web applications on servers. Here, we be installing FAMP stack in order to run our PHP based OwnCloud server.

This processes is pretty easy, you install the server OS (not covered in this guide), latest version of Apache web server, PHP and mySQL or MariaDB, we will be working whit the following versions:

FreeBSD 11.1
OwnCloud 10.0.7
Apache 2.4.29
PHP 7.1.15
mySQL 5.7.21

Preparing FreeBSD 11.1
Check current version: uname -a
Show current system info: neofetch (not installed by default)



Before installing any applications we need to make sure we have access to all the latest applications, versions and software available for the platform
Update package repository information:
sudo pkg update

Upgrade package repository information:
sudo pkg upgrade

When the repository is updated, we need to install the tools used in this guide
sudo pkg install curl wget vim nano gnupg

Apache:
The Apache HTTP Server Project is a collaborative software development effort aimed at creating a robust, commercial-grade, featureful, and freely-available source code implementation of an HTTP (Web) server. The project is jointly managed by a group of volunteers located around the world, using the Internet and the Web to communicate, plan, and develop the server and its related documentation. This project is part of the Apache Software Foundation. In addition, hundreds of users have contributed ideas, code, and documentation to the project. This file is intended to briefly describe the history of the Apache HTTP Server and recognize the many contributors.

Documentation: https://httpd.apache.org/docs/2.4/

Important files and locations:
Apache configuration file is: httpd.conf located at /usr/local/etc/apache24/httpd.conf
Default website folder: /usr/local/www/apache24/data
Apache logs: /var/log
Add-on modules are located in: /usr/local/etc/apache24/Includes/

Installing Apache:
sudo pkg install apache24

Now we need to set Apache to start automatically on boots:
sudo sysrc apache24_enable=YES

Now we have to set the default production configuration for the Apache web server: sudo cp /usr/local/etc/apache24/httpd.conf.sample /usr/local/etc/apache24/httpd.conf

Now we can start the web server:
sudo service apache24 start

When starting the Apache web server it is going to do a sanitycheck of its configuration, and since there is no static IP or DNS configuration on the server it is going to complain and warn you about this, this message can be ignored for now.

Test web server, open a web browser and test both IP and DNS access: http://192.168.55.30/ and http://server.it-monkey.lan/





PHP:
PHP is a server-side scripting language designed for web development but also used as a general-purpose programming language. It was originally created by Rasmus Lerdorf in 1994, the PHP reference implementation is now produced by The PHP Group. PHP originally stood for Personal Home Page, but it now stands for the recursive acronym PHP: Hypertext Preprocessor

PHP code may be embedded into HTML code, or it can be used in combination with various web template systems, web content management systems, and web frameworks. PHP code is usually processed by a PHP interpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. The web server combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface (CLI) and can be used to implement standalone graphical applications.

The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system and platform, free of charge.

Documentation: http://fi2.php.net/docs.php

Important PHP files:
PHP Apache module: /usr/local/etc/php.ini
PHP FastCGI Process Manager Global Directive: /usr/local/etc/php-fpm.conf
PHP FastCGI Process Manager Pool Directive: /usr/local/etc/phpfpm.d/www.conf

Install PHP, PHP Extension and needed modules:
sudo pkg install php71 php71-extensions mod_php71 php71-mysqli php71-gd php71-curl php71-zlib php71-zip php71-pdo_mysql php71-openssl php71-gmp php71-ldap php71-exif php71-fileinfo php71-mbstring php71-bcmath php71-bz2 php71-mcrypt php71-intl

Code tag for no line breaks:
Code: [Select]
sudo pkg install php71 php71-extensions mod_php71 php71-mysqli php71-gd php71-curl php71-zlib php71-zip php71-pdo_mysql php71-openssl php71-gmp php71-ldap php71-exif php71-fileinfo php71-mbstring php71-bcmath php71-bz2 php71-mcrypt php71-intl


Now we need to set the production environment instructions for PHP:
sudo cp /usr/local/etc/php.ini-production  /usr/local/etc/php.ini

We also need to configure PHP to listen on internal socket connections rather than IP and Ports that is done by editing the file  www.conf

In this file we need to check that it has the following valuses

listen = /var/run/php-fpm.sock
listen.owner = www
listen.group = www
listen.mode = 0660

sudo nano /usr/local/etc/php-fpm.d/www.conf

Content of /usr/local/etc/php-fpm.d/www.conf
Code: [Select]

;/usr/local/etc/php-fpm.d/www.conf
;
; Start a new pool named 'www'.
; the variable $pool can be used in any directive and will be replaced by the
; pool name ('www' here)
[www]

; Per pool prefix
; It only applies on the following directives:
; - 'access.log'
; - 'slowlog'
; - 'listen' (unixsocket)
; - 'chroot'
; - 'chdir'
; - 'php_values'
; - 'php_admin_values'
; When not set, the global prefix (or /usr/local) applies instead.
; Note: This directive can also be relative to the global prefix.
; Default Value: none
;prefix = /path/to/pools/$pool

; Unix user/group of processes
; Note: The user is mandatory. If the group is not set, the default user's group
;       will be used.
user = www
group = www

; The address on which to accept FastCGI requests.
; Valid syntaxes are:
;   'ip.add.re.ss:port'    - to listen on a TCP socket to a specific IPv4 address on
;                            a specific port;
;   '[ip:6:addr:ess]:port' - to listen on a TCP socket to a specific IPv6 address on
;                            a specific port;
;   'port'                 - to listen on a TCP socket to all addresses
;                            (IPv6 and IPv4-mapped) on a specific port;
;   '/path/to/unix/socket' - to listen on a unix socket.
; Note: This value is mandatory.
; listen = 127.0.0.1:9000
listen = /var/run/php-fpm.sock
listen.owner = www
listen.group = www
listen.mode = 0660

; Set listen(2) backlog.
; Default Value: 511 (-1 on FreeBSD and OpenBSD)
;listen.backlog = 511

; Set permissions for unix socket, if one is used. In Linux, read/write
; permissions must be set in order to allow connections from a web server. Many
; BSD-derived systems allow connections regardless of permissions.
; Default Values: user and group are set as the running user
;                 mode is set to 0660
;listen.owner = www
;listen.group = www
;listen.mode = 0660
; When POSIX Access Control Lists are supported you can set them using
; these options, value is a comma separated list of user/group names.
; When set, listen.owner and listen.group are ignored
;listen.acl_users =
;listen.acl_groups =

; List of addresses (IPv4/IPv6) of FastCGI clients which are allowed to connect.
; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original
; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address
; must be separated by a comma. If this value is left blank, connections will be
; accepted from any ip address.
; Default Value: any
;listen.allowed_clients = 127.0.0.1

; Specify the nice(2) priority to apply to the pool processes (only if set)
; The value can vary from -19 (highest priority) to 20 (lower priority)
; Note: - It will only work if the FPM master process is launched as root
;       - The pool processes will inherit the master process priority
;         unless it specified otherwise
; Default Value: no set
; process.priority = -19

; Choose how the process manager will control the number of child processes.
; Possible Values:
;   static  - a fixed number (pm.max_children) of child processes;
;   dynamic - the number of child processes are set dynamically based on the
;             following directives. With this process management, there will be
;             always at least 1 children.
;             pm.max_children      - the maximum number of children that can
;                                    be alive at the same time.
;             pm.start_servers     - the number of children created on startup.
;             pm.min_spare_servers - the minimum number of children in 'idle'
;                                    state (waiting to process). If the number
;                                    of 'idle' processes is less than this
;                                    number then some children will be created.
;             pm.max_spare_servers - the maximum number of children in 'idle'
;                                    state (waiting to process). If the number
;                                    of 'idle' processes is greater than this
;                                    number then some children will be killed.
;  ondemand - no children are created at startup. Children will be forked when
;             new requests will connect. The following parameter are used:
;             pm.max_children           - the maximum number of children that
;                                         can be alive at the same time.
;             pm.process_idle_timeout   - The number of seconds after which
;                                         an idle process will be killed.
; Note: This value is mandatory.
pm = dynamic

; The number of child processes to be created when pm is set to 'static' and the
; maximum number of child processes when pm is set to 'dynamic' or 'ondemand'.
; This value sets the limit on the number of simultaneous requests that will be
; served. Equivalent to the ApacheMaxClients directive with mpm_prefork.
; Equivalent to the PHP_FCGI_CHILDREN environment variable in the original PHP
; CGI. The below defaults are based on a server without much resources. Don't
; forget to tweak pm.* to fit your needs.
; Note: Used when pm is set to 'static', 'dynamic' or 'ondemand'
; Note: This value is mandatory.
pm.max_children = 5

; The number of child processes created on startup.
; Note: Used only when pm is set to 'dynamic'
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 2

; The desired minimum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.min_spare_servers = 1

; The desired maximum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.max_spare_servers = 3

; The number of seconds after which an idle process will be killed.
; Note: Used only when pm is set to 'ondemand'
; Default Value: 10s
;pm.process_idle_timeout = 10s;

; The number of requests each child process should execute before respawning.
; This can be useful to work around memory leaks in 3rd party libraries. For
; endless request processing specify '0'. Equivalent to PHP_FCGI_MAX_REQUESTS.
; Default Value: 0
;pm.max_requests = 500

; The URI to view the FPM status page. If this value is not set, no URI will be
; recognized as a status page. It shows the following informations:
;   pool                 - the name of the pool;
;   process manager      - static, dynamic or ondemand;
;   start time           - the date and time FPM has started;
;   start since          - number of seconds since FPM has started;
;   accepted conn        - the number of request accepted by the pool;
;   listen queue         - the number of request in the queue of pending
;                          connections (see backlog in listen(2));
;   max listen queue     - the maximum number of requests in the queue
;                          of pending connections since FPM has started;
;   listen queue len     - the size of the socket queue of pending connections;
;   idle processes       - the number of idle processes;
;   active processes     - the number of active processes;
;   total processes      - the number of idle + active processes;
;   max active processes - the maximum number of active processes since FPM
;                          has started;
;   max children reached - number of times, the process limit has been reached,
;                          when pm tries to start more children (works only for
;                          pm 'dynamic' and 'ondemand');
; Value are updated in real time.
; Example output:
;   pool:                 www
;   process manager:      static
;   start time:           01/Jul/2011:17:53:49 +0200
;   start since:          62636
;   accepted conn:        190460
;   listen queue:         0
;   max listen queue:     1
;   listen queue len:     42
;   idle processes:       4
;   active processes:     11
;   total processes:      15
;   max active processes: 12
;   max children reached: 0
;
; By default the status page output is formatted as text/plain. Passing either
; 'html', 'xml' or 'json' in the query string will return the corresponding
; output syntax. Example:
;   http://www.foo.bar/status
;   http://www.foo.bar/status?json
;   http://www.foo.bar/status?html
;   http://www.foo.bar/status?xml
;
; By default the status page only outputs short status. Passing 'full' in the
; query string will also return status for each pool process.
; Example:
;   http://www.foo.bar/status?full
;   http://www.foo.bar/status?json&full
;   http://www.foo.bar/status?html&full
;   http://www.foo.bar/status?xml&full
; The Full status returns for each process:
;   pid                  - the PID of the process;
;   state                - the state of the process (Idle, Running, ...);
;   start time           - the date and time the process has started;
;   start since          - the number of seconds since the process has started;
;   requests             - the number of requests the process has served;
;   request duration     - the duration in µs of the requests;
;   request method       - the request method (GET, POST, ...);
;   request URI          - the request URI with the query string;
;   content length       - the content length of the request (only with POST);
;   user                 - the user (PHP_AUTH_USER) (or '-' if not set);
;   script               - the main script called (or '-' if not set);
;   last request cpu     - the %cpu the last request consumed
;                          it's always 0 if the process is not in Idle state
;                          because CPU calculation is done when the request
;                          processing has terminated;
;   last request memory  - the max amount of memory the last request consumed
;                          it's always 0 if the process is not in Idle state
;                          because memory calculation is done when the request
;                          processing has terminated;
; If the process is in Idle state, then informations are related to the
; last request the process has served. Otherwise informations are related to
; the current request being served.
; Example output:
;   ************************
;   pid:                  31330
;   state:                Running
;   start time:           01/Jul/2011:17:53:49 +0200
;   start since:          63087
;   requests:             12808
;   request duration:     1250261
;   request method:       GET
;   request URI:          /test_mem.php?N=10000
;   content length:       0
;   user:                 -
;   script:               /home/fat/web/docs/php/test_mem.php
;   last request cpu:     0.00
;   last request memory:  0
;
; Note: There is a real-time FPM status monitoring sample web page available
;       It's available in: /usr/local/share/php/fpm/status.html
;
; Note: The value must start with a leading slash (/). The value can be
;       anything, but it may not be a good idea to use the .php extension or it
;       may conflict with a real PHP file.
; Default Value: not set
;pm.status_path = /status

; The ping URI to call the monitoring page of FPM. If this value is not set, no
; URI will be recognized as a ping page. This could be used to test from outside
; that FPM is alive and responding, or to
; - create a graph of FPM availability (rrd or such);
; - remove a server from a group if it is not responding (load balancing);
; - trigger alerts for the operating team (24/7).
; Note: The value must start with a leading slash (/). The value can be
;       anything, but it may not be a good idea to use the .php extension or it
;       may conflict with a real PHP file.
; Default Value: not set
;ping.path = /ping

; This directive may be used to customize the response of a ping request. The
; response is formatted as text/plain with a 200 response code.
; Default Value: pong
;ping.response = pong

; The access log file
; Default: not set
;access.log = log/$pool.access.log

; The access log format.
; The following syntax is allowed
;  %%: the '%' character
;  %C: %CPU used by the request
;      it can accept the following format:
;      - %{user}C for user CPU only
;      - %{system}C for system CPU only
;      - %{total}C  for user + system CPU (default)
;  %d: time taken to serve the request
;      it can accept the following format:
;      - %{seconds}d (default)
;      - %{miliseconds}d
;      - %{mili}d
;      - %{microseconds}d
;      - %{micro}d
;  %e: an environment variable (same as $_ENV or $_SERVER)
;      it must be associated with embraces to specify the name of the env
;      variable. Some exemples:
;      - server specifics like: %{REQUEST_METHOD}e or %{SERVER_PROTOCOL}e
;      - HTTP headers like: %{HTTP_HOST}e or %{HTTP_USER_AGENT}e
;  %f: script filename
;  %l: content-length of the request (for POST request only)
;  %m: request method
;  %M: peak of memory allocated by PHP
;      it can accept the following format:
;      - %{bytes}M (default)
;      - %{kilobytes}M
;      - %{kilo}M
;      - %{megabytes}M
;      - %{mega}M
;  %n: pool name
;  %o: output header
;      it must be associated with embraces to specify the name of the header:
;      - %{Content-Type}o
;      - %{X-Powered-By}o
;      - %{Transfert-Encoding}o
;      - ....
;  %p: PID of the child that serviced the request
;  %P: PID of the parent of the child that serviced the request
;  %q: the query string
;  %Q: the '?' character if query string exists
;  %r: the request URI (without the query string, see %q and %Q)
;  %R: remote IP address
;  %s: status (response code)
;  %t: server time the request was received
;      it can accept a strftime(3) format:
;      %d/%b/%Y:%H:%M:%S %z (default)
;      The strftime(3) format must be encapsuled in a %{<strftime_format>}t tag
;      e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t
;  %T: time the log has been written (the request has finished)
;      it can accept a strftime(3) format:
;      %d/%b/%Y:%H:%M:%S %z (default)
;      The strftime(3) format must be encapsuled in a %{<strftime_format>}t tag
;      e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t
;  %u: remote user
;
; Default: "%R - %u %t \"%m %r\" %s"
;access.format = "%R - %u %t \"%m %r%Q%q\" %s %f %{mili}d %{kilo}M %C%%"

; The log file for slow requests
; Default Value: not set
; Note: slowlog is mandatory if request_slowlog_timeout is set
;slowlog = log/$pool.log.slow

; The timeout for serving a single request after which a PHP backtrace will be
; dumped to the 'slowlog' file. A value of '0s' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_slowlog_timeout = 0

; The timeout for serving a single request after which the worker process will
; be killed. This option should be used when the 'max_execution_time' ini option
; does not stop script execution for some reason. A value of '0' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_terminate_timeout = 0

; Set open file descriptor rlimit.
; Default Value: system defined value
;rlimit_files = 1024

; Set max core size rlimit.
; Possible Values: 'unlimited' or an integer greater or equal to 0
; Default Value: system defined value
;rlimit_core = 0

; Chroot to this directory at the start. This value must be defined as an
; absolute path. When this value is not set, chroot is not used.
; Note: you can prefix with '$prefix' to chroot to the pool prefix or one
; of its subdirectories. If the pool prefix is not set, the global prefix
; will be used instead.
; Note: chrooting is a great security feature and should be used whenever
;       possible. However, all PHP paths will be relative to the chroot
;       (error_log, sessions.save_path, ...).
; Default Value: not set
;chroot =

; Chdir to this directory at the start.
; Note: relative path can be used.
; Default Value: current directory or / when chroot
;chdir = /var/www

; Redirect worker stdout and stderr into main error log. If not set, stdout and
; stderr will be redirected to /dev/null according to FastCGI specs.
; Note: on highloaded environement, this can cause some delay in the page
; process time (several ms).
; Default Value: no
;catch_workers_output = yes

; Clear environment in FPM workers
; Prevents arbitrary environment variables from reaching FPM worker processes
; by clearing the environment in workers before env vars specified in this
; pool configuration are added.
; Setting to "no" will make all environment variables available to PHP code
; via getenv(), $_ENV and $_SERVER.
; Default Value: yes
;clear_env = no

; Limits the extensions of the main script FPM will allow to parse. This can
; prevent configuration mistakes on the web server side. You should only limit
; FPM to .php extensions to prevent malicious users to use other extensions to
; execute php code.
; Note: set an empty value to allow all extensions.
; Default Value: .php
;security.limit_extensions = .php .php3 .php4 .php5 .php7

; Pass environment variables like LD_LIBRARY_PATH. All $VARIABLEs are taken from
; the current environment.
; Default Value: clean env
;env[HOSTNAME] = $HOSTNAME
;env[PATH] = /usr/local/bin:/usr/bin:/bin
;env[TMP] = /tmp
;env[TMPDIR] = /tmp
;env[TEMP] = /tmp

; Additional php.ini defines, specific to this pool of workers. These settings
; overwrite the values previously defined in the php.ini. The directives are the
; same as the PHP SAPI:
;   php_value/php_flag             - you can set classic ini defines which can
;                                    be overwritten from PHP call 'ini_set'.
;   php_admin_value/php_admin_flag - these directives won't be overwritten by
;                                     PHP call 'ini_set'
; For php_*flag, valid values are on, off, 1, 0, true, false, yes or no.

; Defining 'extension' will load the corresponding shared extension from
; extension_dir. Defining 'disable_functions' or 'disable_classes' will not
; overwrite previously defined php.ini values, but will append the new value
; instead.

; Note: path INI options can be relative and will be expanded with the prefix
; (pool, global or /usr/local)

; Default Value: nothing is defined by default except the values in php.ini and
;                specified at startup with the -d argument
;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f www@my.domain.com
;php_flag[display_errors] = off
;php_admin_value[error_log] = /var/log/fpm-php.www.log
;php_admin_flag[log_errors] = on
;php_admin_value[memory_limit] = 32M


Set PHP to run at bootup:
sudo sysrc php_fpm_enable=YES

Start PHP:
sudo service php-fpm start

Set the PHP Configuration for Apache webserver:
sudo nano /usr/local/etc/apache24/Includes/php.conf

Here you are creating a new config file, and need to add the following code:

Content of /usr/local/etc/apache24/Includes/php.conf
Code: [Select]
<IfModule dir_module>
    DirectoryIndex index.php index.html
    <FilesMatch "\.php$">
        SetHandler application/x-httpd-php
    </FilesMatch>
    <FilesMatch "\.phps$">
        SetHandler application/x-httpd-php-source
    </FilesMatch>
</IfModule>

Now we need to enable the PHP modules in Apache web server:
sudo nano /usr/local/etc/apache24/httpd.conf

Here we need to enable SSL and PHP modules and add the following code:
php7_module:
<IfModule php7_module>
        AddType application/x-httpd-php .php
</IfModule>

dir_module:
<IfModule dir_module>
    DirectoryIndex index.php index.html
</IfModule>

Content of /usr/local/etc/apache24/httpd.conf
Code: [Select]

# /usr/local/etc/apache24/httpd.conf
#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned. 
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
# will be interpreted as '/logs/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/usr/local"

#
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
#
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
#
# Mutex default:/var/run

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
#LoadModule mpm_event_module libexec/apache24/mod_mpm_event.so
LoadModule mpm_prefork_module libexec/apache24/mod_mpm_prefork.so
#LoadModule mpm_worker_module libexec/apache24/mod_mpm_worker.so
LoadModule authn_file_module libexec/apache24/mod_authn_file.so
#LoadModule authn_dbm_module libexec/apache24/mod_authn_dbm.so
#LoadModule authn_anon_module libexec/apache24/mod_authn_anon.so
#LoadModule authn_dbd_module libexec/apache24/mod_authn_dbd.so
#LoadModule authn_socache_module libexec/apache24/mod_authn_socache.so
LoadModule authn_core_module libexec/apache24/mod_authn_core.so
LoadModule authz_host_module libexec/apache24/mod_authz_host.so
LoadModule authz_groupfile_module libexec/apache24/mod_authz_groupfile.so
LoadModule authz_user_module libexec/apache24/mod_authz_user.so
#LoadModule authz_dbm_module libexec/apache24/mod_authz_dbm.so
#LoadModule authz_owner_module libexec/apache24/mod_authz_owner.so
#LoadModule authz_dbd_module libexec/apache24/mod_authz_dbd.so
LoadModule authz_core_module libexec/apache24/mod_authz_core.so
#LoadModule authnz_fcgi_module libexec/apache24/mod_authnz_fcgi.so
LoadModule access_compat_module libexec/apache24/mod_access_compat.so
LoadModule auth_basic_module libexec/apache24/mod_auth_basic.so
#LoadModule auth_form_module libexec/apache24/mod_auth_form.so
#LoadModule auth_digest_module libexec/apache24/mod_auth_digest.so
#LoadModule allowmethods_module libexec/apache24/mod_allowmethods.so
#LoadModule file_cache_module libexec/apache24/mod_file_cache.so
#LoadModule cache_module libexec/apache24/mod_cache.so
#LoadModule cache_disk_module libexec/apache24/mod_cache_disk.so
#LoadModule cache_socache_module libexec/apache24/mod_cache_socache.so
#LoadModule socache_shmcb_module libexec/apache24/mod_socache_shmcb.so
#LoadModule socache_dbm_module libexec/apache24/mod_socache_dbm.so
#LoadModule socache_memcache_module libexec/apache24/mod_socache_memcache.so
#LoadModule watchdog_module libexec/apache24/mod_watchdog.so
#LoadModule macro_module libexec/apache24/mod_macro.so
#LoadModule dbd_module libexec/apache24/mod_dbd.so
#LoadModule dumpio_module libexec/apache24/mod_dumpio.so
#LoadModule buffer_module libexec/apache24/mod_buffer.so
#LoadModule data_module libexec/apache24/mod_data.so
#LoadModule ratelimit_module libexec/apache24/mod_ratelimit.so
LoadModule reqtimeout_module libexec/apache24/mod_reqtimeout.so
#LoadModule ext_filter_module libexec/apache24/mod_ext_filter.so
#LoadModule request_module libexec/apache24/mod_request.so
#LoadModule include_module libexec/apache24/mod_include.so
LoadModule filter_module libexec/apache24/mod_filter.so
#LoadModule reflector_module libexec/apache24/mod_reflector.so
#LoadModule substitute_module libexec/apache24/mod_substitute.so
#LoadModule sed_module libexec/apache24/mod_sed.so
#LoadModule charset_lite_module libexec/apache24/mod_charset_lite.so
#LoadModule deflate_module libexec/apache24/mod_deflate.so
#LoadModule xml2enc_module libexec/apache24/mod_xml2enc.so
#LoadModule proxy_html_module libexec/apache24/mod_proxy_html.so
LoadModule mime_module libexec/apache24/mod_mime.so
LoadModule log_config_module libexec/apache24/mod_log_config.so
#LoadModule log_debug_module libexec/apache24/mod_log_debug.so
#LoadModule log_forensic_module libexec/apache24/mod_log_forensic.so
#LoadModule logio_module libexec/apache24/mod_logio.so
LoadModule env_module libexec/apache24/mod_env.so
#LoadModule mime_magic_module libexec/apache24/mod_mime_magic.so
#LoadModule cern_meta_module libexec/apache24/mod_cern_meta.so
#LoadModule expires_module libexec/apache24/mod_expires.so
LoadModule headers_module libexec/apache24/mod_headers.so
#LoadModule usertrack_module libexec/apache24/mod_usertrack.so
#LoadModule unique_id_module libexec/apache24/mod_unique_id.so
LoadModule setenvif_module libexec/apache24/mod_setenvif.so
LoadModule version_module libexec/apache24/mod_version.so
#LoadModule remoteip_module libexec/apache24/mod_remoteip.so
#LoadModule proxy_module libexec/apache24/mod_proxy.so
#LoadModule proxy_connect_module libexec/apache24/mod_proxy_connect.so
#LoadModule proxy_ftp_module libexec/apache24/mod_proxy_ftp.so
#LoadModule proxy_http_module libexec/apache24/mod_proxy_http.so
#LoadModule proxy_fcgi_module libexec/apache24/mod_proxy_fcgi.so
#LoadModule proxy_scgi_module libexec/apache24/mod_proxy_scgi.so
#LoadModule proxy_fdpass_module libexec/apache24/mod_proxy_fdpass.so
#LoadModule proxy_wstunnel_module libexec/apache24/mod_proxy_wstunnel.so
#LoadModule proxy_ajp_module libexec/apache24/mod_proxy_ajp.so
#LoadModule proxy_balancer_module libexec/apache24/mod_proxy_balancer.so
#LoadModule proxy_express_module libexec/apache24/mod_proxy_express.so
#LoadModule proxy_hcheck_module libexec/apache24/mod_proxy_hcheck.so
#LoadModule session_module libexec/apache24/mod_session.so
#LoadModule session_cookie_module libexec/apache24/mod_session_cookie.so
#LoadModule session_crypto_module libexec/apache24/mod_session_crypto.so
#LoadModule session_dbd_module libexec/apache24/mod_session_dbd.so
#LoadModule slotmem_shm_module libexec/apache24/mod_slotmem_shm.so
#LoadModule slotmem_plain_module libexec/apache24/mod_slotmem_plain.so
LoadModule ssl_module libexec/apache24/mod_ssl.so
#LoadModule dialup_module libexec/apache24/mod_dialup.so
#LoadModule http2_module libexec/apache24/mod_http2.so
#LoadModule proxy_http2_module libexec/apache24/mod_proxy_http2.so
#LoadModule lbmethod_byrequests_module libexec/apache24/mod_lbmethod_byrequests.so
#LoadModule lbmethod_bytraffic_module libexec/apache24/mod_lbmethod_bytraffic.so
#LoadModule lbmethod_bybusyness_module libexec/apache24/mod_lbmethod_bybusyness.so
#LoadModule lbmethod_heartbeat_module libexec/apache24/mod_lbmethod_heartbeat.so
LoadModule unixd_module libexec/apache24/mod_unixd.so
#LoadModule heartbeat_module libexec/apache24/mod_heartbeat.so
#LoadModule heartmonitor_module libexec/apache24/mod_heartmonitor.so
#LoadModule dav_module libexec/apache24/mod_dav.so
LoadModule status_module libexec/apache24/mod_status.so
LoadModule autoindex_module libexec/apache24/mod_autoindex.so
#LoadModule asis_module libexec/apache24/mod_asis.so
#LoadModule info_module libexec/apache24/mod_info.so
<IfModule !mpm_prefork_module>
#LoadModule cgid_module libexec/apache24/mod_cgid.so
</IfModule>
<IfModule mpm_prefork_module>
#LoadModule cgi_module libexec/apache24/mod_cgi.so
</IfModule>
#LoadModule dav_fs_module libexec/apache24/mod_dav_fs.so
#LoadModule dav_lock_module libexec/apache24/mod_dav_lock.so
#LoadModule vhost_alias_module libexec/apache24/mod_vhost_alias.so
#LoadModule negotiation_module libexec/apache24/mod_negotiation.so
LoadModule dir_module libexec/apache24/mod_dir.so
#LoadModule imagemap_module libexec/apache24/mod_imagemap.so
#LoadModule actions_module libexec/apache24/mod_actions.so
#LoadModule speling_module libexec/apache24/mod_speling.so
#LoadModule userdir_module libexec/apache24/mod_userdir.so
LoadModule alias_module libexec/apache24/mod_alias.so
#LoadModule rewrite_module libexec/apache24/mod_rewrite.so
LoadModule php7_module        libexec/apache24/libphp7.so

<IfModule php7_module>
        AddType application/x-httpd-php .php
</IfModule>

# Third party modules
IncludeOptional etc/apache24/modules.d/[0-9][0-9][0-9]_*.conf
 
<IfModule unixd_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch. 
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User www
Group www

</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin you@example.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
    AllowOverride none
    Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/usr/local/www/apache24/data"
<Directory "/usr/local/www/apache24/data">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   AllowOverride FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.php index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
    Require all denied
</Files>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "/var/log/httpd-error.log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "/var/log/httpd-access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "/var/log/httpd-access.log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/usr/local/www/apache24/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock cgisock
</IfModule>

#
# "/usr/local/www/apache24/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/usr/local/www/apache24/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>

<IfModule headers_module>
    #
    # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied
    # backend servers which have lingering "httpoxy" defects.
    # 'Proxy' request header is undefined by the IETF, not listed by IANA
    #
    RequestHeader unset Proxy early
</IfModule>

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig etc/apache24/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile etc/apache24/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
#EnableSendfile on

# Supplemental configuration
#
# The configuration files in the etc/apache24/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include etc/apache24/extra/httpd-mpm.conf

# Multi-language error messages
#Include etc/apache24/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include etc/apache24/extra/httpd-autoindex.conf

# Language settings
#Include etc/apache24/extra/httpd-languages.conf

# User home directories
#Include etc/apache24/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include etc/apache24/extra/httpd-info.conf

# Virtual hosts
#Include etc/apache24/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include etc/apache24/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include etc/apache24/extra/httpd-dav.conf

# Various default settings
#Include etc/apache24/extra/httpd-default.conf

# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include etc/apache24/extra/proxy-html.conf
</IfModule>

# Secure (SSL/TLS) connections
#Include etc/apache24/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

Include etc/apache24/Includes/*.conf


Now we need to create a PHP Info \ Diagnostics page to check if all is working correctly:
sudo nano /usr/local/www/apache24/data/phpinfo.php

Content of /usr/local/www/apache24/data/phpinfo.php
Code: [Select]
<?php phpinfo();  ?>

Now we need to restart Apache web server since we have done alot of configuration changes that needs to be reloaded: sudo service apache24 restart

Test web server, open a web browser and test both IP and DNS access: http://192.168.55.30/phpinfo.php and http://server.it-monkey.lan/phpinfo.php





Now that you have checked that everything is working correctly whit Apache and PHP, it is time to install and configure the Database server mySQL v5.7

mySQL:
mySQL is the world's most popular open source database. With its proven performance, reliability and ease-of-use, mySQL has become the leading database choice for web-based applications, used by high profile web properties including Facebook, Twitter, YouTube, Yahoo! and many more.

Oracle drives mySQL innovation, delivering new capabilities to power next generation web, cloud, mobile and embedded applications.

Documentation: https://dev.mysql.com/doc/refman/5.7/en/introduction.html

Install mySQL:
sudo pkg install mysql57-server

Set mySQL to automatically start at bootup:
sudo sysrc mysql_enable=YES

Start mySQL Server:
sudo service mysql-server start

Secure the Database SQL Server: sudo mysql_secure_installation
- Would you like to setup VALIDATE PASSWORD plugin?: yes
There are three levels of password validation policy:

LOW    Length >= 8
MEDIUM Length >= 8, numeric, mixed case, and special characters
STRONG Length >= 8, numeric, mixed case, special characters and dictionary                  file

Please enter 0 = LOW, 1 = MEDIUM and 2 = STRONG: 1
- Change the password for root ?: yes
New password: MySexyPassword123.
Re-enter new password: MySexyPassword123.

- Do you wish to continue with the password provided?: yes
- Remove anonymous users?: yes
- Disallow root login remotely?: yes
- Remove test database and access to it?: yes
- Remove test database and access to it?: yes
- Reload privilege tables now?: yes

Open mySQL Server to create the needed Databases and access that is required by OwnCloud: sudo mysql -u root -p

Now there is a bug in the SQL secure installation process that make us to reset the password for root user before creating the databases and access:
ALTER USER 'root'@'localhost' IDENTIFIED BY 'MySexyPassword123.';

Then we can create the database: ownclouddb, and the admin user: ocadmin

CREATE DATABASE ownclouddb;
CREATE USER ocadmin@localhost IDENTIFIED BY 'MySexyPassword123.';
GRANT ALL PRIVILEGES ON ownclouddb.* TO 'ocadmin'@'localhost';
FLUSH PRIVILEGES;
EXIT;

Now we have done the minimum FAMP configuration for OwnCloud to run on FreeBSD, now we are just missing a few environment configurations before installing the OwnCloud package. We start by creating the SSL Certs so we can use HTTPS connection for accessing the server

In this guide we will be using the self signed SSL Cert, but the process for generating a self signed cert and a signed cert is identical as you need to generate a CSR and PEM file and a private and public key pair, if you follow this process and give the correct details, you can send the CSR file to a Certificate Authority and get it publicly signed and validated for your server

Make the SSL Cert directory:
sudo mkdir -p /usr/local/etc/ssl/self-cert/owncloud/

Move to the SSL Cert directory:
cd /usr/local/etc/ssl/self-cert/owncloud/

Generating CSR and PEM file:
sudo openssl req -config /etc/ssl/openssl.cnf -new -out /usr/local/etc/ssl/self-cert/owncloud/owncloud.csr -keyout /usr/local/etc/ssl/self-cert/owncloud/owncloud.pem

Enter PEM pass phrase: MySexyPassword123.
Verifying - Enter PEM pass phrase: MySexyPassword123.

You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but for some fields there will be a default value,
If you enter “ . “ the field will be left blank(not recommended).

Country Name (2 letter code) [AU]:
State or Province Name (full name) [Some-State]:
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:
Organizational Unit Name (eg, section) []:
Common Name (e.g. server FQDN or YOUR name) []:
Email Address []:

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:

My server is located in Drammen, Norway so the form will look like this for me, and you have to adjust this to your server or organisation locations, if you are a home user the important part here is Country, City, Common Name and Email are correct and you can leave the rest empty

Common Name needs to be the FQDN and or Public IP of the server if you are going to have it accessed for the Internet

Country Name (2 letter code) [AU]: NO
State or Province Name (full name) [Some-State]: Buskerud
Locality Name (eg, city) []: Drammen
Organization Name (eg, company) [Internet Widgits Pty Ltd]: IT-Monkey
Organizational Unit Name (eg, section) []: IT
Common Name (e.g. server FQDN or YOUR name) []: server.it-monkey.lan
Email Address []: admin@it-monkey.lan

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []: MySexyPassword123.
An optional company name []: IT-Monkey

Generating RSA key:
sudo openssl rsa -in /usr/local/etc/ssl/self-cert/owncloud/owncloud.pem -out /usr/local/etc/ssl/self-cert/owncloud/owncloud.key

Enter pass phrase for /usr/local/etc/ssl/self-cert/owncloud/owncloud.pem: MySexyPassword123.

Sign the CRT and PEM file whit the RSA Key valid for 3 years:
sudo openssl x509 -in /usr/local/etc/ssl/self-cert/owncloud/owncloud.csr -out /usr/local/etc/ssl/self-cert/owncloud/owncloud.crt -req -signkey /usr/local/etc/ssl/self-cert/owncloud/owncloud.key -days 1095

Set the correct file permissions for the certificates:
sudo chmod 600 *

Finally we come to the process for getting OwnCloud on our system, we start by creating the folder that will hold the files for OwnCloud application

Creating the OwnCloud folder under Apache web server:
sudo mkdir -p /usr/local/www/apache24/data/owncloud/

Set the correct premission so Apache web server can read the files:
sudo chown -R www:www /usr/local/www/apache24/data/owncloud/
 
We can now download the OwnCloud software to our server, the current way to do that is to use wget or curl and point it at the URL holding the tar install file of OwnCloud, these URLs changes often so check OwnClouds website for the current version

We only need these files temporarily so we move to the system temp folder:
cd /tmp

Now we need to download the OwnCloud software to our server, the current way to do that is to use wget or curl and point it at the URL holding the tar install file of OwnCloud, these urls changes often so check OwnClouds website for the current version

Current files to be downloaded:
wget https://download.owncloud.org/community/owncloud-10.0.7.tar.bz2
wget https://download.owncloud.org/community/owncloud-10.0.7.tar.bz2.sha256
wget https://download.owncloud.org/community/owncloud-10.0.7.tar.bz2.asc
wget https://owncloud.org/owncloud.asc

Verifying the downloaded files:
sudo gpg --import owncloud.asc
sudo sha256 -c owncloud-10.0.7.tar.bz2.sha256 -s owncloud-10.0.7.tar.bz2
sudo gpg --verify owncloud-10.0.7.tar.bz2.sha256 owncloud-10.0.7.tar.bz2

After you have verified the files, you need to extract them from the tar archive
sudo tar -xjf owncloud-10.0.7.tar.bz2

Now we want to move the files to the directory we created for it under Apache web server
sudo cp -r owncloud/* /usr/local/www/apache24/data/owncloud/

Last thing to do is to restart the Apache web server:
sudo service apache24 restart

Now everything should be installed and working and when you open your web browser and navigate to http://192.168.55.30/owncloud/ or http://server.it-monkey.lan/owncloud/ you should see the OwnCloud setup page





Server output
Code: [Select]


=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.03.28 11:10:04 =~=~=~=~=~=~=~=~=~=~=~=
login as: edd
Using keyboard-interactive authentication.
Password for edd@server:
Last login: Mon Mar 26 10:37:58 2018 from 192.168.55.150

FreeBSD 11.1-RELEASE (GENERIC) #0 r321309: Fri Jul 21 02:08:28 UTC 2017

Welcome to FreeBSD!

Release Notes, Errata: https://www.FreeBSD.org/releases/
Security Advisories: https://www.FreeBSD.org/security/
FreeBSD Handbook: https://www.FreeBSD.org/handbook/
FreeBSD FAQ: https://www.FreeBSD.org/faq/
Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/
FreeBSD Forums: https://forums.FreeBSD.org/

Documents installed with the system are in the /usr/local/share/doc/freebsd/
directory, or can be installed later with:  pkg install en-freebsd-doc
For other languages, replace "en" with a language code like de or fr.

Show the version of FreeBSD installed:  freebsd-version ; uname -a
Please include that output and any error messages when posting questions.
Introduction to manual pages:  man man
FreeBSD directory layout:      man hier

Edit /etc/motd to change this login announcement.
In order to make fetch (the FreeBSD downloading tool) ask for
username/password when it encounters a password-protected web page, you can set
the environment variable HTTP_AUTH to 'basic:*'.

$ uname  -a
FreeBSD server 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017     root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

$ neofetch
   ```                        `    edd@server
  ` `.....---.......--.```   -/    ----------
  +o   .--`         /y:`      +.   OS: FreeBSD 11.1-RELEASE amd64
   yo`:.            :o      `+-    Uptime: 1 day, 18 hours, 50 mins
    y/               -/`   -o/     Packages: 126
   .-                  ::/sy+:.    Shell: sh
   /                     `--  /    Terminal: /dev/pts/0
  `:                          :`   CPU: Intel i7-4770 (4) @ 3.392GHz
  `:                          :`   GPU: SVGA II Adapter
   /                          /    Memory: 1641MiB / 2012MiB
   .-                        -.
    --                      -.
     `:`                  `:`
       .--             `--.
          .---.....----.
$

  Updating the package repositories
$ sudo pkg update
Updating FreeBSD repository catalogue...
Fetching meta.txz:   0%
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01   
Fetching packagesite.txz:   0%
Fetching packagesite.txz:   6%  392 KiB 401.4kB/s    00:14 ETA
Fetching packagesite.txz:  54%    3 MiB   2.9MB/s    00:01 ETA
Fetching packagesite.txz: 100%    6 MiB   3.1MB/s    00:02   
Processing entries:   0%
.
.
Processing entries: 100%
FreeBSD repository update completed. 28605 packages processed.
All repositories are up to date.

$ sudo pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Updating database digests format:   0%
Updating database digests format: 100%
Checking for upgrades (10 candidates):   0%
Checking for upgrades (10 candidates): 100%
Processing candidates (10 candidates):   0%
Processing candidates (10 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

  Installing the needed tools
$ sudo pkg install curl wget vim nano gnupg
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 21 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
curl: 7.58.0
wget: 1.19.2
vim: 8.0.1427
nano: 2.9.1
gnupg: 2.2.4
libnghttp2: 1.29.0
libedit: 3.1.20170329_2,1
libXpm: 3.5.12
ruby: 2.4.3,1
libyaml: 0.1.6_2
desktop-file-utils: 0.23
ctags: 5.8
cscope: 15.8b
pinentry: 1.0.0_3
pinentry-tty: 1.0.0
libgpg-error: 1.27
libassuan: 2.5.1
libksba: 1.3.5
libgcrypt: 1.8.2
npth: 1.5
sqlite3: 3.22.0_1

Number of packages to be installed: 21

The process will require 104 MiB more space.
22 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/21] Fetching curl-7.58.0.txz:   0%
[1/21] Fetching curl-7.58.0.txz:  31%  376 KiB 385.0kB/s    00:02 ETA
[1/21] Fetching curl-7.58.0.txz: 100%    1 MiB   1.2MB/s    00:01   
[2/21] Fetching wget-1.19.2.txz:   0%
[2/21] Fetching wget-1.19.2.txz:  25%  160 KiB 163.8kB/s    00:02 ETA
[2/21] Fetching wget-1.19.2.txz: 100%  624 KiB 639.1kB/s    00:01   
[3/21] Fetching vim-8.0.1427.txz:   0%
[3/21] Fetching vim-8.0.1427.txz:   1%  128 KiB 131.1kB/s    00:51 ETA
[3/21] Fetching vim-8.0.1427.txz:  18%    1 MiB   1.2MB/s    00:07 ETA
[3/21] Fetching vim-8.0.1427.txz:  71%    5 MiB   3.6MB/s    00:00 ETA
[3/21] Fetching vim-8.0.1427.txz: 100%    7 MiB   2.3MB/s    00:03   
[4/21] Fetching nano-2.9.1.txz:   0%
[4/21] Fetching nano-2.9.1.txz:  65%  312 KiB 319.5kB/s    00:00 ETA
[4/21] Fetching nano-2.9.1.txz: 100%  476 KiB 487.8kB/s    00:01   
[5/21] Fetching gnupg-2.2.4.txz:   0%
[5/21] Fetching gnupg-2.2.4.txz:  20%  408 KiB 417.8kB/s    00:03 ETA
[5/21] Fetching gnupg-2.2.4.txz: 100%    2 MiB   2.0MB/s    00:01   
[6/21] Fetching libnghttp2-1.29.0.txz:   0%
[6/21] Fetching libnghttp2-1.29.0.txz: 100%  108 KiB 110.4kB/s    00:01   
[7/21] Fetching libedit-3.1.20170329_2,1.txz:   0%
[7/21] Fetching libedit-3.1.20170329_2,1.txz: 100%  125 KiB 128.5kB/s    00:01   
[8/21] Fetching libXpm-3.5.12.txz:   0%
[8/21] Fetching libXpm-3.5.12.txz: 100%   71 KiB  72.2kB/s    00:01   
[9/21] Fetching ruby-2.4.3,1.txz:   0%
[9/21] Fetching ruby-2.4.3,1.txz:   6%  568 KiB 581.6kB/s    00:14 ETA
[9/21] Fetching ruby-2.4.3,1.txz:  35%    3 MiB   2.6MB/s    00:03 ETA
[9/21] Fetching ruby-2.4.3,1.txz:  98%    8 MiB   5.7MB/s    00:00 ETA
[9/21] Fetching ruby-2.4.3,1.txz: 100%    9 MiB   3.0MB/s    00:03   
[10/21] Fetching libyaml-0.1.6_2.txz:   0%
[10/21] Fetching libyaml-0.1.6_2.txz: 100%   64 KiB  65.3kB/s    00:01   
[11/21] Fetching desktop-file-utils-0.23.txz:   0%
[11/21] Fetching desktop-file-utils-0.23.txz: 100%   37 KiB  37.4kB/s    00:01   
[12/21] Fetching ctags-5.8.txz:   0%
[12/21] Fetching ctags-5.8.txz: 100%  121 KiB 124.0kB/s    00:01   
[13/21] Fetching cscope-15.8b.txz:   0%
[13/21] Fetching cscope-15.8b.txz: 100%  127 KiB 130.1kB/s    00:01   
[14/21] Fetching pinentry-1.0.0_3.txz:   0%
[14/21] Fetching pinentry-1.0.0_3.txz: 100%   16 KiB  16.6kB/s    00:01   
[15/21] Fetching pinentry-tty-1.0.0.txz:   0%
[15/21] Fetching pinentry-tty-1.0.0.txz: 100%   27 KiB  27.6kB/s    00:01   
[16/21] Fetching libgpg-error-1.27.txz:   0%
[16/21] Fetching libgpg-error-1.27.txz: 100%  183 KiB 187.2kB/s    00:01   
[17/21] Fetching libassuan-2.5.1.txz:   0%
[17/21] Fetching libassuan-2.5.1.txz: 100%   77 KiB  78.7kB/s    00:01   
[18/21] Fetching libksba-1.3.5.txz:   0%
[18/21] Fetching libksba-1.3.5.txz: 100%  158 KiB 161.3kB/s    00:01   
[19/21] Fetching libgcrypt-1.8.2.txz:   0%
[19/21] Fetching libgcrypt-1.8.2.txz:  26%  192 KiB 196.6kB/s    00:02 ETA
[19/21] Fetching libgcrypt-1.8.2.txz: 100%  716 KiB 733.5kB/s    00:01   
[20/21] Fetching npth-1.5.txz:   0%
[20/21] Fetching npth-1.5.txz: 100%   20 KiB  20.9kB/s    00:01   
[21/21] Fetching sqlite3-3.22.0_1.txz:   0%
[21/21] Fetching sqlite3-3.22.0_1.txz:   6%   72 KiB  73.7kB/s    00:15 ETA
[21/21] Fetching sqlite3-3.22.0_1.txz: 100%    1 MiB   1.2MB/s    00:01   
Checking integrity... done (0 conflicting)
[1/21] Installing libgpg-error-1.27...
[1/21] Extracting libgpg-error-1.27:   0%
[1/21] Extracting libgpg-error-1.27: 100%
[2/21] Installing libassuan-2.5.1...
[2/21] Extracting libassuan-2.5.1:   0%
[2/21] Extracting libassuan-2.5.1: 100%
[3/21] Installing libedit-3.1.20170329_2,1...
[3/21] Extracting libedit-3.1.20170329_2,1:   0%
[3/21] Extracting libedit-3.1.20170329_2,1: 100%
[4/21] Installing libyaml-0.1.6_2...
[4/21] Extracting libyaml-0.1.6_2:   0%
[4/21] Extracting libyaml-0.1.6_2: 100%
[5/21] Installing pinentry-tty-1.0.0...
[5/21] Extracting pinentry-tty-1.0.0:   0%
[5/21] Extracting pinentry-tty-1.0.0: 100%
[6/21] Installing libnghttp2-1.29.0...
[6/21] Extracting libnghttp2-1.29.0:   0%
[6/21] Extracting libnghttp2-1.29.0: 100%
[7/21] Installing libXpm-3.5.12...
[7/21] Extracting libXpm-3.5.12:   0%
[7/21] Extracting libXpm-3.5.12: 100%
[8/21] Installing ruby-2.4.3,1...
[8/21] Extracting ruby-2.4.3,1:   0%
[8/21] Extracting ruby-2.4.3,1: 100%
[9/21] Installing desktop-file-utils-0.23...
[9/21] Extracting desktop-file-utils-0.23:   0%
[9/21] Extracting desktop-file-utils-0.23: 100%
[10/21] Installing ctags-5.8...
[10/21] Extracting ctags-5.8:   0%
[10/21] Extracting ctags-5.8: 100%
[11/21] Installing cscope-15.8b...
[11/21] Extracting cscope-15.8b:   0%
[11/21] Extracting cscope-15.8b: 100%
[12/21] Installing pinentry-1.0.0_3...
[12/21] Extracting pinentry-1.0.0_3:   0%
[12/21] Extracting pinentry-1.0.0_3: 100%
[13/21] Installing libksba-1.3.5...
[13/21] Extracting libksba-1.3.5:   0%
[13/21] Extracting libksba-1.3.5: 100%
[14/21] Installing libgcrypt-1.8.2...
[14/21] Extracting libgcrypt-1.8.2:   0%
[14/21] Extracting libgcrypt-1.8.2: 100%
[15/21] Installing npth-1.5...
[15/21] Extracting npth-1.5:   0%
[15/21] Extracting npth-1.5: 100%
[16/21] Installing sqlite3-3.22.0_1...
[16/21] Extracting sqlite3-3.22.0_1:   0%
[16/21] Extracting sqlite3-3.22.0_1: 100%
[17/21] Installing curl-7.58.0...
[17/21] Extracting curl-7.58.0:   0%
[17/21] Extracting curl-7.58.0: 100%
[18/21] Installing wget-1.19.2...
[18/21] Extracting wget-1.19.2:   0%
[18/21] Extracting wget-1.19.2: 100%
[19/21] Installing vim-8.0.1427...
[19/21] Extracting vim-8.0.1427:   0%
[19/21] Extracting vim-8.0.1427: 100%
[20/21] Installing nano-2.9.1...
[20/21] Extracting nano-2.9.1:   0%
[20/21] Extracting nano-2.9.1: 100%
[21/21] Installing gnupg-2.2.4...
Extracting gnupg-2.2.4:   0%
Extracting gnupg-2.2.4: 100%
Message from ruby-2.4.3,1:

====
Some of the standard commands are provided as separate ports for ease
of upgrading:

devel/ruby-gems: gem - RubyGems package manager
devel/rubygem-rake: rake - Ruby Make

And some of the standard libraries are provided as separate ports
since they require extra dependencies:

databases/ruby-gdbm: GDBM module

Install them as occasion demands.
====
Message from ctags-5.8:

**************************************************************************
The executable for Exuberant CTAGS is installed as /usr/local/bin/exctags
**************************************************************************

  Installation of the tools is now compleeted, now we install the Webserver Apache v2.4
$ sudo pkg install apache24
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 3 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
apache24: 2.4.29
apr: 1.6.3.1.6.1
db5: 5.3.28_6

Number of packages to be installed: 3

The process will require 76 MiB more space.
17 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/3] Fetching apache24-2.4.29.txz:   0%
[1/3] Fetching apache24-2.4.29.txz:  15%  752 KiB 770.1kB/s    00:05 ETA
[1/3] Fetching apache24-2.4.29.txz:  79%    4 MiB   3.3MB/s    00:00 ETA
[1/3] Fetching apache24-2.4.29.txz:  99%    5 MiB   1.0MB/s    00:00 ETA
[1/3] Fetching apache24-2.4.29.txz: 100%    5 MiB   1.7MB/s    00:03   
[2/3] Fetching apr-1.6.3.1.6.1.txz:   0%
[2/3] Fetching apr-1.6.3.1.6.1.txz: 100%  453 KiB 464.2kB/s    00:01   
[3/3] Fetching db5-5.3.28_6.txz:   0%
[3/3] Fetching db5-5.3.28_6.txz:   5%  640 KiB 655.4kB/s    00:18 ETA
[3/3] Fetching db5-5.3.28_6.txz:  22%    3 MiB   2.2MB/s    00:06 ETA
[3/3] Fetching db5-5.3.28_6.txz:  48%    6 MiB   3.3MB/s    00:02 ETA
[3/3] Fetching db5-5.3.28_6.txz:  74%    9 MiB   3.4MB/s    00:01 ETA
[3/3] Fetching db5-5.3.28_6.txz: 100%   12 MiB   3.2MB/s    00:04   
Checking integrity... done (0 conflicting)
[1/3] Installing db5-5.3.28_6...
[1/3] Extracting db5-5.3.28_6:   0%
[1/3] Extracting db5-5.3.28_6: 100%
[2/3] Installing apr-1.6.3.1.6.1...
[2/3] Extracting apr-1.6.3.1.6.1:   0%
[2/3] Extracting apr-1.6.3.1.6.1: 100%
[3/3] Installing apache24-2.4.29...
===> Creating groups.
Using existing group 'www'.
===> Creating users
Using existing user 'www'.
Extracting apache24-2.4.29:   0%
Extracting apache24-2.4.29: 100%
Message from apr-1.6.3.1.6.1:

/!\ ================================================================== /!\

The Apache Portable Runtime project removed support for FreeTDS with
version 1.6. Users requiring MS-SQL connectivity must migrate
configurations to use the added ODBC driver and FreeTDS' ODBC features.

/!\ ================================================================== /!\
Message from apache24-2.4.29:

To run apache www server from startup, add apache24_enable="yes"
in your /etc/rc.conf. Extra options can be found in startup script.

Your hostname must be resolvable using at least 1 mechanism in
/etc/nsswitch.conf typically DNS or /etc/hosts or apache might
have issues starting depending on the modules you are using.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

- apache24 default build changed from static MPM to modular MPM
- more modules are now enabled per default in the port
- icons and error pages moved from WWWDIR to DATADIR

   If build with modular MPM and no MPM is activated in
   httpd.conf, then mpm_prefork will be activated as default
   MPM in etc/apache24/modules.d to keep compatibility with
   existing php/perl/python modules!

Please compare the existing httpd.conf with httpd.conf.sample
and merge missing modules/instructions into httpd.conf!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  Now we need to set Apache to start automatically on reboots
$ sudo sysrc apache24_enable=YES
apache24_enable:  -> YES

 Now we have to set the default production configuration for the Apache web server
$ sudo cp /usr/local/etc/apache24/httpd.conf.sample /usr/local/etc/apache24/httpd.conf

 Now we can start the web server
$ sudo service apache24 start
Performing sanity check on apache24 configuration:
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message
Syntax OK
Starting apache24.
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message

 This is a common error since we have not configured DNS or Domain of the FreeBSD Server as this is handled by an external system you do not need to do this for this guide and can be ignored for now

 Now we need to install PHP and PHP Extension modules
$ sudo pkg install php71 php71-extensions mod_php71 php71-mysqli php71-gd php71-curl php71-zlib php71-zip php71-pdo_mysql php71-openssl php71-gmp php71-ldap php71-exif php71-fileinfo php71-mbstring php71-bcmath php71-bz2 php71-mcrypt php71-intl
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 43 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
php71: 7.1.15
php71-extensions: 1.0
mod_php71: 7.1.15
php71-mysqli: 7.1.15
php71-gd: 7.1.15
php71-curl: 7.1.15
php71-zlib: 7.1.15
php71-zip: 7.1.15
php71-pdo_mysql: 7.1.15
php71-openssl: 7.1.15
php71-gmp: 7.1.15
php71-ldap: 7.1.15
php71-exif: 7.1.15
php71-fileinfo: 7.1.15
php71-mbstring: 7.1.15
php71-bcmath: 7.1.15
php71-bz2: 7.1.15
php71-mcrypt: 7.1.15
php71-intl: 7.1.15
php71-session: 7.1.15
php71-opcache: 7.1.15
php71-xmlwriter: 7.1.15
php71-xmlreader: 7.1.15
php71-dom: 7.1.15
php71-xml: 7.1.15
php71-simplexml: 7.1.15
php71-ctype: 7.1.15
php71-posix: 7.1.15
php71-hash: 7.1.15
php71-filter: 7.1.15
php71-tokenizer: 7.1.15
php71-json: 7.1.15
php71-sqlite3: 7.1.15
php71-pdo_sqlite: 7.1.15
php71-pdo: 7.1.15
php71-iconv: 7.1.15
php71-phar: 7.1.15
libzip: 1.3.2
openldap-client: 2.4.45
oniguruma6: 6.6.1
libmcrypt: 2.5.8_3
libltdl: 2.4.6
icu: 60.2_1,1

Number of packages to be installed: 43

The process will require 91 MiB more space.
17 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/43] Fetching php71-7.1.15.txz:   0%
[1/43] Fetching php71-7.1.15.txz:   1%   64 KiB  65.5kB/s    00:49 ETA
[1/43] Fetching php71-7.1.15.txz:  60%    2 MiB   1.9MB/s    00:01 ETA
[1/43] Fetching php71-7.1.15.txz: 100%    3 MiB   1.7MB/s    00:02   
[2/43] Fetching php71-extensions-1.0.txz:   0%
[2/43] Fetching php71-extensions-1.0.txz: 100%    1 KiB   1.1kB/s    00:01   
[3/43] Fetching mod_php71-7.1.15.txz:   0%
[3/43] Fetching mod_php71-7.1.15.txz:  13%  160 KiB 163.8kB/s    00:06 ETA
[3/43] Fetching mod_php71-7.1.15.txz: 100%    1 MiB   1.2MB/s    00:01   
[4/43] Fetching php71-mysqli-7.1.15.txz:   0%
[4/43] Fetching php71-mysqli-7.1.15.txz:  40%   16 KiB  16.4kB/s    00:01 ETA
[4/43] Fetching php71-mysqli-7.1.15.txz: 100%   39 KiB  40.2kB/s    00:01   
[5/43] Fetching php71-gd-7.1.15.txz:   0%
[5/43] Fetching php71-gd-7.1.15.txz: 100%  128 KiB 131.1kB/s    00:01   
[6/43] Fetching php71-curl-7.1.15.txz:   0%
[6/43] Fetching php71-curl-7.1.15.txz: 100%   27 KiB  27.8kB/s    00:01   
[7/43] Fetching php71-zlib-7.1.15.txz:   0%
[7/43] Fetching php71-zlib-7.1.15.txz: 100%   17 KiB  17.6kB/s    00:01   
[8/43] Fetching php71-zip-7.1.15.txz:   0%
[8/43] Fetching php71-zip-7.1.15.txz: 100%   20 KiB  20.4kB/s    00:01   
[9/43] Fetching php71-pdo_mysql-7.1.15.txz:   0%
[9/43] Fetching php71-pdo_mysql-7.1.15.txz: 100%   16 KiB  16.3kB/s    00:01   
[10/43] Fetching php71-openssl-7.1.15.txz:   0%
[10/43] Fetching php71-openssl-7.1.15.txz: 100%   53 KiB  54.0kB/s    00:01   
[11/43] Fetching php71-gmp-7.1.15.txz:   0%
[11/43] Fetching php71-gmp-7.1.15.txz: 100%   18 KiB  18.2kB/s    00:01   
[12/43] Fetching php71-ldap-7.1.15.txz:   0%
[12/43] Fetching php71-ldap-7.1.15.txz: 100%   20 KiB  20.7kB/s    00:01   
[13/43] Fetching php71-exif-7.1.15.txz:   0%
[13/43] Fetching php71-exif-7.1.15.txz: 100%   24 KiB  24.9kB/s    00:01   
[14/43] Fetching php71-fileinfo-7.1.15.txz:   0%
[14/43] Fetching php71-fileinfo-7.1.15.txz: 100%  203 KiB 208.1kB/s    00:01   
[15/43] Fetching php71-mbstring-7.1.15.txz:   0%
[15/43] Fetching php71-mbstring-7.1.15.txz:  10%   72 KiB  73.7kB/s    00:08 ETA
[15/43] Fetching php71-mbstring-7.1.15.txz: 100%  715 KiB 732.6kB/s    00:01   
[16/43] Fetching php71-bcmath-7.1.15.txz:   0%
[16/43] Fetching php71-bcmath-7.1.15.txz: 100%   20 KiB  20.3kB/s    00:01   
[17/43] Fetching php71-bz2-7.1.15.txz:   0%
[17/43] Fetching php71-bz2-7.1.15.txz: 100%   11 KiB  10.9kB/s    00:01   
[18/43] Fetching php71-mcrypt-7.1.15.txz:   0%
[18/43] Fetching php71-mcrypt-7.1.15.txz: 100%   15 KiB  14.9kB/s    00:01   
[19/43] Fetching php71-intl-7.1.15.txz:   0%
[19/43] Fetching php71-intl-7.1.15.txz: 100%  118 KiB 120.7kB/s    00:01   
[20/43] Fetching php71-session-7.1.15.txz:   0%
[20/43] Fetching php71-session-7.1.15.txz: 100%   32 KiB  32.8kB/s    00:01   
[21/43] Fetching php71-opcache-7.1.15.txz:   0%
[21/43] Fetching php71-opcache-7.1.15.txz: 100%  144 KiB 147.2kB/s    00:01   
[22/43] Fetching php71-xmlwriter-7.1.15.txz:   0%
[22/43] Fetching php71-xmlwriter-7.1.15.txz: 100%   13 KiB  13.1kB/s    00:01   
[23/43] Fetching php71-xmlreader-7.1.15.txz:   0%
[23/43] Fetching php71-xmlreader-7.1.15.txz: 100%   13 KiB  12.9kB/s    00:01   
[24/43] Fetching php71-dom-7.1.15.txz:   0%
[24/43] Fetching php71-dom-7.1.15.txz: 100%   54 KiB  55.0kB/s    00:01   
[25/43] Fetching php71-xml-7.1.15.txz:   0%
[25/43] Fetching php71-xml-7.1.15.txz:  81%   16 KiB  16.4kB/s    00:00 ETA
[25/43] Fetching php71-xml-7.1.15.txz: 100%   20 KiB  20.2kB/s    00:01   
[26/43] Fetching php71-simplexml-7.1.15.txz:   0%
[26/43] Fetching php71-simplexml-7.1.15.txz: 100%   22 KiB  23.0kB/s    00:01   
[27/43] Fetching php71-ctype-7.1.15.txz:   0%
[27/43] Fetching php71-ctype-7.1.15.txz: 100%    6 KiB   6.5kB/s    00:01   
[28/43] Fetching php71-posix-7.1.15.txz:   0%
[28/43] Fetching php71-posix-7.1.15.txz: 100%   11 KiB  11.4kB/s    00:01   
[29/43] Fetching php71-hash-7.1.15.txz:   0%
[29/43] Fetching php71-hash-7.1.15.txz: 100%  118 KiB 121.2kB/s    00:01   
[30/43] Fetching php71-filter-7.1.15.txz:   0%
[30/43] Fetching php71-filter-7.1.15.txz:  85%   16 KiB  16.4kB/s    00:00 ETA
[30/43] Fetching php71-filter-7.1.15.txz: 100%   19 KiB  19.2kB/s    00:01   
[31/43] Fetching php71-tokenizer-7.1.15.txz:   0%
[31/43] Fetching php71-tokenizer-7.1.15.txz: 100%    9 KiB   8.8kB/s    00:01   
[32/43] Fetching php71-json-7.1.15.txz:   0%
[32/43] Fetching php71-json-7.1.15.txz: 100%   19 KiB  19.8kB/s    00:01   
[33/43] Fetching php71-sqlite3-7.1.15.txz:   0%
[33/43] Fetching php71-sqlite3-7.1.15.txz: 100%   18 KiB  18.0kB/s    00:01   
[34/43] Fetching php71-pdo_sqlite-7.1.15.txz:   0%
[34/43] Fetching php71-pdo_sqlite-7.1.15.txz: 100%   12 KiB  12.1kB/s    00:01   
[35/43] Fetching php71-pdo-7.1.15.txz:   0%
[35/43] Fetching php71-pdo-7.1.15.txz: 100%   43 KiB  44.5kB/s    00:01   
[36/43] Fetching php71-iconv-7.1.15.txz:   0%
[36/43] Fetching php71-iconv-7.1.15.txz:  90%   16 KiB  16.4kB/s    00:00 ETA
[36/43] Fetching php71-iconv-7.1.15.txz: 100%   18 KiB  18.2kB/s    00:01   
[37/43] Fetching php71-phar-7.1.15.txz:   0%
[37/43] Fetching php71-phar-7.1.15.txz: 100%  102 KiB 104.6kB/s    00:01   
[38/43] Fetching libzip-1.3.2.txz:   0%
[38/43] Fetching libzip-1.3.2.txz:  82%  192 KiB 196.6kB/s    00:00 ETA
[38/43] Fetching libzip-1.3.2.txz: 100%  232 KiB 238.0kB/s    00:01   
[39/43] Fetching openldap-client-2.4.45.txz:   0%
[39/43] Fetching openldap-client-2.4.45.txz:  52%  536 KiB 548.9kB/s    00:00 ETA
[39/43] Fetching openldap-client-2.4.45.txz: 100%    1 MiB   1.1MB/s    00:01   
[40/43] Fetching oniguruma6-6.6.1.txz:   0%
[40/43] Fetching oniguruma6-6.6.1.txz:  97%  232 KiB 237.6kB/s    00:00 ETA
[40/43] Fetching oniguruma6-6.6.1.txz: 100%  237 KiB 242.8kB/s    00:01   
[41/43] Fetching libmcrypt-2.5.8_3.txz:   0%
[41/43] Fetching libmcrypt-2.5.8_3.txz: 100%  115 KiB 118.0kB/s    00:01   
[42/43] Fetching libltdl-2.4.6.txz:   0%
[42/43] Fetching libltdl-2.4.6.txz: 100%   36 KiB  37.0kB/s    00:01   
[43/43] Fetching icu-60.2_1,1.txz:   0%
[43/43] Fetching icu-60.2_1,1.txz:   1%   96 KiB  98.3kB/s    01:38 ETA
[43/43] Fetching icu-60.2_1,1.txz:  13%    1 MiB   1.2MB/s    00:11 ETA
[43/43] Fetching icu-60.2_1,1.txz:  42%    4 MiB   2.9MB/s    00:02 ETA
[43/43] Fetching icu-60.2_1,1.txz:  76%    7 MiB   3.4MB/s    00:01 ETA
[43/43] Fetching icu-60.2_1,1.txz: 100%    9 MiB   2.5MB/s    00:04   
Checking integrity... done (0 conflicting)
[1/43] Installing php71-7.1.15...
[1/43] Extracting php71-7.1.15:   0%
[1/43] Extracting php71-7.1.15: 100%
[2/43] Installing php71-dom-7.1.15...
[2/43] Extracting php71-dom-7.1.15:   0%
[2/43] Extracting php71-dom-7.1.15: 100%
[3/43] Installing php71-hash-7.1.15...
[3/43] Extracting php71-hash-7.1.15:   0%
[3/43] Extracting php71-hash-7.1.15: 100%
[4/43] Installing php71-pdo-7.1.15...
[4/43] Extracting php71-pdo-7.1.15:   0%
[4/43] Extracting php71-pdo-7.1.15: 100%
[5/43] Installing php71-session-7.1.15...
[5/43] Extracting php71-session-7.1.15:   0%
[5/43] Extracting php71-session-7.1.15: 100%
[6/43] Installing php71-opcache-7.1.15...
[6/43] Extracting php71-opcache-7.1.15:   0%
[6/43] Extracting php71-opcache-7.1.15: 100%
[7/43] Installing php71-xmlwriter-7.1.15...
[7/43] Extracting php71-xmlwriter-7.1.15:   0%
[7/43] Extracting php71-xmlwriter-7.1.15: 100%
[8/43] Installing php71-xmlreader-7.1.15...
[8/43] Extracting php71-xmlreader-7.1.15:   0%
[8/43] Extracting php71-xmlreader-7.1.15: 100%
[9/43] Installing php71-xml-7.1.15...
[9/43] Extracting php71-xml-7.1.15:   0%
[9/43] Extracting php71-xml-7.1.15: 100%
[10/43] Installing php71-simplexml-7.1.15...
[10/43] Extracting php71-simplexml-7.1.15:   0%
[10/43] Extracting php71-simplexml-7.1.15: 100%
[11/43] Installing php71-ctype-7.1.15...
[11/43] Extracting php71-ctype-7.1.15:   0%
[11/43] Extracting php71-ctype-7.1.15: 100%
[12/43] Installing php71-posix-7.1.15...
[12/43] Extracting php71-posix-7.1.15:   0%
[12/43] Extracting php71-posix-7.1.15: 100%
[13/43] Installing php71-filter-7.1.15...
[13/43] Extracting php71-filter-7.1.15:   0%
[13/43] Extracting php71-filter-7.1.15: 100%
[14/43] Installing php71-tokenizer-7.1.15...
[14/43] Extracting php71-tokenizer-7.1.15:   0%
[14/43] Extracting php71-tokenizer-7.1.15: 100%
[15/43] Installing php71-json-7.1.15...
[15/43] Extracting php71-json-7.1.15:   0%
[15/43] Extracting php71-json-7.1.15: 100%
[16/43] Installing php71-sqlite3-7.1.15...
[16/43] Extracting php71-sqlite3-7.1.15:   0%
[16/43] Extracting php71-sqlite3-7.1.15: 100%
[17/43] Installing php71-pdo_sqlite-7.1.15...
[17/43] Extracting php71-pdo_sqlite-7.1.15:   0%
[17/43] Extracting php71-pdo_sqlite-7.1.15: 100%
[18/43] Installing php71-iconv-7.1.15...
[18/43] Extracting php71-iconv-7.1.15:   0%
[18/43] Extracting php71-iconv-7.1.15: 100%
[19/43] Installing php71-phar-7.1.15...
[19/43] Extracting php71-phar-7.1.15:   0%
[19/43] Extracting php71-phar-7.1.15: 100%
[20/43] Installing libzip-1.3.2...
[20/43] Extracting libzip-1.3.2:   0%
[20/43] Extracting libzip-1.3.2: 100%
[21/43] Installing openldap-client-2.4.45...
[21/43] Extracting openldap-client-2.4.45:   0%
[21/43] Extracting openldap-client-2.4.45: 100%
[22/43] Installing oniguruma6-6.6.1...
[22/43] Extracting oniguruma6-6.6.1:   0%
[22/43] Extracting oniguruma6-6.6.1: 100%
[23/43] Installing libmcrypt-2.5.8_3...
[23/43] Extracting libmcrypt-2.5.8_3:   0%
[23/43] Extracting libmcrypt-2.5.8_3: 100%
[24/43] Installing libltdl-2.4.6...
[24/43] Extracting libltdl-2.4.6:   0%
[24/43] Extracting libltdl-2.4.6: 100%
[25/43] Installing icu-60.2_1,1...
[25/43] Extracting icu-60.2_1,1:   0%
[25/43] Extracting icu-60.2_1,1: 100%
[26/43] Installing php71-extensions-1.0...
[27/43] Installing mod_php71-7.1.15...
[27/43] Extracting mod_php71-7.1.15:   0%
[27/43] Extracting mod_php71-7.1.15: 100%
[activating module `php7' in /usr/local/etc/apache24/httpd.conf]
[28/43] Installing php71-mysqli-7.1.15...
[28/43] Extracting php71-mysqli-7.1.15:   0%
[28/43] Extracting php71-mysqli-7.1.15: 100%
[29/43] Installing php71-gd-7.1.15...
[29/43] Extracting php71-gd-7.1.15:   0%
[29/43] Extracting php71-gd-7.1.15: 100%
[30/43] Installing php71-curl-7.1.15...
[30/43] Extracting php71-curl-7.1.15:   0%
[30/43] Extracting php71-curl-7.1.15: 100%
[31/43] Installing php71-zlib-7.1.15...
[31/43] Extracting php71-zlib-7.1.15:   0%
[31/43] Extracting php71-zlib-7.1.15: 100%
[32/43] Installing php71-zip-7.1.15...
[32/43] Extracting php71-zip-7.1.15:   0%
[32/43] Extracting php71-zip-7.1.15: 100%
[33/43] Installing php71-pdo_mysql-7.1.15...
[33/43] Extracting php71-pdo_mysql-7.1.15:   0%
[33/43] Extracting php71-pdo_mysql-7.1.15: 100%
[34/43] Installing php71-openssl-7.1.15...
[34/43] Extracting php71-openssl-7.1.15:   0%
[34/43] Extracting php71-openssl-7.1.15: 100%
[35/43] Installing php71-gmp-7.1.15...
[35/43] Extracting php71-gmp-7.1.15:   0%
[35/43] Extracting php71-gmp-7.1.15: 100%
[36/43] Installing php71-ldap-7.1.15...
[36/43] Extracting php71-ldap-7.1.15:   0%
[36/43] Extracting php71-ldap-7.1.15: 100%
[37/43] Installing php71-exif-7.1.15...
[37/43] Extracting php71-exif-7.1.15:   0%
[37/43] Extracting php71-exif-7.1.15: 100%
[38/43] Installing php71-fileinfo-7.1.15...
[38/43] Extracting php71-fileinfo-7.1.15:   0%
[38/43] Extracting php71-fileinfo-7.1.15: 100%
[39/43] Installing php71-mbstring-7.1.15...
[39/43] Extracting php71-mbstring-7.1.15:   0%
[39/43] Extracting php71-mbstring-7.1.15: 100%
[40/43] Installing php71-bcmath-7.1.15...
[40/43] Extracting php71-bcmath-7.1.15:   0%
[40/43] Extracting php71-bcmath-7.1.15: 100%
[41/43] Installing php71-bz2-7.1.15...
[41/43] Extracting php71-bz2-7.1.15:   0%
[41/43] Extracting php71-bz2-7.1.15: 100%
[42/43] Installing php71-mcrypt-7.1.15...
[42/43] Extracting php71-mcrypt-7.1.15:   0%
[42/43] Extracting php71-mcrypt-7.1.15: 100%
[43/43] Installing php71-intl-7.1.15...
Extracting php71-intl-7.1.15:   0%
Extracting php71-intl-7.1.15: 100%
Message from openldap-client-2.4.45:

************************************************************

The OpenLDAP client package has been successfully installed.

Edit
  /usr/local/etc/openldap/ldap.conf
to change the system-wide client defaults.

Try `man ldap.conf' and visit the OpenLDAP FAQ-O-Matic at
  http://www.OpenLDAP.org/faq/index.cgi?file=3
for more information.

************************************************************
Message from libmcrypt-2.5.8_3:

===>   NOTICE:

The libmcrypt port currently does not have a maintainer. As a result, it is
more likely to have unresolved issues, not be up-to-date, or even be removed in
the future. To volunteer to maintain this port, please create an issue at:

https://bugs.freebsd.org/bugzilla

More information about port maintainership is available at:

https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html#maintain-port
Message from mod_php71-7.1.15:

***************************************************************

Make sure index.php is part of your DirectoryIndex.

You should add the following to your Apache configuration file:

<FilesMatch "\.php$">
    SetHandler application/x-httpd-php
</FilesMatch>
<FilesMatch "\.phps$">
    SetHandler application/x-httpd-php-source
</FilesMatch>

*********************************************************************

If you are building PHP-based ports in poudriere(8) with ZTS enabled,
add WITH_MPM=event to /etc/make.conf to prevent build failures.

*********************************************************************
 
 Now we need to configure the production configuration of PHP
$ sudo cp /usr/local/etc/php.ini-production  /usr/local/etc/php.ini
$ sudo nano /usr/local/etc/php-fpm.d/www.conf
; Start a new pool named 'www'.
; the variable $pool can be used in any directive and will be replaced by the
; pool name ('www' here)
[www]

; Per pool prefix
; It only applies on the following directives:
; - 'access.log'
; - 'slowlog'
; - 'listen' (unixsocket)
; - 'chroot'
; - 'chdir'
; - 'php_values'
; - 'php_admin_values'
; When not set, the global prefix (or /usr/local) applies instead.
; Note: This directive can also be relative to the global prefix.
; Default Value: none
;prefix = /path/to/pools/$pool

; Unix user/group of processes
; Note: The user is mandatory. If the group is not set, the default user's group
;       will be used.
user = www
group = www

; The address on which to accept FastCGI requests.
; Valid syntaxes are:
;   'ip.add.re.ss:port'    - to listen on a TCP socket to a specific IPv4 address on
;                            a specific port;
;   '[ip:6:addr:ess]:port' - to listen on a TCP socket to a specific IPv6 address on
;                            a specific port;
;   'port'                 - to listen on a TCP socket to all addresses
;                            (IPv6 and IPv4-mapped) on a specific port;
;   '/path/to/unix/socket' - to listen on a unix socket.
; Note: This value is mandatory.
; listen = 127.0.0.1:9000
listen = /var/run/php-fpm.sock
listen.owner = www
listen.group = www
listen.mode = 0660

; Set listen(2) backlog.
; Default Value: 511 (-1 on FreeBSD and OpenBSD)
;listen.backlog = 511

; Set permissions for unix socket, if one is used. In Linux, read/write
; permissions must be set in order to allow connections from a web server. Many
; BSD-derived systems allow connections regardless of permissions.
; Default Values: user and group are set as the running user
;                 mode is set to 0660
;listen.owner = www
;listen.group = www
;listen.mode = 0660
; When POSIX Access Control Lists are supported you can set them using
; these options, value is a comma separated list of user/group names.
; When set, listen.owner and listen.group are ignored
;listen.acl_users =
;listen.acl_groups =

; List of addresses (IPv4/IPv6) of FastCGI clients which are allowed to connect.
; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original
; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address
; must be separated by a comma. If this value is left blank, connections will be
; accepted from any ip address.
; Default Value: any
;listen.allowed_clients = 127.0.0.1

; Specify the nice(2) priority to apply to the pool processes (only if set)
; The value can vary from -19 (highest priority) to 20 (lower priority)
; Note: - It will only work if the FPM master process is launched as root
;       - The pool processes will inherit the master process priority
;         unless it specified otherwise
; Default Value: no set
; process.priority = -19

; Choose how the process manager will control the number of child processes.
; Possible Values:
;   static  - a fixed number (pm.max_children) of child processes;
;   dynamic - the number of child processes are set dynamically based on the
;             following directives. With this process management, there will be
;             always at least 1 children.
;             pm.max_children      - the maximum number of children that can
;                                    be alive at the same time.
;             pm.start_servers     - the number of children created on startup.
;             pm.min_spare_servers - the minimum number of children in 'idle'
;                                    state (waiting to process). If the number
;                                    of 'idle' processes is less than this
;                                    number then some children will be created.
;             pm.max_spare_servers - the maximum number of children in 'idle'
;                                    state (waiting to process). If the number
;                                    of 'idle' processes is greater than this
;                                    number then some children will be killed.
;  ondemand - no children are created at startup. Children will be forked when
;             new requests will connect. The following parameter are used:
;             pm.max_children           - the maximum number of children that
;                                         can be alive at the same time.
;             pm.process_idle_timeout   - The number of seconds after which
;                                         an idle process will be killed.
; Note: This value is mandatory.
pm = dynamic

; The number of child processes to be created when pm is set to 'static' and the
; maximum number of child processes when pm is set to 'dynamic' or 'ondemand'.
; This value sets the limit on the number of simultaneous requests that will be
; served. Equivalent to the ApacheMaxClients directive with mpm_prefork.
; Equivalent to the PHP_FCGI_CHILDREN environment variable in the original PHP
; CGI. The below defaults are based on a server without much resources. Don't
; forget to tweak pm.* to fit your needs.
; Note: Used when pm is set to 'static', 'dynamic' or 'ondemand'
; Note: This value is mandatory.
pm.max_children = 5

; The number of child processes created on startup.
; Note: Used only when pm is set to 'dynamic'
; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2
pm.start_servers = 2

; The desired minimum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.min_spare_servers = 1

; The desired maximum number of idle server processes.
; Note: Used only when pm is set to 'dynamic'
; Note: Mandatory when pm is set to 'dynamic'
pm.max_spare_servers = 3

; The number of seconds after which an idle process will be killed.
; Note: Used only when pm is set to 'ondemand'
; Default Value: 10s
;pm.process_idle_timeout = 10s;

; The number of requests each child process should execute before respawning.
; This can be useful to work around memory leaks in 3rd party libraries. For
; endless request processing specify '0'. Equivalent to PHP_FCGI_MAX_REQUESTS.
; Default Value: 0
;pm.max_requests = 500

; The URI to view the FPM status page. If this value is not set, no URI will be
; recognized as a status page. It shows the following informations:
;   pool                 - the name of the pool;
;   process manager      - static, dynamic or ondemand;
;   start time           - the date and time FPM has started;
;   start since          - number of seconds since FPM has started;
;   accepted conn        - the number of request accepted by the pool;
;   listen queue         - the number of request in the queue of pending
;                          connections (see backlog in listen(2));
;   max listen queue     - the maximum number of requests in the queue
;                          of pending connections since FPM has started;
;   listen queue len     - the size of the socket queue of pending connections;
;   idle processes       - the number of idle processes;
;   active processes     - the number of active processes;
;   total processes      - the number of idle + active processes;
;   max active processes - the maximum number of active processes since FPM
;                          has started;
;   max children reached - number of times, the process limit has been reached,
;                          when pm tries to start more children (works only for
;                          pm 'dynamic' and 'ondemand');
; Value are updated in real time.
; Example output:
;   pool:                 www
;   process manager:      static
;   start time:           01/Jul/2011:17:53:49 +0200
;   start since:          62636
;   accepted conn:        190460
;   listen queue:         0
;   max listen queue:     1
;   listen queue len:     42
;   idle processes:       4
;   active processes:     11
;   total processes:      15
;   max active processes: 12
;   max children reached: 0
;
; By default the status page output is formatted as text/plain. Passing either
; 'html', 'xml' or 'json' in the query string will return the corresponding
; output syntax. Example:
;   http://www.foo.bar/status
;   http://www.foo.bar/status?json
;   http://www.foo.bar/status?html
;   http://www.foo.bar/status?xml
;
; By default the status page only outputs short status. Passing 'full' in the
; query string will also return status for each pool process.
; Example:
;   http://www.foo.bar/status?full
;   http://www.foo.bar/status?json&full
;   http://www.foo.bar/status?html&full
;   http://www.foo.bar/status?xml&full
; The Full status returns for each process:
;   pid                  - the PID of the process;
;   state                - the state of the process (Idle, Running, ...);
;   start time           - the date and time the process has started;
;   start since          - the number of seconds since the process has started;
;   requests             - the number of requests the process has served;
;   request duration     - the duration in µs of the requests;
;   request method       - the request method (GET, POST, ...);
;   request URI          - the request URI with the query string;
;   content length       - the content length of the request (only with POST);
;   user                 - the user (PHP_AUTH_USER) (or '-' if not set);
;   script               - the main script called (or '-' if not set);
;   last request cpu     - the %cpu the last request consumed
;                          it's always 0 if the process is not in Idle state
;                          because CPU calculation is done when the request
;                          processing has terminated;
;   last request memory  - the max amount of memory the last request consumed
;                          it's always 0 if the process is not in Idle state
;                          because memory calculation is done when the request
;                          processing has terminated;
; If the process is in Idle state, then informations are related to the
; last request the process has served. Otherwise informations are related to
; the current request being served.
; Example output:
;   ************************
;   pid:                  31330
;   state:                Running
;   start time:           01/Jul/2011:17:53:49 +0200
;   start since:          63087
;   requests:             12808
;   request duration:     1250261
;   request method:       GET
;   request URI:          /test_mem.php?N=10000
;   content length:       0
;   user:                 -
;   script:               /home/fat/web/docs/php/test_mem.php
;   last request cpu:     0.00
;   last request memory:  0
;
; Note: There is a real-time FPM status monitoring sample web page available
;       It's available in: /usr/local/share/php/fpm/status.html
;
; Note: The value must start with a leading slash (/). The value can be
;       anything, but it may not be a good idea to use the .php extension or it
;       may conflict with a real PHP file.
; Default Value: not set
;pm.status_path = /status

; The ping URI to call the monitoring page of FPM. If this value is not set, no
; URI will be recognized as a ping page. This could be used to test from outside
; that FPM is alive and responding, or to
; - create a graph of FPM availability (rrd or such);
; - remove a server from a group if it is not responding (load balancing);
; - trigger alerts for the operating team (24/7).
; Note: The value must start with a leading slash (/). The value can be
;       anything, but it may not be a good idea to use the .php extension or it
;       may conflict with a real PHP file.
; Default Value: not set
;ping.path = /ping

; This directive may be used to customize the response of a ping request. The
; response is formatted as text/plain with a 200 response code.
; Default Value: pong
;ping.response = pong

; The access log file
; Default: not set
;access.log = log/$pool.access.log

; The access log format.
; The following syntax is allowed
;  %%: the '%' character
;  %C: %CPU used by the request
;      it can accept the following format:
;      - %{user}C for user CPU only
;      - %{system}C for system CPU only
;      - %{total}C  for user + system CPU (default)
;  %d: time taken to serve the request
;      it can accept the following format:
;      - %{seconds}d (default)
;      - %{miliseconds}d
;      - %{mili}d
;      - %{microseconds}d
;      - %{micro}d
;  %e: an environment variable (same as $_ENV or $_SERVER)
;      it must be associated with embraces to specify the name of the env
;      variable. Some exemples:
;      - server specifics like: %{REQUEST_METHOD}e or %{SERVER_PROTOCOL}e
;      - HTTP headers like: %{HTTP_HOST}e or %{HTTP_USER_AGENT}e
;  %f: script filename
;  %l: content-length of the request (for POST request only)
;  %m: request method
;  %M: peak of memory allocated by PHP
;      it can accept the following format:
;      - %{bytes}M (default)
;      - %{kilobytes}M
;      - %{kilo}M
;      - %{megabytes}M
;      - %{mega}M
;  %n: pool name
;  %o: output header
;      it must be associated with embraces to specify the name of the header:
;      - %{Content-Type}o
;      - %{X-Powered-By}o
;      - %{Transfert-Encoding}o
;      - ....
;  %p: PID of the child that serviced the request
;  %P: PID of the parent of the child that serviced the request
;  %q: the query string
;  %Q: the '?' character if query string exists
;  %r: the request URI (without the query string, see %q and %Q)
;  %R: remote IP address
;  %s: status (response code)
;  %t: server time the request was received
;      it can accept a strftime(3) format:
;      %d/%b/%Y:%H:%M:%S %z (default)
;      The strftime(3) format must be encapsuled in a %{<strftime_format>}t tag
;      e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t
;  %T: time the log has been written (the request has finished)
;      it can accept a strftime(3) format:
;      %d/%b/%Y:%H:%M:%S %z (default)
;      The strftime(3) format must be encapsuled in a %{<strftime_format>}t tag
;      e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t
;  %u: remote user
;
; Default: "%R - %u %t \"%m %r\" %s"
;access.format = "%R - %u %t \"%m %r%Q%q\" %s %f %{mili}d %{kilo}M %C%%"

; The log file for slow requests
; Default Value: not set
; Note: slowlog is mandatory if request_slowlog_timeout is set
;slowlog = log/$pool.log.slow

; The timeout for serving a single request after which a PHP backtrace will be
; dumped to the 'slowlog' file. A value of '0s' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_slowlog_timeout = 0

; The timeout for serving a single request after which the worker process will
; be killed. This option should be used when the 'max_execution_time' ini option
; does not stop script execution for some reason. A value of '0' means 'off'.
; Available units: s(econds)(default), m(inutes), h(ours), or d(ays)
; Default Value: 0
;request_terminate_timeout = 0

; Set open file descriptor rlimit.
; Default Value: system defined value
;rlimit_files = 1024

; Set max core size rlimit.
; Possible Values: 'unlimited' or an integer greater or equal to 0
; Default Value: system defined value
;rlimit_core = 0

; Chroot to this directory at the start. This value must be defined as an
; absolute path. When this value is not set, chroot is not used.
; Note: you can prefix with '$prefix' to chroot to the pool prefix or one
; of its subdirectories. If the pool prefix is not set, the global prefix
; will be used instead.
; Note: chrooting is a great security feature and should be used whenever
;       possible. However, all PHP paths will be relative to the chroot
;       (error_log, sessions.save_path, ...).
; Default Value: not set
;chroot =

; Chdir to this directory at the start.
; Note: relative path can be used.
; Default Value: current directory or / when chroot
;chdir = /var/www

; Redirect worker stdout and stderr into main error log. If not set, stdout and
; stderr will be redirected to /dev/null according to FastCGI specs.
; Note: on highloaded environement, this can cause some delay in the page
; process time (several ms).
; Default Value: no
;catch_workers_output = yes

; Clear environment in FPM workers
; Prevents arbitrary environment variables from reaching FPM worker processes
; by clearing the environment in workers before env vars specified in this
; pool configuration are added.
; Setting to "no" will make all environment variables available to PHP code
; via getenv(), $_ENV and $_SERVER.
; Default Value: yes
;clear_env = no

; Limits the extensions of the main script FPM will allow to parse. This can
; prevent configuration mistakes on the web server side. You should only limit
; FPM to .php extensions to prevent malicious users to use other extensions to
; execute php code.
; Note: set an empty value to allow all extensions.
; Default Value: .php
;security.limit_extensions = .php .php3 .php4 .php5 .php7

; Pass environment variables like LD_LIBRARY_PATH. All $VARIABLEs are taken from
; the current environment.
; Default Value: clean env
;env[HOSTNAME] = $HOSTNAME
;env[PATH] = /usr/local/bin:/usr/bin:/bin
;env[TMP] = /tmp
;env[TMPDIR] = /tmp
;env[TEMP] = /tmp

; Additional php.ini defines, specific to this pool of workers. These settings
; overwrite the values previously defined in the php.ini. The directives are the
; same as the PHP SAPI:
;   php_value/php_flag             - you can set classic ini defines which can
;                                    be overwritten from PHP call 'ini_set'.
;   php_admin_value/php_admin_flag - these directives won't be overwritten by
;                                     PHP call 'ini_set'
; For php_*flag, valid values are on, off, 1, 0, true, false, yes or no.

; Defining 'extension' will load the corresponding shared extension from
; extension_dir. Defining 'disable_functions' or 'disable_classes' will not
; overwrite previously defined php.ini values, but will append the new value
; instead.

; Note: path INI options can be relative and will be expanded with the prefix
; (pool, global or /usr/local)

; Default Value: nothing is defined by default except the values in php.ini and
;                specified at startup with the -d argument
;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f www@my.domain.com
;php_flag[display_errors] = off
;php_admin_value[error_log] = /var/log/fpm-php.www.log
;php_admin_flag[log_errors] = on
;php_admin_value[memory_limit] = 32M


 Set PHP to run at bootup
$ sudo sysrc php_fpm_enable=YES
php_fpm_enable:  -> YES

 Start PHP
$ sudo service php-fpm start
Performing sanity check on php-fpm configuration:
[28-Mar-2018 12:37:47] NOTICE: configuration file /usr/local/etc/php-fpm.conf test is successful

Starting php_fpm.

 Set the PHP Configuration for Apache webserver
$ sudo nano /usr/local/etc/apache24/Includes/php.conf
<IfModule dir_module>
    DirectoryIndex index.php index.html
    <FilesMatch "\.php$">
        SetHandler application/x-httpd-php
    </FilesMatch>
    <FilesMatch "\.phps$">
        SetHandler application/x-httpd-php-source
    </FilesMatch>
</IfModule>


 Now we need to enable the PHP modules in Apache webserver
$ sudo nano /usr/local/etc/apache24/httpd.conf
#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned. 
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
# will be interpreted as '/logs/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/usr/local"

#
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
#
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
#
# Mutex default:/var/run

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
#LoadModule mpm_event_module libexec/apache24/mod_mpm_event.so
LoadModule mpm_prefork_module libexec/apache24/mod_mpm_prefork.so
#LoadModule mpm_worker_module libexec/apache24/mod_mpm_worker.so
LoadModule authn_file_module libexec/apache24/mod_authn_file.so
#LoadModule authn_dbm_module libexec/apache24/mod_authn_dbm.so
#LoadModule authn_anon_module libexec/apache24/mod_authn_anon.so
#LoadModule authn_dbd_module libexec/apache24/mod_authn_dbd.so
#LoadModule authn_socache_module libexec/apache24/mod_authn_socache.so
LoadModule authn_core_module libexec/apache24/mod_authn_core.so
LoadModule authz_host_module libexec/apache24/mod_authz_host.so
LoadModule authz_groupfile_module libexec/apache24/mod_authz_groupfile.so
LoadModule authz_user_module libexec/apache24/mod_authz_user.so
#LoadModule authz_dbm_module libexec/apache24/mod_authz_dbm.so
#LoadModule authz_owner_module libexec/apache24/mod_authz_owner.so
#LoadModule authz_dbd_module libexec/apache24/mod_authz_dbd.so
LoadModule authz_core_module libexec/apache24/mod_authz_core.so
#LoadModule authnz_fcgi_module libexec/apache24/mod_authnz_fcgi.so
LoadModule access_compat_module libexec/apache24/mod_access_compat.so
LoadModule auth_basic_module libexec/apache24/mod_auth_basic.so
#LoadModule auth_form_module libexec/apache24/mod_auth_form.so
#LoadModule auth_digest_module libexec/apache24/mod_auth_digest.so
#LoadModule allowmethods_module libexec/apache24/mod_allowmethods.so
#LoadModule file_cache_module libexec/apache24/mod_file_cache.so
#LoadModule cache_module libexec/apache24/mod_cache.so
#LoadModule cache_disk_module libexec/apache24/mod_cache_disk.so
#LoadModule cache_socache_module libexec/apache24/mod_cache_socache.so
#LoadModule socache_shmcb_module libexec/apache24/mod_socache_shmcb.so
#LoadModule socache_dbm_module libexec/apache24/mod_socache_dbm.so
#LoadModule socache_memcache_module libexec/apache24/mod_socache_memcache.so
#LoadModule watchdog_module libexec/apache24/mod_watchdog.so
#LoadModule macro_module libexec/apache24/mod_macro.so
#LoadModule dbd_module libexec/apache24/mod_dbd.so
#LoadModule dumpio_module libexec/apache24/mod_dumpio.so
#LoadModule buffer_module libexec/apache24/mod_buffer.so
#LoadModule data_module libexec/apache24/mod_data.so
#LoadModule ratelimit_module libexec/apache24/mod_ratelimit.so
LoadModule reqtimeout_module libexec/apache24/mod_reqtimeout.so
#LoadModule ext_filter_module libexec/apache24/mod_ext_filter.so
#LoadModule request_module libexec/apache24/mod_request.so
#LoadModule include_module libexec/apache24/mod_include.so
LoadModule filter_module libexec/apache24/mod_filter.so
#LoadModule reflector_module libexec/apache24/mod_reflector.so
#LoadModule substitute_module libexec/apache24/mod_substitute.so
#LoadModule sed_module libexec/apache24/mod_sed.so
#LoadModule charset_lite_module libexec/apache24/mod_charset_lite.so
#LoadModule deflate_module libexec/apache24/mod_deflate.so
#LoadModule xml2enc_module libexec/apache24/mod_xml2enc.so
#LoadModule proxy_html_module libexec/apache24/mod_proxy_html.so
LoadModule mime_module libexec/apache24/mod_mime.so
LoadModule log_config_module libexec/apache24/mod_log_config.so
#LoadModule log_debug_module libexec/apache24/mod_log_debug.so
#LoadModule log_forensic_module libexec/apache24/mod_log_forensic.so
#LoadModule logio_module libexec/apache24/mod_logio.so
LoadModule env_module libexec/apache24/mod_env.so
#LoadModule mime_magic_module libexec/apache24/mod_mime_magic.so
#LoadModule cern_meta_module libexec/apache24/mod_cern_meta.so
#LoadModule expires_module libexec/apache24/mod_expires.so
LoadModule headers_module libexec/apache24/mod_headers.so
#LoadModule usertrack_module libexec/apache24/mod_usertrack.so
#LoadModule unique_id_module libexec/apache24/mod_unique_id.so
LoadModule setenvif_module libexec/apache24/mod_setenvif.so
LoadModule version_module libexec/apache24/mod_version.so
#LoadModule remoteip_module libexec/apache24/mod_remoteip.so
#LoadModule proxy_module libexec/apache24/mod_proxy.so
#LoadModule proxy_connect_module libexec/apache24/mod_proxy_connect.so
#LoadModule proxy_ftp_module libexec/apache24/mod_proxy_ftp.so
#LoadModule proxy_http_module libexec/apache24/mod_proxy_http.so
#LoadModule proxy_fcgi_module libexec/apache24/mod_proxy_fcgi.so
#LoadModule proxy_scgi_module libexec/apache24/mod_proxy_scgi.so
#LoadModule proxy_fdpass_module libexec/apache24/mod_proxy_fdpass.so
#LoadModule proxy_wstunnel_module libexec/apache24/mod_proxy_wstunnel.so
#LoadModule proxy_ajp_module libexec/apache24/mod_proxy_ajp.so
#LoadModule proxy_balancer_module libexec/apache24/mod_proxy_balancer.so
#LoadModule proxy_express_module libexec/apache24/mod_proxy_express.so
#LoadModule proxy_hcheck_module libexec/apache24/mod_proxy_hcheck.so
#LoadModule session_module libexec/apache24/mod_session.so
#LoadModule session_cookie_module libexec/apache24/mod_session_cookie.so
#LoadModule session_crypto_module libexec/apache24/mod_session_crypto.so
#LoadModule session_dbd_module libexec/apache24/mod_session_dbd.so
#LoadModule slotmem_shm_module libexec/apache24/mod_slotmem_shm.so
#LoadModule slotmem_plain_module libexec/apache24/mod_slotmem_plain.so
LoadModule ssl_module libexec/apache24/mod_ssl.so
#LoadModule dialup_module libexec/apache24/mod_dialup.so
#LoadModule http2_module libexec/apache24/mod_http2.so
#LoadModule proxy_http2_module libexec/apache24/mod_proxy_http2.so
#LoadModule lbmethod_byrequests_module libexec/apache24/mod_lbmethod_byrequests.so
#LoadModule lbmethod_bytraffic_module libexec/apache24/mod_lbmethod_bytraffic.so
#LoadModule lbmethod_bybusyness_module libexec/apache24/mod_lbmethod_bybusyness.so
#LoadModule lbmethod_heartbeat_module libexec/apache24/mod_lbmethod_heartbeat.so
LoadModule unixd_module libexec/apache24/mod_unixd.so
#LoadModule heartbeat_module libexec/apache24/mod_heartbeat.so
#LoadModule heartmonitor_module libexec/apache24/mod_heartmonitor.so
#LoadModule dav_module libexec/apache24/mod_dav.so
LoadModule status_module libexec/apache24/mod_status.so
LoadModule autoindex_module libexec/apache24/mod_autoindex.so
#LoadModule asis_module libexec/apache24/mod_asis.so
#LoadModule info_module libexec/apache24/mod_info.so
<IfModule !mpm_prefork_module>
#LoadModule cgid_module libexec/apache24/mod_cgid.so
</IfModule>
<IfModule mpm_prefork_module>
#LoadModule cgi_module libexec/apache24/mod_cgi.so
</IfModule>
#LoadModule dav_fs_module libexec/apache24/mod_dav_fs.so
#LoadModule dav_lock_module libexec/apache24/mod_dav_lock.so
#LoadModule vhost_alias_module libexec/apache24/mod_vhost_alias.so
#LoadModule negotiation_module libexec/apache24/mod_negotiation.so
LoadModule dir_module libexec/apache24/mod_dir.so
#LoadModule imagemap_module libexec/apache24/mod_imagemap.so
#LoadModule actions_module libexec/apache24/mod_actions.so
#LoadModule speling_module libexec/apache24/mod_speling.so
#LoadModule userdir_module libexec/apache24/mod_userdir.so
LoadModule alias_module libexec/apache24/mod_alias.so
#LoadModule rewrite_module libexec/apache24/mod_rewrite.so
LoadModule php7_module        libexec/apache24/libphp7.so

<IfModule php7_module>
        AddType application/x-httpd-php .php
</IfModule>

# Third party modules
IncludeOptional etc/apache24/modules.d/[0-9][0-9][0-9]_*.conf
 
<IfModule unixd_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch. 
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User www
Group www

</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin you@example.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
    AllowOverride none
    Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/usr/local/www/apache24/data"
<Directory "/usr/local/www/apache24/data">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   AllowOverride FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.php index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
    Require all denied
</Files>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "/var/log/httpd-error.log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "/var/log/httpd-access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "/var/log/httpd-access.log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/usr/local/www/apache24/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock cgisock
</IfModule>

#
# "/usr/local/www/apache24/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/usr/local/www/apache24/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>

<IfModule headers_module>
    #
    # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied
    # backend servers which have lingering "httpoxy" defects.
    # 'Proxy' request header is undefined by the IETF, not listed by IANA
    #
    RequestHeader unset Proxy early
</IfModule>

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig etc/apache24/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile etc/apache24/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
#EnableSendfile on

# Supplemental configuration
#
# The configuration files in the etc/apache24/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include etc/apache24/extra/httpd-mpm.conf

# Multi-language error messages
#Include etc/apache24/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include etc/apache24/extra/httpd-autoindex.conf

# Language settings
#Include etc/apache24/extra/httpd-languages.conf

# User home directories
#Include etc/apache24/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include etc/apache24/extra/httpd-info.conf

# Virtual hosts
#Include etc/apache24/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include etc/apache24/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include etc/apache24/extra/httpd-dav.conf

# Various default settings
#Include etc/apache24/extra/httpd-default.conf

# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include etc/apache24/extra/proxy-html.conf
</IfModule>

# Secure (SSL/TLS) connections
#Include etc/apache24/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

Include etc/apache24/Includes/*.conf



 Now we need to create a PHP Info \ Diagnostics page to check if all is working correctly
$ sudo nano /usr/local/www/apache24/data/phpinfo.php
<?php phpinfo();  ?>


 Now we need to restart Apache Web server since we have done alot of configuration changes that needs to be reloaded
$ sudo service apache24 restart
Performing sanity check on apache24 configuration:
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message
Syntax OK
Stopping apache24.
Waiting for PIDS: 5585.
Performing sanity check on apache24 configuration:
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message
Syntax OK
Starting apache24.
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message
 
 Test web server, open a web browser and test both IP and DNS access: http://192.168.55.30/phpinfo.php and http://server.it-monkey.lan/phpinfo.php
 Now that you have checked that everything is working correctly whit Apache and PHP, it is time to install and configure the Database server mySQL v5.7

 $ sudo pkg install mysql57-server
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 6 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
mysql57-server: 5.7.21
cyrus-sasl: 2.1.26_12
protobuf: 3.5.1
libevent: 2.1.8_1
mysql57-client: 5.7.21
liblz4: 1.8.0,1

Number of packages to be installed: 6

The process will require 211 MiB more space.
19 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/6] Fetching mysql57-server-5.7.21.txz:   0%
[1/6] Fetching mysql57-server-5.7.21.txz:   7%    1 MiB   1.1MB/s    00:12 ETA
[1/6] Fetching mysql57-server-5.7.21.txz:  29%    4 MiB   3.1MB/s    00:04 ETA
[1/6] Fetching mysql57-server-5.7.21.txz:  53%    7 MiB   3.4MB/s    00:02 ETA
[1/6] Fetching mysql57-server-5.7.21.txz:  77%   11 MiB   3.5MB/s    00:01 ETA
[1/6] Fetching mysql57-server-5.7.21.txz: 100%   14 MiB   3.6MB/s    00:04   
[2/6] Fetching cyrus-sasl-2.1.26_12.txz:   0%
[2/6] Fetching cyrus-sasl-2.1.26_12.txz: 100%  474 KiB 485.2kB/s    00:01   
[3/6] Fetching protobuf-3.5.1.txz:   0%
[3/6] Fetching protobuf-3.5.1.txz:  31%  752 KiB 770.1kB/s    00:02 ETA
[3/6] Fetching protobuf-3.5.1.txz: 100%    2 MiB   2.5MB/s    00:01   
[4/6] Fetching libevent-2.1.8_1.txz:   0%
[4/6] Fetching libevent-2.1.8_1.txz:  10%   32 KiB  32.8kB/s    00:08 ETA
[4/6] Fetching libevent-2.1.8_1.txz: 100%  305 KiB 311.9kB/s    00:01   
[5/6] Fetching mysql57-client-5.7.21.txz:   0%
[5/6] Fetching mysql57-client-5.7.21.txz:  10%  192 KiB 196.6kB/s    00:08 ETA
[5/6] Fetching mysql57-client-5.7.21.txz:  96%    2 MiB   1.7MB/s    00:00 ETA
[5/6] Fetching mysql57-client-5.7.21.txz: 100%    2 MiB 963.5kB/s    00:02   
[6/6] Fetching liblz4-1.8.0,1.txz:   0%
[6/6] Fetching liblz4-1.8.0,1.txz: 100%   98 KiB 100.8kB/s    00:01   
Checking integrity... done (0 conflicting)
[1/6] Installing cyrus-sasl-2.1.26_12...
*** Added group `cyrus' (id 60)
*** Added user `cyrus' (id 60)
[1/6] Extracting cyrus-sasl-2.1.26_12:   0%
[1/6] Extracting cyrus-sasl-2.1.26_12: 100%
[2/6] Installing protobuf-3.5.1...
[2/6] Extracting protobuf-3.5.1:   0%
[2/6] Extracting protobuf-3.5.1: 100%
[3/6] Installing libevent-2.1.8_1...
[3/6] Extracting libevent-2.1.8_1:   0%
[3/6] Extracting libevent-2.1.8_1: 100%
[4/6] Installing liblz4-1.8.0,1...
[4/6] Extracting liblz4-1.8.0,1:   0%
[4/6] Extracting liblz4-1.8.0,1: 100%
[5/6] Installing mysql57-client-5.7.21...
[5/6] Extracting mysql57-client-5.7.21:   0%
[5/6] Extracting mysql57-client-5.7.21: 100%
[6/6] Installing mysql57-server-5.7.21...
===> Creating groups.
Creating group 'mysql' with gid '88'.
===> Creating users
Creating user 'mysql' with uid '88'.
Extracting mysql57-server-5.7.21:   0%
Extracting mysql57-server-5.7.21: 100%
Message from cyrus-sasl-2.1.26_12:

You can use sasldb2 for authentication, to add users use:

saslpasswd2 -c username

If you want to enable SMTP AUTH with the system Sendmail, read
Sendmail.README

NOTE: This port has been compiled with a default pwcheck_method of
      auxprop.  If you want to authenticate your user by /etc/passwd,
      PAM or LDAP, install ports/security/cyrus-sasl2-saslauthd and
      set sasl_pwcheck_method to saslauthd after installing the
      Cyrus-IMAPd 2.X port.  You should also check the
      /usr/local/lib/sasl2/*.conf files for the correct
      pwcheck_method.
      If you want to use GSSAPI mechanism, install
      ports/security/cyrus-sasl2-gssapi.
      If you want to use SRP mechanism, install
      ports/security/cyrus-sasl2-srp.
      If you want to use LDAP auxprop plugin, install
      ports/security/cyrus-sasl2-ldapdb.
Message from mysql57-client-5.7.21:

* * * * * * * * * * * * * * * * * * * * * * * *

This is the mysql CLIENT without the server.
for complete server and client, please install databases/mysql57-server

* * * * * * * * * * * * * * * * * * * * * * * *
Message from mysql57-server-5.7.21:

*****************************************************************************

Remember to run mysql_upgrade the first time you start the MySQL server
after an upgrade from an earlier version.

Initial password for first time use of MySQL is saved in $HOME/.mysql_secret
ie. when you want to use "mysql -u root -p" first you should see password
in /root/.mysql_secret

MySQL57 has a default %%ETCDIR%%/my.cnf,
remember to replace it wit your own
or set `mysql_optfile="$YOUR_CNF_FILE` in rc.conf.

*****************************************************************************
 Set mySQL to automaticly start at Bootup

 $ sudo sysrc mysql_enable=YES
mysql_enable:  -> YES

Start mySQL Server

 $ sudo service mysql-server start
Starting mysql.

 Secure the Database SQL Server
$ sudo mysql_secure_installation
mysql_secure_installation: [ERROR] unknown variable 'prompt=\u@\h [\d]>\_'

Securing the MySQL server deployment.

Connecting to MySQL server using password in '/root/.mysql_secret'

VALIDATE PASSWORD PLUGIN can be used to test passwords
and improve security. It checks the strength of password
and allows the users to set only those passwords which are
secure enough. Would you like to setup VALIDATE PASSWORD plugin?

Press y|Y for Yes, any other key for No: y

There are three levels of password validation policy:

LOW    Length >= 8
MEDIUM Length >= 8, numeric, mixed case, and special characters
STRONG Length >= 8, numeric, mixed case, special characters and dictionary file

Please enter 0 = LOW, 1 = MEDIUM and 2 = STRONG: 1
Using existing password for root.

Estimated strength of the password: 100
Change the password for root ? ((Press y|Y for Yes, any other key for No) : y

New password: MySexyPassword123.

Re-enter new password: MySexyPassword123.

Estimated strength of the password: 100
Do you wish to continue with the password provided?(Press y|Y for Yes, any other key for No) : y
By default, a MySQL installation has an anonymous user,
allowing anyone to log into MySQL without having to have
a user account created for them. This is intended only for
testing, and to make the installation go a bit smoother.
You should remove them before moving into a production
environment.

Remove anonymous users? (Press y|Y for Yes, any other key for No) : y
Success.


Normally, root should only be allowed to connect from
'localhost'. This ensures that someone cannot guess at
the root password from the network.

Disallow root login remotely? (Press y|Y for Yes, any other key for No) : y
Success.

By default, MySQL comes with a database named 'test' that
anyone can access. This is also intended only for testing,
and should be removed before moving into a production
environment.


Remove test database and access to it? (Press y|Y for Yes, any other key for No) : y
 - Dropping test database...
Success.

 - Removing privileges on test database...
Success.

Reloading the privilege tables will ensure that all changes
made so far will take effect immediately.

Reload privilege tables now? (Press y|Y for Yes, any other key for No) : y
Success.

All done!

Open mySQL Server to create the needed Databases and access that is required by OwnCloud

 $ sudo mysql -u root -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5
Server version: 5.7.21-log

Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

root@localhost [(none)]> ALTER USER 'root'@'localhost' IDENTIFIED BY 'MySexyPassword123.';
Query OK, 0 rows affected (0.01 sec)

root@localhost [(none)]> CREATE DATABASE ownclouddb;
Query OK, 1 row affected (0.01 sec)

root@localhost [(none)]> CREATE USER ocadmin@localhost IDENTIFIED BY 'MySexyPassword123.';
Query OK, 0 rows affected (0.00 sec)

root@localhost [(none)]> GRANT ALL PRIVILEGES ON ownclouddb.* TO 'ocadmin'@'localhost';
Query OK, 0 rows affected (0.00 sec)

root@localhost [(none)]> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.01 sec)

root@localhost [(none)]> EXIT;
Bye

 Now we have done the minimum FAMP configuration for OwnCloud to run on FreeBSD,now we are just missing a few enviornment configuratuions before installing the OwnCloud package. We start by creating the SSL Certs so we can use HTTPS connection for accessing the server
$ sudo mkdir -p /usr/local/etc/ssl/self-cert/owncloud/
$ cd /usr/local/etc/ssl/self-cert/owncloud/
$ sudo openssl req -config /etc/ssl/openssl.cnf -new -out /usr/local/etc/ssl/self-cert/owncloud/owncloud.csr -keyout /usr/local/etc/ssl/self-cert/owncloud/owncloud.pem
Generating a 2048 bit RSA private key
.+++
...+++
writing new private key to '/usr/local/etc/ssl/self-cert/owncloud/owncloud.pem'
Enter PEM pass phrase: MySexyPassword123.
Verifying - Enter PEM pass phrase: MySexyPassword123.
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:NO
State or Province Name (full name) [Some-State]:Buskerud
Locality Name (eg, city) []:Drammen
Organization Name (eg, company) [Internet Widgits Pty Ltd]:IT-Monkey
Organizational Unit Name (eg, section) []:IT
Common Name (e.g. server FQDN or YOUR name) []:server.it-monkey.lan
Email Address []:admin@it-monkey.lan

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:MySexyPassword123.
An optional company name []:IT-Monkey

$ sudo openssl rsa -in /usr/local/etc/ssl/self-cert/owncloud/owncloud.pem -out /usr/local/etc/ssl/self-cert/owncloud/owncloud.key
Enter pass phrase for /usr/local/etc/ssl/self-cert/owncloud/owncloud.pem:
writing RSA key

$ sudo openssl x509 -in /usr/local/etc/ssl/self-cert/owncloud/owncloud.csr -out /usr/local/etc/ssl/self-cert/owncloud/owncloud.crt -req -signkey /usr/local/etc/ssl/self-cert/owncloud/owncloud.key -days 1095
Signature ok
subject=/C=NO/ST=Buskerud/L=Drammen/O=IT-Monkey/OU=IT/CN=server.it-monkey.lan/emailAddress=admin@it-monkey.lan
Getting Private key

$ sudo chmod 600 *
$ cd /tmp
 
 Now we need to download the OwnCloud software to our server, the current way to do that is to use wget or curl and point it at the url holding the tar install file of OwnCloud, these urls changes often so check OwnClouds website for the current version

$ wget https://download.owncloud.org/community/owncloud-10.0.7.tar.bz2
$ wget https://download.owncloud.org/community/owncloud-10.0.7.tar.bz2.sha256
$ wget https://download.owncloud.org/community/owncloud-10.0.7.tar.bz2.asc
$ wget https://owncloud.org/owncloud.asc

$ sudo gpg --import owncloud.asc
$ sudo sha256 -c owncloud-10.0.7.tar.bz2.sha256 -s owncloud-10.0.7.tar.bz2
$ sudo gpg --verify owncloud-10.0.7.tar.bz2.sha256 owncloud-10.0.7.tar.bz2

 Now we need to unpack and extract the files from the downloaded tar package and move it to a location the web server can read the files
$ sudo tar -xjf owncloud-10.0.7.tar.bz2
$ sudo cp -r owncloud/* /usr/local/www/apache24/data/owncloud/
cp: /usr/local/www/apache24/data/owncloud is not a directory
$ sudo mkdir -p /usr/local/www/apache24/data/owncloud/
$ sudo chown -R www:www /usr/local/www/apache24/data/owncloud/

 Restart Apache web server
$ sudo service apache24 restart
Performing sanity check on apache24 configuration:
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message
Syntax OK
Stopping apache24.
Waiting for PIDS: 5585.
Performing sanity check on apache24 configuration:
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message
Syntax OK
Starting apache24.
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.55.30. Set the 'ServerName' directive globally to suppress this message

 Now everything should be installed and working and when you open your web browser and navigate to http://192.168.55.30/owncloud/ or http://server.it-monkey.lan/owncloud/ you should see the OwnCloud setup page

7
Hardware / IT-Monkey Lab Hardware - end of 2017
« on: November 25, 2017, 11:54:37 AM »
I decided to create this topic about what hardware we use in our test lab her at IT-Monkey, after quite a few comments from people we have been in contact whit that they have no access to brand new hardware and that hardware is so expensive that they can not afford systems and lab equipment like what we have here. This is why I decided to share this list of what our lab hardware is and what our servers are made out of, and to showcase that you do not need the lates and greatest in a home-lab or test-lab at least not when you are starting out and want to learn as it was the goal for my home-lab when I first started out in 2010.


Physical Servers:
At this point in time we at IT-Monkey have 3 different DIY server in our lab-rack, these are:

1. Storage server, running FreeNAS 9.10.2-U6 This system was purpose build as a central storage server for my home office, home-lab and business, it is the only system that I have bought everything brand new from the retailer that sits in my server-rack.
2. Lab1-Server, hypervisor running VMWare ESXi 5.5
3. Lab2-Server, currently have no storage and OS, going to be used as a hypervisor standalone or cluster depending on software and pricing..
these are just generic names and not the actual names of the servers, for security reasons,

FreeNAS-Server Hardware:
Code: [Select]
Chenbro RM23212 2U rackmount whit rails, 12-hotswap hdd bays
Motherboard: Supermicro X11SSL-F (MicroATX, Socket 1151. C232 Chipset and DDR4)
Processor: Intel Xenon E3-1245v5 4 Cores at 3.5Ghz
Memory: Crucial DDR4 ECC unreg 64Gb 2133Mhz KIT
Powersupply: SeaSonic 400w 80-Plus Bronze
CPU Cooler: Noctua NH-L9x56
Raid Controller: LSI MegaRAID 9211-8 (Flashed to IT 20 Firmware)
NIC: Intel PRO 1000 PT (EXPI9404PT) 4-port
OS Drive: SanDisk Cruszer 32Gb
HDD 01: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 02: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 03: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 04: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 05: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 06: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 07: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 08: Seagate Ironwolf ST4000VN008 64MB 4TB
HDD 09: Western Digital Red WD40EFRX 64MB 4TB
HDD 10: Western Digital Red WD40EFRX 64MB 4TB
HDD 11: Western Digital Red WD40EFRX 64MB 4TB
HDD 12: Western Digital Red WD40EFRX 64MB 4TB
Fan 1: GELID Silent PRO 8 PWM
Fan 2: GELID Silent PRO 8 PWM
Fan 3: GELID Silent PRO 8 PWM

Note; This system was purpose build as a central storage server for my home office, home-lab and business, it is the only system that I have bought everything brand new from the retailer that sits in my server-rack.
Lab1-Server Hardware:
Code: [Select]
Case: X-Case X255F 2U rackmount whit rails
Motherboard: MSI Z77A-G45 LGA1155
Processor: Intel i7-3770 4-cors 3.40 GHz
Memory: Corsair Vengeance DDR3 1600mhz 32Gb KIT
Powersupply: Corsair CX500M, 500w 80-Plus Bronze
CPU Cooler: Noctua NH-L9x56
Raid Controller: LSI MegaRAID 9211-8 (Flashed to IT 20 Firmware)
NIC: Intel PRO 1000 PT (EXPI9404PT) 4-port
OS Drive: SanDisk Cruszer Fit 8Gb
Internal HDD 1: Intel 335 240Gb
Internal HDD 2: Intel 335 240Gb
Internal HDD 3: Western Digital Red WD30EFRX 64MB 3TB
Internal HDD 4: --
Fan 1: GELID Silent PRO 8 PWM
Fan 2: GELID Silent PRO 8 PWM
Fan 3: GELID Silent PRO 8 PWM

Note; Currently running VMWare ESXi 5.5 and a Windows 2012r2 DC network, thinking about changing hypervisor to something else
Lab2-Server Hardware:
Code: [Select]
Case: X-Case X255F 2U rackmount whit rails
Motherboard: Gigabyte GA-Z68XP-UD3 LGA1155
Processor: Intel i7-3770 4-cors 3.40 GHz
Memory 1: Corsair Vengeance DDR3 1600mhz 16Gb KIT
Memory 2: Corsair Vengeance DDR3 1600mhz 8Gb KIT
Powersupply: Andersson Mission SG GGP 550w 80-Plus
CPU Cooler: Noctua NH-L9x56
Raid Controller: LSI MegaRAID 9211-8 (Flashed to IT 20 Firmware)
NIC: Intel PRO 1000 PT (EXPI9404PT) 4-port
OS Drive: SanDisk Cruszer Fit 8Gb
Internal HDD 1: --
Internal HDD 2: --
Internal HDD 3: --
Internal HDD 4: --
Fan 1: GELID Silent PRO 8 PWM
Fan 2: GELID Silent PRO 8 PWM
Fan 3: GELID Silent PRO 8 PWM

Note; Server has no storage, server is currently being used as a bench testing server, has support for mSATA SSD, thinking about a hypervisor cluster, not sure what OS to use
As you can see both Lab1 and Lab2 server is built out of old consumer grade hardware and have prior to us getting them been used as gaming machines, where we simply refurbished the motherboard and CPU's moved it to a rack-mount case and added appropriate sized coolers and some other spare parts that we had laying around and most of those are not needed to run a basic test-lab.

Network:
As for our network we do not have very much hardware at all and you really do not need much besides a good Managed Switch whit enough ports to connect it together

For our lab we currently have the following networking equipment:
1. ISP Modem
2. SG-4860 pfSense Firewall
3. Cisco SB SG200-26p Switch

As you know there is no internet connectivity whiteout the ISP and their Modem, then there is the pfSense SG-4860 appliance we use this to separate home network, lab network and office network, then it is the Cisco Switch not much to it plug it in and connect devices to it.

As I am writing this post I am about to redo some of my lab setup so if there is intrest for it I can make a post about setting up your own home-lab from scratch whit more detailed information on how everything is interconnected whit each other

8
Off-Topic Therapy / Re: wallhack cs go pobierz
« on: June 29, 2017, 08:55:34 AM »
We are not against talking about games here, but please use english

9
Off-Topic Therapy / Re: minecraft do pobrania
« on: June 29, 2017, 07:17:47 AM »
It is okay to discuss minecraft, games are a part of IT, but please follow the one single rule of using English on this forum

10
Off-Topic Therapy / Re: Porn
« on: June 29, 2017, 07:13:13 AM »
If this was a porn site I would have done a better job keeping track as it would make me more money than this site does...

I do not want porn on this site, as this is for IT related stuff, unless the discussion is technical on how to setup a porn website or cdn I am not interested... please report all and any bad content you find and I will try cleaning up as much that I can

11
Networking / Re: Zabbix 3.2.6 installation and configuration on esx(i) 6.5
« on: June 10, 2017, 05:42:13 PM »
Looks good so far, but we should add a note that zabbix client or snmp needs to be installed \ configured on the server and devices before the discovery rules are enabled, otherwise it will only be detected by the Ping rule, and the monitoring will be does it respond to ping every x seconds (I added the Ping rule as a catch all other devices so that you know what devices that need some extra attention)

Also I would recommend to disable the Admin user and create your own user for login even tho you have changed the password and you trace the logs and it says admin did the change, not Mello or Noman in the logs, since this is a enterprise level software it should have a note about that.

We should also add in setting up the email and sms alerting before creating the discovery rules, whit is the point of having a monitoring system without getting alerted when it is triggered ?

This is just some of the thougts I have from laying sick in beed whit my laptop

12
Networking / Re: Zabbix 3.2.6 installation and configuration on esx(i) 6.5
« on: June 09, 2017, 01:45:59 PM »
Navigate to Configuration -> Action -> Event source: Discovery -> Create Action -> Operation, see the fb post for screenshot mr. Hill asked about the same yesterday

13
Networking / Re: Zabbix 3.2.6 installation and configuration on esx(i) 6.5
« on: June 09, 2017, 08:46:47 AM »
These are good instructions, but you are missing a whole lot of Zabbix configurations in between setting a new system password and accessing the webgui, I have alot of this wirtten up in a document here as generic notes, but ost of that information is also found in the documentation: https://www.zabbix.com/documentation/3.2/manual/appliance

This is what I have so far for zabbix installation, there are missing a few pices and nmap and sudo access but that is easy added on a later stage

Zabbix Installation
Download ISO file from: https://sourceforge.net/projects/zabbix/
Latest version in time of writing is: 3.2.6
Latest version is based on a customized Ubuntu 14.04 release
Install server whit mysql option (would love a nginx and mariadb version), follow the onscreen instructions
Systems default credentials are:
Core Server System:
User: appliance  \ Password: zabbix
Database:
User: root  \ Password: <random>
User: zabbix  \ Password: <random>
Database passwords are randomly generated during the installation process.
Root password is stored to /root/.my.cnf file, it is not required to input a password under the “root” account.
To change the database user password it has to be changed in the following locations:
MySQL;
/etc/zabbix/zabbix_server.conf;
/etc/zabbix/web/zabbix.conf.php.
Zabbix frontend WebGUI
User: Admin  \ Password: zabbix

Login to system shell and get root access and change the root password; User: appliance  \ Password: zabbix
sudo –I
this changes your user appliance into the root user
passwd
this lets you change the password of the current user, now you have gotten your root password set to something known, I recommend setting a strong password as root user have full access to your server and it should not be trivial to get a hold of
I like to work from a SSH connection so edit /etc/ssh_config and /etc/sshd_config to allow root to access the system from a SSH tunnel at least until you are done making changes to the core system
In /etc/ssh_config I have the default settings except
# PasswordAuthentication yes  is changed to PasswordAuthentication yes
added the line: PermitRootLogin yes
Save and exit
In /etc/sshd_config I have the default settings except
# Authentication:
LoginGraceTime 360
PermitRootLogin yes
StrictModes yes
Save and exit
Now restart SSH server whit command: service ssh restart
when this is done open your favorite terminal or console and connect to your server I like to use Putty  - http://www.putty.org/
Now if you are like me and are running Zabbix Server as a VM the next thing you would like to do is install the VM drivers and toolkits so that you get better performance of your monitoring VM
For VM’s running on a vmware platform the commands are as following:
apt-get update  or sudo apt-get update  if you are not at root level
apt-get install open-vm-tools  or sudo apt-get install open-vm-tools  if you are not at root level
reboot or sudo reboot if you are not at root level
For VM’s running on VirtualBox platform the commands are as following:
apt-get update  or sudo apt-get update  if you are not at root level
apt-get install build-essential module-assistant or sudo apt-get install build-essential module-assistant if you are not at root level
m-a prepare or sudo m-a prepare if you are not at root level

Now click "Devices > Insert guest additions CD image" in the virtualbox window. This will insert the guest additions cd image into the guest OS
The cd-image should be located on the path /media/root/VBOXADDITIONS_X.X  or /media/appliance/VBOXADDITIONS_X.X   depending on what user level you are at
Navigate to the directory and run the script named VBoxLinuxAdditions.run
cd /media/root/VBOXADDITIONS_X.X or cd /media/appliance/VBOXADDITIONS_X.X
./VBoxLinuxAdditions.run or sudo ./VBoxLinuxAdditions.run if you are not at root level
When it is done you should see the following line:
Building the VirtualBox Guest Additions kernel modules ...done.
reboot or sudo reboot if you are not at root level
After the server has rebooted we want to change some of the system settings to match our environment and location, this includes timesync, zoneinfo, dns
Check that you have the correct nameservers and dns server specified for your server so that zabbix is able to resolve IP’s into hostnames this is done by editing  /etc/resolv.conf

nameserver 10.99.99.1
nameserver 192.168.55.254
search vmlab.lan
search qnett.lan
This tells the Zabbix server that my dns server is at IP 10.99.99.1 and that my domain is vmlab.lan, if you have a router whit dhcp your server should have gotten this information automaticly, if you would like to add a custom server you just enter each value as its own line.
Now to change the zoneinfo and localization of the server this is done by editing the /etc/localtime file this is done by copying the right zone file over
The zone files are located under: /usr/share/zoneinfo/
/usr/share/zoneinfo /Africa
/usr/share/zoneinfo /America
/usr/share/zoneinfo /Asia
/usr/share/zoneinfo /Europe
In my case I would have to set it to /usr/share/zoneinfo /Europe/Oslo as I am in Norway
cp /usr/share/zoneinfo/Europe/Oslo  /etc/localtime
You would need to select the city closest to your location

Now we need to change the default Zabbix timezone as it it hardcoded to be Europe/Riga this is done by editing the file /etc/apache2/conf-available/zabbix.conf
As per default it will try to synchronize its clock whit the Ubuntu servers, but we would like to synchronize it whit our local time servers so all the systems in our data-center keep the same time, as this is very important for monitoring, logs and reporting purposes we need to install NTP services as this is not installed whit the zabbix installer iso
sudo apt-get update
sudo apt-get install ntp
If you have followed some of my other guides you might recall that I configured my pfSense firewall to act as a local time server for my local network, and I want the zabbix server to get its time synced from that pfSense firewall like any other device
To do this we need to edit the file /etc/ntp.conf
# Specify one or more NTP servers.
server 10.99.99.1 prefer iburst
server pfsense.vmlab.lan prefer iburst
server 0.no.pool.ntp.org
server 1.no.pool.ntp.org
server 2.no.pool.ntp.org
server 3.no.pool.ntp.org
As you can see I have set it to prefer my local pfSense firewall whit both IP and DNS and then added the Norwegian servers of the ntp.org project this is incase my ntp server running at the firewall could have issues one day and it would then fall back to use close external timeservers so it does not lose its time configuration
Now restart NTP whit command: sudo service ntp restart
Test that NTP is working correctly:  watch ntpq -cpe –cas
More information about ntp on Ubuntu servers are here: https://blogging.dragon.org.uk/setting-up-ntp-on-ubuntu-14-04/
When the server is rebooted navigate to its webgui and login whit Admin:zabbix
We want to configure 3 things on the server, which is Host Group, Discovery rules and Action rules
Host Group: This is just a sorting group and serves no other purpose than labeling and sorting different type of devices and servers so you can apply different monitoring rules and parameters to different Host Groups
Discovery Rules: These are the rules that you create that define how and where the Zabbix Server should look for network devices and servers, in short here is where you define the rules for SNMP, PING or Zabbix Client.
Action Rules: These are the rules that says what should happen whit newly discovered devices and servers, should they be added to a Host Group, and should they be assigned a monitoring pattern based of what type of device that were detected whether it is a router or switch using SNMP or a Windows Domain Controller responding to PING or Zabbix Client installed.
This is the very basic configuration needed to get the monitoring going on Zabbix
Navigate to Configuration -> Host Groups -> Create new Host Group
I create the following 3 Host Groups
myNetwork.Zabbx
myNetwork.SNMP
myNetwork.PING
Navigate to Configuration -> Discovery -> Create Discovery rule
I create the following 3 Discovery rules
Discovery.Zabbix
Discovery.SNMP
Discovery.PING
Discovery.Zabbix
Name: Discovery.Zabbix
Discovery by proxy: No Proxy
IP range: 10.99.99.0-254
Delay (in sec): 3600
Checks:  Zabbix agent – default values, key= system.uname
Device uniqueness criteria: IP address
Enabled: NO (unchecked)

Discovery.SNMP
Name: Discovery.SNMP
Discovery by proxy: No Proxy
IP range: 10.99.99.0-254
Delay (in sec): 3600
Checks:  SNMPv1 agent and SNMPv2 agent – default values
Device uniqueness criteria: IP address
Enabled: NO (unchecked)
Discovery.PING
Name: Discovery.PING
Discovery by proxy: No Proxy
IP range: 10.99.99.0-254
Delay (in sec): 3600
Checks:  ICMP Ping
Device uniqueness criteria: IP address
Enabled: NO (unchecked)
Navigate to Configuration -> Action -> Event source: Discovery -> Create Action
Here I create 3 new Action rules
Auto.Discovery.Zabbix
Auto.Discovery.SNMP
Auto.Discovery.PING
Auto.Discovery.Zabbix
Action:
Name: Auto.Discovery.Zabbix
Type of calculation: And/Or
Conditions:
A   Discovery check = Discovery.Zabbix: Zabbix agent "system.uname”
B   Host IP = 10.99.99.0-254
Enable: Yes (checked)
Operation:
1. Send message about new device
2. Operation details:
Add to host groups: myNetwork.Zabbx
Link to templates: Template App Zabbix Agent
Enable host
Set host inventory mode: Automatic
Auto.Discovery.SNMP
Action:
Name: Auto.Discovery.SNMP
Type of calculation: And/Or
Conditions:
A   Discovery check = Discovery.SNMP: SNMPv1 agent "zabbix"
B   Discovery check = Discovery.SNMP: SNMPv2 agent "zabbix"
C   Host IP = 10.99.99.0-254
Enable: Yes (checked)
Operation:
1. Send message about new device
2. Operation details:
Add to host groups: myNetwork.SNMP
Link to templates: Template SNMP Device, Template SNMP Disks, Template SNMP Generic, Template SNMP Interfaces and Template SNMP Processors
Enable host
Set host inventory mode: Automatic
Auto.Discovery.PING
Action:
Name: Auto.Discovery.PING
Type of calculation: And/Or
Conditions:
A   Discovery check = Discovery.PING: ICMP ping
B   Host IP = 10.99.99.0-254
Enable: Yes (checked)
Operation:
1. Send message about new device
2. Operation details:
Add to host groups: myNetwork.PING
Link to templates: Template ICMP Ping
Enable host
Set host inventory mode: Automatic
Navigate to Configuration -> Discovery
Now you can enable the following rules
Discovery.Zabbix
Discovery.SNMP
Discovery.PING

When these rules are enabled let it run for a couple of hours as scanning the network for all your devices will take some time depending on your network layout, how many devices that are on it and the hardware of your Zabbix Server


14
Networking / Zabbix Appliance 3.2.6 inconsistencies
« on: June 08, 2017, 10:09:30 AM »
Hello everyone, I just did a fresh lab deployment of the Zabbix Appliance 3.2.6 and I noticed some inconsistencies from my old lab deployment of Zabbix Appliance 3.0.4

Both ISO files where download from: https://sourceforge.net/projects/zabbix/

Hostname on 3.0.4 is set to: zabbix
Hostname on 3.2.6 is set to: ubuntu

This should be set to zabbix or zabbix-appliance on all versions or a even better option would be a prompt during install to set the hostname, also if you would use Static IP or DHCP configuration, this is a enterprise level server appliance to be deployed in lots of different network environments after all.

Another issue is whit the scrip: Detect operating system,
Command: sudo /usr/bin/nmap -O {HOST.CONN} 2>&1

Does not work as it is not added into sudoers list and nmap is not not installed so after editing it to allow to run the sudo command, it gives error command not find as nmap is not installed to begin whit, this should have been in there to begin whit or this option should have been removed from the front end

This issue is on both version, lucely these are minor issues that are easy to fix, just add the zabbix usergroup to sudo users whit visudo, and then install nmap on the device


Running Script on a detected host, no changes made


Editing sudo users to allow zabbix users to run sudo commands


Running OS Detection script against detected host after sudo rights


Running OS Detection script after nmap was installed

15
pfSense / Configure pfSense as HTTPS \ SSL Proxy filter using Squid and SquidGuard!
« on: June 05, 2017, 09:33:44 AM »
Configure pfSense as HTTPS \ SSL Proxy filter using Squid and SquidGuard!

This is a short write-up of how I got pfSense 2.3 and 2.4-Beta to act as an Proxy filter for ssl and https traffic without the needs of installing or configuring any client side settings or certificates, all configurations are done on the pfSense Firewall itself.
Tools needed:

Web-browser
Putty or similar console emulator
Notepad or Notepad++
WinSCP (Optional) gives you graphical text editor over ssh, good for beginners

All the steps below can be done directly on the firewall using only the GUI or SSH connections but for beginners it would be easier to use tools like Notepad++ and WinSCP to edit the configuration files needed for this to work

Step 1. Configuring the root Certificate Authority (rootCA)
This is probably the part that is most confusing for people and why their setups have failed, Squid need to have a CA assigned to it so that it is able to decrypt parts of the HTTPS header so that it can determine what to do whit that traffic, otherwise all traffic is passed.

I used the built-in openssl tool of pfSense to generate this rootCA, for this you need to ssh in to your firewall or connect to it over console, when at the console menu select option 8 Shell, when you are at the shell prompt you need to manually edit the openssl to give you the necessary prompts and questions for you to configure the rootCA

vi /etc/ssl/openssl.cnf

under the [ REQ ] option change the following line from: prompt=no to prompt=yes
under the [ V3_REQ ] option change the following line from: basicConstraints=CA:FALSE to basicConstraints=CA:TRUE
Then save and quit (to save and quit vi editor use :wq!).
Now we would make a known location in the filesystem to save our rootCA and key file as they need to be imported into pfSense GUI at a later stage, I like to use /tmp for any temporary files

Command:
mkdir /tmp/Proxyfiles

Now move to the folder you created whit:
cd /tmp/Proxyfiles

When you’re in this folder you are ready to start the openssl tool and start to create your rootCA, you start whit generating your KEY file by running the command:

openssl genrsa -out myProxykey.key 2048

This will create an rsa key file named myProxykey.key that we use to sign our rootCA whit in the next command for generating the pem file for the rootCA
Create a pem file signed whit key using command:

openssl req -x509 -new -nodes -key myProxykey.key -sha256 -days 365 -out myProxyca.pem

This will prompt you to answer some questions to generate the needed pem file in my case it is as below, you need to change this for where you are

US []:NO    - Country code
Somewhere []:Oslo  - State or province
Somecity []:Oslo   - Your city or town
CompanyName []:IT-Monkey   - Name of your company or business, "make something up if you’re a home user"
Organizational Unit Name (eg, section) []:IT-Department  - What part of the company issued the cert, can also be left blank
Common Name (eg, YOUR name) []:Admin    - Your name or identity in the company
Email Address []:admin@it-monkey.local  - Your contact email

At this point you should have 2 files in your /tmp/Proxyfiles directory

myProxyca.pem
myProxykey.key

This can be double checked whit command:

ls -la

If both are there then you are ready to download them and exit the shell environment and continue to the GUI of pfSense, if not you need to look over any error or try again.

To download these files I like to use WinSCP as its fast to navigate and find the files you want to move you can also do this from pfSense Diagnostic -> Command Prompt option and select the file path of:

/tmp/Proxyfiles/myProxyca.pem
/tmp/Proxyfiles/myProxykey.key



In the download box, this is somewhat slower to navigate but works just fine.

Now as you have these files on your desktop or computer you need to open them in a text editor, I prefer Notepad++ as it’s able to adjust the formatting layout of the text but any text editor will work as you will need to copy paste the information in these files to fields in the pfSense GUI.
Navigate to System -> Cert. Manager -> CA's
Here you want to add a new CA

Descriptive name: SquidCA
Method: Import an existing Certificate Authority
Certificate data: Copy \ Paste the info from myProxyca.pem file
Certificate Private Key: Copy \ Paste the info from myProxykey.key file
Save and apply




now you should see your SquidCA (rootCA) populated under System -> Cert. Manager -> CA's whit all the info you provided in the shell prompt and you are done whit Step 1.

You might want to undo the changes from the /etc/ssl/openssl.cnf file before proceeding

vi /etc/ssl/openssl.cnf

under the [ REQ ] option change the following line from: prompt=yes to prompt=no
under the [ V3_REQ ] option change the following line from: basicConstraints=CA:TRUE to basicConstraints=CA:FALSE

Then save and quit (to save and quit vi editor use :wq!).

Step 2. Installing required packages
this is probably the easiest step of the whole write up and you have probably already done it before looking up this post...
Navigate to System -> Package Manager -> Available Packages

Now look for Squid, SquidGuard and Lightsquid (if you want a log phraser)There is a small bug whit squid and SquidGuard installation that I have seen a few times and that is that you need to install the packages in a certain order for them to work properly

1. Squid
2. Lightsquid
3. SquidGuard



When installation is done you are done whit step 2.


Step 3. Configuration of Squid
Now we are going to setup the Squid service to handle the all the HTTP and HTTPS traffic for our clients, but before we can start the configurations Squid have an little bug where it will not save any of your settings before the Local Cache values are set so navigate to Services -> Squid Proxy Server -> Local Cache then set whatever options you like or scroll down to the bottom and hit save.

When the site refreshes from saving the Local Cache settings navigate to Services -> Squid Proxy Server -> General Settings
I have the following option set:

Squid General Settings
Enable Squid Proxy: Yes
Keep Settings/Data: Yes
Proxy Interface(s): LAN & Loopback
Proxy Port: 3128 (you can change this to a custom one if you like)
Allow Users on Interface: Yes



Transparent Proxy Settings
NO I do not use this leave option empty



SSL Man In the Middle Filtering
HTTPS/SSL Interception: Yes
SSL/MITM Mode: SPLICE ALL <- THIS IS AN IMPORTANT SETTING, IF SETT WRONG IT WILL NOT WORK.
SSL Proxy Port: 3129 (you can change this to a custom one if you like)
SSL Proxy Compatibility Mode: Modern
DHParams Key Size: 2048 Default
CA: SquidCA <- This is the rootCA you created in Step 1.
SSL Certificate Daemon Children: 5 Default
Remote Cert Checks: Do not verify remote certificates
Certificate Adapt: Sets the "Not Before" (setvalidbefore)



Logging Settings
Enable Access Logging: Yes
Log Store Directory: /var/squid/logs
Rotate Logs: 62 - keeps 2 months of logs in case of access reviews or issues, large SSD recommended
Log Pages Denied by SquidGuard: Yes
Save and apply



Step 4. Configuration of SquidGuard Proxy filter
This is where you define your ACL's and Blacklist, I do not use any pre-defined blacklist in this guide as I believe you get better control when you set it up manually from scratch, I am going to use Facebook and YouTube as primary targets to block as these are the most requested sites to be blocked by my clients, but this will work for any sites running on HTTP and HTTPS.

To start the configuration navigate to Services -> SquidGuard Proxy filter -> General Settings

General Options
Enable: Yes

LDAP Options
NO I do not use this leave option empty

Logging options
Enable GUI log: Yes
Enable log: Yes
Enable log rotation: Yes

Miscellaneous
Clean Advertising: Yes

Blacklist options
NO I do not use this leave option empty
Save and apply.





Now that SquidGuard is configured and running we need to setup some instructions for it to follow in terms of what to allow and what to block, this is called Target Categories or Target ACL's you can configure this by navigating to Services -> SquidGuard Proxy filter -> Target Categories

There is a bug in SquidGuard that it will not initiate the blacklist blocking before it has a dummy ACL defined under Target Categories so we need to create 3 ACL's for this to work properly



1. Dummy
2. myBlockList
3. myAllowList

Dummy ACL
Name: Dummy
Description: Dummy ACL
Save





myBlockList
Name: myBlockList
Order: ---
Domain List: facbook.com fb.com youtube.com
URL List: facbook.com/ fb.com/ youtube.com/
Regular Expression: BLANK
Redirect mode: int error page
Redirect: these sites have been blocked by your ADMIN, if you have business reason to visit this page contact your supervisor.
Description: Blocked internet sites
Save





myAllowlist
Name: myAllowlist
Order: ---
Domain List: it-monkey.net company.local
URL List: it-monkey.net/ company.local/
Regular Expression: BLANK
Redirect mode: None
Redirect: BLANK
Description: All allowed sites to bypass Proxy filter
save





You should now have all the needed Target ACL's configured to block Facebook and YouTube, but you may wonder why you put the information in both the Domain List and URL List option of the ACL's and there is a reason for that. If a site uses HTTPS it will read from the Domain List option and if it uses HTTP then it uses URL List option and it the sites uses both then you need to have it in both places to fully block the site

HTTP = URL List
HTTPS = Domain List

Now we need to assign an action for what SquidGuard should do whit the different "Categories" this is where you specify if the list you created is a Blacklist and should be blocked or if it’s a whitelist and should bypass all the filters and always allow traffic for it, to do this navigate to
Services -> SquidGuard Proxy filter -> Common ACL

General Options
Target Rules List  + \ -
[Dummy]  Access: ---
[myBlockList]  Access: Block
[myAllowlist]  Access: Whitelist
Default access [all] Access: Allow



Do not allow IP-Addresses in URL: Yes
Proxy Denied Error: Default
Redirect mode: int error message
Use SafeSearch engine: Yes
Rewrite: None
Save and apply



Now that the entire configuration in Squid and SquidGuard is done you need to apply it to the current running configuration by pressing the large green Apply button has to be pressed found on
Services -> SquidGuard Proxy filter -> General Settings

Quote from: https://doc.pfsense.org
" Important: Please set up at least one category on the 'Target Categories' tab before enabling. The Save button at the bottom of this page must be clicked to save configuration changes. To activate SquidGuard configuration changes, the Apply button must be clicked. "

Now we have to setup WPAD and Firewall rules for pfSense to automatically push the Proxy configuration to its client and also who has access to connect and use the internet on your network, I will setup WPAD first since it will only work when pfSense GUI runs on HTTP and not the default HTTPS so it will affect how you configure your firewall rules.

Step 5. Configuring pfSense to act as WPAD for Squid
For security purpose I am separating the WebGUI and the WPAD servers by using a custom port HTTP TCP port for the WebGUI, I will be running WebGUI on 8080 and WPAD on 80
(8080 is a known admin\ gui port and is only used as example; you should set a custom port for your network)

Stat by creating a allow rule so you don’t lock yourself out of the firewall by going to Firewall -> Rules -> LAN and create an allow rule for port 8080

Action: Pass
Disabled: NO
Interface: LAN
Address Family: IPv4
Protocol: TCP
Source: Single host or alias: IT_Department
Destination: This Firewall (Self)
Destination Port Range: From: other Custom  8080 To: other Custom  8080 
Description: Allow IT-Admins access to WebGUI



I use Aliases for everything, but if you do not have an IT-Department Alias defined, then just set the source to the IP-Address of your main computer.
Save and apply this rule



Now we are ready to change the WebGUI to a custom HTTP port without locking yourself out, to do this navigate to System -> Advanced -> Admin Access

webConfigurator
Protocol: HTTP
TCP port: 8080
Save and apply, then wait for it to automatically redirect your session to the new port this takes about 30sec or so.



Next thing you need to do is set the DNS Record for WPAD to resolve to the webserver that will be hosting your Proxy settings file, since I will run all of this out of pfSense I use the DNS Resolver service for this, If you want you could use whatever DNS and Web server you want as long as you set it to resolve the correct URL to its correct IP.
Navigate to Services -> DNS Resolver add a new Host Override

Host Override Options
Host: wpad
Domain: it-monkey.local  (Set your own internal domain here, if you do not have one you can set one in the System -> General Settings)
IP Address: 192.168.1.1  (LAN IP of pfSense, this has to be set to the local IP of the interface you want to run the Proxy on)
Description: WPAD Autoconfigure Host
Save and Apply



General DNS Settings



Internal Domain Settings



Now we are ready to create the actual client configuration file that will be pushed by this setup, some programing is involved so open your Notepad++ and get ready to create the following 3 files:

wpad.dat
wpad.da
Proxy.pac

All of these files require the same code so it is just a copy\paste or save-as exercise, the code needed is

function FindProxyForURL(url,host)
 {
 return "PROXY IP-of-pfSense-LAN:PORT-of-Squid";
 }

In my setup that would be

function FindProxyForURL(url,host)
 {
 return "PROXY 192.168.1.1:3128";
 }


Now you would need to upload these files to pfSense, I recommend using WinSCP or similar for this the path you want to store these files in are:
/usr/local/www

When all files are uploaded you should see them in the directory like

/usr/local/www/wpad.dat
/usr/local/www/wpad.da
/usr/local/www/Proxy.pac

Now that all this is done we are done whit the WPAD configurations and only need to adjust our firewall rules and lockdown unrestricted access of our network.

Step 6. Logging whit Lightsquid
Lightsquid is currently the only supported and maintained log phraser that you can use whit Squid and SquidGuard on pfSense, this is a small applicatuon that takes all the logs from your proxy server and sort them by your prefrense and the present them to you in a easily read format through its own webinterface. To configure this serverce navigate to Status -> Squid Proxy Reports

Web Service Settings
Lightsquid Web Port: 7445 (Default port, you can use custom port)
Lightsquid Web SSL: Yes
Lightsquid Web User: Admin
Lightsquid Web Password: MysuperSecretandSEXYkeYg3n3ratedbyN0tApA$$w0rdgenetAT0r

Report Template Settings
Language: English
Report Template: Base
Bar Color: Orange

Reporting Settings and Scheduler
IP Resolve Method: DNS
Skip URL(s): None left blank
Refresh Scheduler: None




Step 7. Configuring the Firewall Rules
Start by navigating back to Firewall -> Rules -> LAN
Depending on your preferences you should only need to have about 5 - 8 rules in this list, I currently only have 6 rules defined and in use, those are the following in order

Allow IT Department management access to pfSense
Allow ICMP form LAN Clients
Allow DNS from LAN Clients
Allow WPAD from LAN Clients
Allow Proxy from LAN Clients
Block Everything else from anywhere



Whit this rule set only Ping and DNS traffic is allowed to be used outside of the Proxy filter, this is a good thing for diagnostics purpose in case something breaks for your clients , you can use simple tests for connectivity using Ping and DNS without touching the Proxy or Firewall settings

The rules are defined whit the following details

Allow IT Department management access of pfSense
Action: Pass
Disabled: NO
Interface: LAN
Address Family: IPv4
Protocol: TCP
Source: Single host or alias: IT_Department (alias IT_Department contains IP of 192.168.1.2 which is the main desktop used by IT)
Destination: This Firewall (Self)
Destination Port Range: From: other Custom  PF_MGMT To: other Custom  PF_MGMT  (port alias contains port 22, 7445 and 8080 and allow you to define it in a single rule)
Description: Allow IT Department management access of pfSense



Allow ICMP form LAN Clients
Action: Pass
Disabled: NO
Interface: LAN
Address Family: IPv4
Protocol: ICMP
ICMP Subtypes: Any
Source: LAN Net
Destination: Any 
Description: Allow ICMP



Allow DNS from LAN Clients
Action: Pass
Disabled: NO
Interface: LAN
Address Family: IPv4
Protocol: TCP \ UDP
Source: LAN Net
Destination: ANY
Destination Port Range: From: DNS To: DNS
Description: Allow DNS



Allow WPAD from LAN Clients
Action: Pass
Disabled: NO
Interface: LAN
Address Family: IPv4
Protocol: TCP
Source: LAN Net
Destination: This Firewall (Self)
Destination Port Range: From: other Custom  WPAD To: other Custom WPAD  (port alias WPAD contains port 80 \ HTTP)
Description: Allow WPAD



Allow Proxy from LAN Clients
Action: Pass
Disabled: NO
Interface: LAN
Address Family: IPv4
Protocol: TCP \ UDP
Source: LAN Net
Destination: This Firewall (Self)
Destination Port Range: From: other Custom  3128 To: other Custom  3129
Description: Allow Proxy



Block Everything else from anywhere
Action: BLOCK
Disabled: NO
Interface: LAN
Address Family: IPv4
Protocol: ANY
Source: ANY
Destination: ANY
Destination Port Range: ANY
Log: Yes
Description: Block Everything



Firewall Aliases

PF_MGMT Ports



WPAD



IT_Admin



All Aliases



When you have all these rules created and applied then all the pieces are in place and you are ready to test these settings on your client computer, However since you have done a lot of configurations as changes to the pfSense systems and rules I suggest that you reboot it so you clear out any conflicting rule or state stuck in the system memory, that way you would start testing on a freshly booted system and rule set.

If you follow this guide and it is not working for you and it broke your system, I am not responsible or liability for that as you should not take anything you read on the internet at face value and you should test settings like this in a lab environment and not on your production servers.

Pages: [1] 2