An encrypted connection to the requested name
People still say SSL certificate, although modern HTTPS uses TLS. TLS encrypts the connection and lets the browser authenticate the server. A certificate contains the covered domain names, a public key and a validity period, among other details.
The browser checks whether the certificate covers the requested name, is within its validity period and has a certificate chain leading to an authority it trusts. Owning a certificate does not make a server accessible over HTTPS by itself. The server or a proxy in front of it must also be configured to serve TLS.
Why adding www can trigger a warning
example.com and www.example.com are separate names. To serve both over HTTPS, the certificate presented for each request must cover the requested name. This applies even if one address only redirects to the other, because the encrypted connection is established before the redirect.
A wildcard such as *.example.com covers names such as portal.example.com. It does not cover example.com or internal.portal.example.com unless those names are also listed in the certificate.
Check expiry, DNS and the proxy
An expired certificate or a name mismatch usually causes a browser warning or a connection error. After renewal, check that the public server actually presents the new certificate.
DNS determines which destination the browser reaches. If a domain still points to the old server after a move, visitors may receive a different certificate. When a proxy terminates TLS, the browser sees the proxy’s certificate. The connection from that proxy to the application is separate and needs its own configuration.
HTTPS does not certify the application
HTTPS protects data on the encrypted connection. It does not certify that an application is free from bugs or that its operator is trustworthy. A fraudulent website can have a valid certificate for its own domain. Access control, secure storage and protection against application vulnerabilities remain separate responsibilities.
Connecting a MainPath domain over HTTPS
MainPath shows the expected and actual DNS values under Domains. For published applications, Traefik routes requests to the appropriate container based on the domain, and MainPath sets up the HTTPS certificates. See Publish web apps for the workflow. The domain, destination server and configuration must agree for the browser to reach the intended application.