Site Bindings

The Site Bindings interface provides visibility into the endpoints exposed by Open iT Ingress. It displays the active listening addresses, associated hosts and ports, and the certificates used to secure incoming connections.

While the web interface allows you to view the current bindings and their status, site bindings themselves are configured directly on the machine where Ingress is installed. For instructions on how to configure or add new bindings, see Adding Multiple Site Bindings.

Site Bindings

Each row in the table represents a site binding with the following information:

Column	Description
Status	Indicates whether the binding is successfully active. Bound – Indicates that the service is active and successfully running. Not Bound – Indicates that the service is not currently running.
URI	The full address used to access the entry point, including the protocol, host, and port.
Scheme	The protocol used by the binding, such as HTTP or HTTPS.
Host	The hostname or machine name where the binding is configured.
Port	The network port on which Ingress listens for incoming connections.
Certificate Used	Indicates the certificate type used to secure the connection when HTTPS is enabled (for example, PEM pair, PFX, or Auto HTTPS / Let’s Encrypt).

Ingress Site Bindings Details

Site bindings can use different certificate formats or sources to secure HTTPS connections.

Certificate Type	Description
PEM Pair	Uses a certificate file (.crt) together with its corresponding private key (.key) in PEM (Privacy-Enhanced Mail) format. These files are stored separately and must match for HTTPS to function correctly.
PFX	Uses a .pfx file that contains the certificate, private key, and optionally the certificate chain in a single bundle.
Auto HTTPS / Let’s Encrypt	Automatically obtains and manages HTTPS certificates using Let’s Encrypt. Ingress handles certificate issuance and renewal, simplifying HTTPS configuration.

Ingress Certificate Types