# HTTPS Configuration HTTPS is supported for the profiles *test-local-3nodes and test-network.* ### Certificate The certificates are held in the configuration profile folder (e.g, `${MEDCO_SETUP_DIR}/deployments/test-local-3nodes/configuration`): * *certificate.key*: private key * *certificate.crt*: certificate of own node * *srv0-certificate.crt*, *srv1-certificate.crt*, …: certificates of all nodes of the network ### Enable HTTPS for the Local Local Deployment To enable HTTPS for the profile *test-local-3nodes*, replace the files *certificate.key* and *certificate.crt* from the *configuration profile* folder with your own versions. Such a certificate can be obtained for example through [Let’s Encrypt](https://letsencrypt.org/). Then edit the file `.env` from the *compose profile*, replace the `http` with `https`, and restart the deployment. ### Configure HTTPS for the Network Deployment For this profile, HTTPS is mandatory. The profile generation script generates and uses default self-signed certificates for each node. Those are perfectly fine to be used, but because they are self-signed, an HTTPS warning will be displayed to users in their browser when accessing one of the Glowing Bear instance. There is currently only one way of avoiding this warning: configuring the browsers of your users to trust this certificate. This procedure is specific to the browsers and operating systems used at your site. --- # 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://ldsec.gitbook.io/medco-documentation/v2.0.1/system-administrators/deployment/configuration/https-configuration.md?ask= ``` 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.