> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure the log file location

> Create a log directory the Online Responder can write to and point the Futurex FXCL KMES CNG provider configuration at it.

The Online Responder service runs as the Network Service account, so the FXCL CNG provider's log file must be placed in a directory that account can write to.

<Note>
  The log file must be stored in a location accessible by the Network Service account, which is
  the account used by the Online Responder service. Using a path under `C:\Users\` will cause
  log writes to fail silently when the Online Responder calls CryptoHub.
</Note>

<Steps>
  <Step>
    Create the log directory and grant Network Service write access:

    ```powershell expandable lines wrap title="PowerShell" theme={null} theme={null}
    New-Item -Path "C:\ProgramData\Futurex" -ItemType Directory -Force
    icacls "C:\ProgramData\Futurex" /grant "NETWORK SERVICE:(OI)(CI)F"
    ```

    <Check>
      Verify the permissions were applied correctly:

      ```powershell expandable lines wrap title="PowerShell" theme={null} theme={null}
      $acl = Get-Acl "C:\ProgramData\Futurex"
      $acl.Access | Format-Table IdentityReference, FileSystemRights, AccessControlType
      ```

      Confirm that `NT AUTHORITY\NETWORK SERVICE` appears with `FullControl` in the output.
    </Check>
  </Step>

  <Step>
    In `config.json`, set the log file path to the new directory:

    ```json expandable lines wrap title="cryptohub.json" theme={null} theme={null}
    "log_file": "C:\\ProgramData\\Futurex\\fxcl.log",
    ```

    <Note>
      For development testing, set the `log_level` to `traffic` and `enable_debug_view` to
      `true`. Once in production, set the `log_level` to `info` and `enable_debug_view` to
      `false`.
    </Note>
  </Step>
</Steps>