# StifleR Dashboard installation

Prerequisites

## Installation

From an Elevated Command prompt launch **StifleR.Dashboard.Installer64.msi**.

At the "Welcome" screen, feel welcomed, and then click **Next**.

<figure><img src="/files/WKwFvWgtyOewLwTtAWaF" alt=""><figcaption></figcaption></figure>

***

At the "End-User License Agreement" screen, once you have reviewed the EULA, check the box: \
**I accept the terms in the License Agreement**, and then click **Next**.

<figure><img src="/files/R8UDk4HyRCeRi3ejP0hn" alt=""><figcaption></figcaption></figure>

***

At the "Destination Folder" screen, enter the path to the directory where the StifleR dashboard program files should be installed and then click **Next**.

<figure><img src="/files/pYR6RvvY14tgqRZ7YVWj" alt=""><figcaption></figcaption></figure>

***

At the "Select Operation Mode and Parameters" screen, verify the URLs for the dashboard to connect to the StifleR server and dashboard web service. By default, the port number for the StifleR service is 1414. If during the [StifleR Server installation](/stifler/setup/installation/stifler-server-installation.md), a different port was used, modify the URL accordingly. Once complete, click **Next** to continue.

{% hint style="info" %}
Note: By default, the installation wizard will define the URLs as HTTP-based sites. It is acceptable to install the Dashboard using HTTP for testing, but in production, it is strongly recommended to use HTTPS. To configure the Dashboard to use HTTPS, simply change the URLs to https\://\<servername>:\<port>.\
For more information on how to secure IIS for HTTPS, see: [Using a Web Server Certificate](/stifler/configuration/securing-stifler-operations-with-ssl/using-a-full-iis-certificate.md).
{% endhint %}

<figure><img src="/files/3cucj2fNTyxNep2rCRDv" alt=""><figcaption></figcaption></figure>

***

At the "Ready to install..." screen, click **Install** to begin the installation.

<figure><img src="/files/wyMMuzXgeQspTC7Axt0d" alt=""><figcaption></figcaption></figure>

***

At the "Completed" screen, the installation wizard is complete. Click **Finish**.

<figure><img src="/files/tFjwuWSh2HitZF92DoHT" alt=""><figcaption></figcaption></figure>

## Post installation

#### Confirm Config File

Open notepad elevated, browse to the server.json file located in the C:\Program
\
Files\2Pint Software\StifleR Dashboards\Dashboard Files\assets\config folder, and ensure
&#x20;the controller and hub values are set to [https://FQDN:Port](https://documentation.2pintsoftware.com/stifler/setup/installation/https:/FQDN:Port) as in the examples below (these should already be set properly from the installation):

* "controller": "<https://StifleR.company.com:9000>"
* "hub": "<https://StifleR.company.com:1414>"

<figure><img src="/files/SCASvUIFhQj9alqhWTlY" alt=""><figcaption></figcaption></figure>

### Installed to non default location

If you've installed the dashboard to a non-standard location, IE D:\2Pint\Dashboard, you must update the StifleR config so it knows where to find the dashboard.  If you don't, then you'll get some errors trying to pull up the dashboard through port 9000.

<figure><img src="/files/rLBbISeVSAFpWvIXabYm" alt=""><figcaption></figcaption></figure>

### Testing the StifleR Dashboard website

Navigate to the StifleR Dashboard website by visiting the URL defined during the setup wizard. By default this would be something like:\
**<https://servername.domain.com:9000/dashboard>**<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/setup/installation/stifler-dashboard-installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.