> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/controller-web-server.md).

# Controller Web Server

### Introduction

All Controller 7000 devices must now use the **HTTPS protocol** instead of HTTP by default. As a result, the diagnostics web page is only accessible via: https\://\<controller>/debug.

This tab provides options to:

* Export the CA Certificate - This action will download the current CA certificate.
* Regenerate CA - This action will regenerate CA and automatically deploy new certificates to all controllers, replacing the existing ones.

Additionally, there is an option to force the controller's web server to use HTTP instead of HTTPS, if required.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Controller Web Server** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0fb5db38f50c9cd75fd867e9a3ff11363f645f75%2Fcontrollerwebservertab.png?alt=media)
3. Perform the required function(s):

<details>

<summary>To export CA Certificate</summary>

1. Click the **Export CA Certificate** button.

   The Certificate Export Wizard opens.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-adcbfc6e54a802ba5d882e584b04b3e2143a6e5c%2Fcertificateexportwizard.png?alt=media)
2. Click **Next** to continue.
3. Select DER encoded binary X.509 (.CER) then click **Next**.
4. Browse desired location, then enter filename and click **Save**.
5. Click **Next** and then click **Finish**.

   A message will appear confirming the export was successful. See instructions below for how to install the certificates.

</details>

<details>

<summary>To generate CA</summary>

1. Click the **Regenerate CA** button.
2. Click **Yes** on the warning prompt.

   **Note:** The Valid date is updated.

</details>

4. To force the controller web server to use HTTP, rather than HTTPS, click on the checkbox and then click **Apply**.

   Selecting this option will create a warning in the Security Health Check report.
5. Installing CA certificate into Trusted Root Certification Authorities removed invalid CA error when opening debug web page on a browser.

   **Note:** If the CA is not installed on the computer you are using to access the debug web page, the browser will display a strikethrough HTTPS indicator marked as Not Secure. This indicates that the page is still being accessed over HTTPS, but the CA is not trusted or valid.

   **To install the CA:**

   1. Open the certificate file folder where it was saved.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-264cf56b970b9774e435bb49c7e36094c3aa5f94%2Fcacertificate_dialog.png?alt=media)
   2. Click the **Install Certificate…** button.
   3. Select the store location where you want to save the certificate.
   4. Click **Next**.
   5. Tick **Place all certificates in the following store**.
   6. Click on **Browse**, and select the **Trusted Root Certificate**.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9662f05dad83ea4d3ce86ba23077bf19366cab49%2Fselectcertificatestore_dialog.png?alt=media)
   7. Click **OK**, then **Next**.
   8. Click **Finish**.

      A Security warning displays.
   9. Click **Yes** to proceed with installation.

      A message will appear confirming the export was successful.
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/controller-web-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
