Skip to content
Docs

HTTPS certificates

FileAgent's console is HTTPS-only. Replace the default self-signed certificate with your own so administrators connect without browser warnings.

Last updated July 17, 2026

#Why you'll see a warning at first

New installs generate a self-signed certificate when no certificate of your own is configured, so the console is encrypted from day one. Browsers show a certificate warning for self-signed certificates until you install one that your organization trusts.

#Installing your certificate

Certificate settings are under Settings → System Configuration → HTTPS / TLS Certificate. FileAgent accepts:

  • A password-protected .pfx / .p12 bundle, or
  • A certificate file (.crt, .cer, or .pem) with its matching private key.

FileAgent validates the certificate material before installing it. Use a certificate whose subject/SAN matches the hostname or DNS name administrators will use in the browser.

After replacing the certificate, restart the web service if FileAgent prompts you or the new certificate isn't served immediately.

#How to reach the console

Open FileAgent with a name covered by the certificate — https://<hostname>, https://<server-ip>, or a DNS record pointed at the host. Don't bookmark plain http:// URLs; the console is HTTPS only.

#Best practices

  • Use a certificate from your organization's certificate authority whose SAN matches the DNS name admins use.
  • Track its expiry and renew before it lapses.
  • Keep the private key protected and limited to administrators.