> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/3.1/configuration/securing-stifler-operations-with-ssl/running-signalr-with-ssl.md).

# Configuring StifleR to use SSL

With the certificate installed, to switch to SSL for SignalR and Dashboard communications, you will need to do the following:

* Modify the StifleR Server configuration settings.
* Modify the Dashboard configuration file.
* Modify the StifleR Client configuration file. 

### StifleR Server Service 

You'll also need to modify the SignalR URL and Web Service URLS in the[ StifleR Server Configuration File](broken://pages/nHStlYiqePE9p1g7bKrM):

```
<add key="ListenToUrl" value="https://*:1414/" />
<add key="LocationWSListenToUrl" value="https://*:9000/"/>
```

This binds SignalR to all IP addresses on Port 1414. You can also specify a specific IP address, but using \* is more portable especially if you set the value as part of a shared configuration file.

The [certificate thumbprint](/stifler/3.1/configuration/securing-stifler-operations-with-ssl/finding-the-certhash.md) will also need to be added to the [StifleR Server Configuration File](broken://pages/nHStlYiqePE9p1g7bKrM):

```
<add key="SignalRCertificateThumbprint" value="thumbprint value"/>
<add key="WebServiceCertificateThumbprint" value="thumbprint value"/>
```

For the StifleR Server to use any changed settings above, the StifleR Server service must be restarted.&#x20;

### StiflelR Dashboard URL Configuration

To configure the web page which will connect to the SignalR service, change the URL in the file [StifleR Dashboard Configuration File](broken://pages/sL3rvzzq7UovRhGxpCfa). The value should reflect the https URLs for the StifleR Server:

```
    "controller": "https://StifleRServer.domain.com:9000",
    "hub": "https://StifleRServer.domain.com:1414"
```

{% hint style="info" %}
As with all certificates, make sure that the FQDN that exactly matches the certificate name. If the Dashboard is hosted on the local machine, you cannot use 'localhost', NetBiosName, or IP address. Use only the name to which the certificate is assigned.
{% endhint %}

### Clients

On new and existing StifleR Clients, the SSL info is set in the [StifleR Client Configuration File](broken://pages/oawEeEGDtdQVU7o0yKF6):

```
<add key="StiflerServers" value="https://StifleRServerName:1414”/>
```

To validate that the client is successfully connecting to the StifleR Server, restart the StifleR Client Service. Check the Event Viewer on the client within:&#x20;

**Applications and Services Logs / TwoPintSoftware / StifleR.ClientApp / SignalR / Operational**

There should be an entry for a corresponding event such as:

*Connection completed: Server <https://StifleRServerName:1414/> Status: RanToCompletion*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/3.1/configuration/securing-stifler-operations-with-ssl/running-signalr-with-ssl.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.