---
title: "Complete the HTTPS Settings fields when configuring a Portal"
slug: "https-settings-v6-7"
description: "Complete the HTTPS Settings fields when configuring a Portal appliance, such as the Portal hostname and allowed sources of traffic."
tags: ["Appliance Configuration", "Portal"]
updated: 2026-03-16T19:21:44Z
published: 2026-04-03T16:41:06Z
canonical: "support.appgate.com/https-settings-v6-7"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.appgate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HTTPS Settings

Complete the following fields to configure HTTPS settings for a **Portal** appliance:

- ***Portal hostname.*** This is the Portal's public hostname. Use a fully-qualified domain name related to the PKCS #12 below. The Portal requires a FQDN for the Portal hostname where users go to sign in using a web client. They will also be redirected here if they use the URL of the protected host they are trying to access. A PKCS#12 file containing a certificate signed by a trusted CA (for the Portal hostname) and the private key; these are required to terminate this HTTPS connection from the user.
- ***HTTPS Certificate - PKCS #12.*** Upload a PKCS #12 file which includes a CA signed certificate for the Portal hostname.
  - *File.* Select the PKCS #12 file to upload.
  - *Password.* The password for the PKCS #12 file.

See [Adding third party certificates](/v1/docs/adding-3rd-party-certificates-v6-7) for more details

- ***Allowed Sources.*** By default, all incoming traffic is allowed. You can limit this to only IP address that match at least one of these source addresses.
- ***TLS Ciphers.*** TLS ciphers the Portal can use. Use the default ciphers unless your browsers require some other specific cipher to be used.