Set up Teams HTTPS certificates
Choose a certificate, configure Host Server, enroll Windows and Android, and renew without breaking access.
On this page
Choose the server address
Use the name clients will actually enter. For https://teams.example.com:8000, the certificate must include teams.example.com in its Subject Alternative Name. If clients use an IP address, the certificate must include that IP.
Use a publicly trusted certificate with private DNS if you control a domain and want to avoid installing trust on each client. For a closed network or no domain, use a private CA or a LocateHub-generated certificate. A maintained reverse proxy can also handle HTTPS.
Use a public certificate with private DNS
DNS-01 validation proves control of the name through a DNS TXT record. The Teams app can remain accessible only on the LAN or VPN.
- Set internal DNS so the chosen name resolves to the private address of the host or proxy.
- Use an ACME client with a DNS-01 plugin for your DNS provider, such as Certbot with the Cloudflare plugin. If using Cloudflare, scope a DNS-edit token to the relevant zone and add zone-read access only if your client needs it. Store it in the ACME client’s protected configuration.
- Request the certificate for the chosen name. In Host Control Center, select Import HTTPS Cert and provide the full-chain PEM certificate and matching unencrypted PEM private key. Keep that key on the host.
- Configure the host to use the matching HTTPS name and restart it. If you installed the Windows service, use Repair Service so the service picks up the certificate paths, then verify that it is running.
Use a private CA or LocateHub certificate
- Import the host’s PEM certificate chain and key from your private CA, or use Generate HTTPS Cert in Host Control Center. Check that the certificate covers every name or IP the clients will use.
- Start or restart the host with HTTPS. If it runs as a Windows service, use Repair Service to apply the certificate configuration.
- Give clients the public CA certificate or supported self-signed certificate through a trusted channel. For supported direct-host configurations, LocateHub’s certificate-only bootstrap port defaults to the HTTPS port plus one. A host on port 8000 serves the download at http://teams.example.com:8001/api/server-certificate.
- If using the bootstrap download, verify its SHA-256 fingerprint against one the administrator provides separately before trusting it. For a private CA, distribute the appropriate CA certificate separately when needed. Use the HTTPS URL for sign-in and job work.
Trust the certificate on Windows and Android
- On Windows, open the certificate import wizard and install the administrator-provided trust certificate into Trusted Root Certification Authorities for the current user or local computer, as directed by your administrator.
- On Android, open Settings → Security or Security & privacy → Encryption & credentials → Install a certificate → CA certificate. Menu labels vary by device. Select the administrator-provided certificate. For a managed device, ask the administrator to deploy it if installation is restricted.
- From Windows and Android on the LAN or VPN, test the exact HTTPS address before signing in. Open a known job and download a test PDF after you sign in.
Terminate HTTPS at a reverse proxy
Install the certificate on the proxy and forward the original hostname and HTTPS scheme to LocateHub. Use LocateHub’s proxy mode and keep the upstream on loopback or a restricted private address. Test client sign-in and downloads before enabling application-level HTTPS redirects.
Renew and diagnose
Schedule ACME renewal and verify the updated certificate reaches your host or proxy. For direct HTTPS, import the renewed files and restart the host. For the Windows service, repair or restart it as required to use the renewed files. Distribute a replacement private CA before changing the trust chain.
For a name mismatch, check the URL against the certificate names. For an untrusted issuer, check the full chain and client trust store. For an expiry error, check the certificate being served and the device clock. For a timeout, check name resolution, VPN, firewall and host service first.