StifleR
2.10
2.10
  • Start Here - StifleR 2.10
  • Introduction
    • StifleR Overview
      • The StifleR Solution
      • Managing Microsoft Data Transfer Services
    • Technical Overview
      • 2Pint BranchCache Administrator Guide
    • Features Overview
      • Control
      • Monitor
      • Automate
      • Other Features
      • StifleR Feature Details
    • Release Notes
  • Proof of Concept
    • Objectives and Prerequisites
    • Configure Microsoft Peer-to-Peer Components
    • Install and Configure StifleR
    • Testing and Validation
    • StifleR POC Quick Checklist
  • Planning
    • StifleR Server Considerations
    • StifleR Client Considerations
    • Firewall Ports
    • Permissions
    • Antivirus Exclusions
    • Network Topology
    • StifleR Generic Concepts
      • Client Leader Roles
        • Red Leader
        • Blue Leader
        • Green Leader
        • Examples of Leader Selection
      • Templates
      • Beacons
  • Installation
    • Overview
    • Server
      • StifleR Server Installation
      • StifleR Dashboard Installation
      • StifleR Beacon Installation
    • Client
      • StifleR Client Installation
      • Post Installation Checks
  • Configuration
    • Configuration Files
      • StifleR Server Configuration File
        • Using the AppSettings Override File
      • StifleR Client Configuration File
      • StifleR Dashboard Configuration File
    • Configuring BranchCache on Windows Server
    • Configuring Delivery Optimization
    • Configuring LEDBAT on CM DPs
    • Configuring a Beacon Server
    • Configuring StifleR SQL History
    • StifleR Network Locations
      • Automatic linking of Location, Network Groups and Networks
      • Network Topology Automation
      • Location Fields
        • Network Group Fields
          • Network Fields
    • StifleRulez.xml Configuration Guide
      • The Match – TypeData
        • When the Job Title Isn’t Suitable
        • ConfigMgr Specific Rules
      • The Setting - DownloadTypes
        • Delivery Optimization Jobs
      • Sample StifleRulez.xml
    • Securing StifleR Operations with SSL
      • Prerequisites
      • Using a Web Server Certificate
        • Requesting a Web Server Certificate
      • Using a Self-Signed Certificate
      • Preparing the StifleR Dashboard Web Site for SSL
      • Configuring StifleR to Use SSL
      • Finding the Certificate Thumbprint
    • StifleR Client Access Control Options
  • Operations
    • Dashboard
      • Overview & Navigation
        • Home Page
        • Traffic & Downloads
          • Transfers & Downloads
            • How to use query hosts search?
          • Running Sequences
          • Weekly Downloads Activity
          • History
        • Devices
          • Clients
            • Client Details
              • How to use an extended search?
          • Servers
          • StifleR Server
            • Templates Detail
        • Cache Management
        • System Resource Usage
        • Network Topology
          • Maps
          • Countries
          • Locations
            • Bandwidth Allocations and Locations
          • Network Groups
          • Networks
        • Reporting & Diagrams
    • Client Management & Remote Tools
      • Remote PowerShell Session
      • Remote Performance Counter
      • Remote WMI Browsing
      • Remote Event Log Viewer
      • Remote Netmon Session
    • Monitoring
      • StifleR server health
      • StifleR client health
      • BranchCache Testing and Monitoring
    • Maintenance tasks
    • Bandwidth Management and Allocation
      • Bandwidth Tuning Monitoring and Control
    • Backup and Recovery
      • Moving the StifleR Server Databases to a New Drive on the Same Server
    • Troubleshooting
      • StifleR Client Command Line Options
      • BranchCache across Subnets
    • StifleR WMI Provider
Powered by GitBook
On this page
  1. Configuration
  2. Configuration Files

StifleR Dashboard Configuration File

PreviousStifleR Client Configuration FileNextConfiguring BranchCache on Windows Server

Last updated 3 months ago

The StifleR Dashboard configuration file is used to configure how the Dashboard accesses the StifleR Server service. The config file (config.json) is located within the program files directory in which the StifleR Dashboard was installed.

For example, if the StifleR Dashboard was installed under C:\Program Files\2Pint Software

...then the configuration file would be located in this location: C:\Program Files\2Pint Software\StifleR Dashboards\Dashboard Files\assets\config

The most important settings in the config.json file are referenced in the "apiServers" section. The values for backendServerUrl and backendLocationServerUrl are set during the .

  "apiServers": {
    "backendServerUrl": "http://StifleRServer.domain.com:1414",
    "backendLocationServerUrl": "http://StifleRServer.domain.com:9000/api",
    "chainHomeSystemVersion": ""
  },

Note: If when the StifleR Dashboard was installed, you entered the above URLs as HTTP and later enabled HTTPS, then the above values should be modified to HTTPS.

You can check whether StifleR is configured to use HTTPS by checking the and reviewing the ListenToUrl and LocationWSListenToUrl values.

Configuring the Dashboard to Use HTTPS

If when the StifleR Dashboard was installed, you entered the above URLs as HTTP and would like to switch to HTTPS you will need to make modifications to several files.

Note: The StifleR SignalR communications protocol uses port 1414 by default, and is primarily used for client communications. This section does not address switching clients to use HTTPS based communications.

To switch from HTTP to HTTPS communications for the Dashboard, you will need to complete several steps:

  • Acquire a Web Server certificate - see for more information on how to configure a web certificate for IIS.

  • Copy the thumbprint value from the web server certificate - see to find your certificate thumbprint.

  1. Edit the config.json file on the server hosting the Dashboard: C:\Program Files\2Pint Software\StifleR Dashboards\Dashboard Files\assets\config.

  2. Modify the URL for the backendLocationServerUrl value to https://. Example:

    "apiServers": {      
          "backendLocationServerUrl": "http://StifleRServer.domain.com:9000/api",
  3. Edit the StifleR Server Config file (StifleR.Service.exe.config) which is located in the Program Files folder on the StifleR Server.

  4. Modify the value: LocationWSListenToUrl to: https://*:9000"/ Modify the value: WebServiceCertificateThumbprint to your web server certificate thumbprint.

  5. Restart the "2Pint Software StifleR Server" service. Example:

    <add key="LocationWSListenToUrl" value="https://*:9000"/>
    <add key="WebServiceCertificateThumbprint" value="3d6ccb8c908b5986d6fa1669dad5e44dfd7715c9"/>

StifleR Dashboard Installation
StifleR Server Configuration File
this page
Prepare the StifleR Dashboard Web Site for SSL
this page