> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/installation/logicnets-installation-configuring-https.md).

# LogicNets Installation: Configuring HTTPS

## Description

From LogicNets version 7.3 onwards, LogicNets enforces the use of encrypted traffic to ensure the security of customer data. If you are running a prior version of LogicNets with HTTP only and you upgrade to release 7.3 or higher, you must update the IIS binding to enable HTTPS. If you do not update the IIS binding you may have access problems, such as an HTTP error 404.

## Enable HTTPS

To enable HTTPS you must first obtain a valid certificate and import it in IIS. After that you can perform the following steps to update your bindings for HTTPS:

1. Open the IIS manager from the system where the application is configured.
2. Select and right-click the site associated with your traffic.
3. Click *Binding* (you can also select the site and select binding in the action menu on the right-hand side of the screen).
4. If there is no HTTPS binding already configured, do the following:
   1. Click ***Add***.
   2. Under Type select ***HTTPS***.
   3. Under hostname type the same binding as is configured for the HTTP binding. This is the same URL you used during the installation process.
   4. Select the appropriate SSL certificate.
   5. Leave everything else on its default value and click ***OK***.
   6. To verify your binding was configured correctly, navigate to the site using HTTPS (e.g.: [https://Logicnets.abc.com](https://logicnets.abc.com/)). Your site should be reachable.

Alternatively, you can switch off *Enforce HTTPS* in the LogicNets System Configuration module. This is not recommended and should only be done when HTTPS cannot be supported.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/system-administration/installation/logicnets-installation-configuring-https.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.