Skip to content

Follow the steps from installation to the first certificate that is installed and renewed automatically on one of your servers.

Drawing: how sslbrain works. sslbrain Cloud (EU) sits at the top between a DNS card (domain validation) and a CA stamp. In your network, sslbrain On-Premise talks to Cloud; a Windows and a Linux service agent fetch certificates from On-Premise, which pushes them to a FortiGate and an F5. A Windows server at a remote site connects through Cloud.
  • Your network: sslbrain On-Premise runs here and generates the private keys, and sslbrain Cloud (EU) never sees them. On-Premise talks only to Cloud, outbound on port 443.
  • Domain validation: a CNAME to your.autodns.sslbrain.net, access to your DNS provider’s API, or a dns-persist-01 TXT record.
  • CA: your choice of Let’s Encrypt, DigiCert, Google Public CA, Sectigo or GlobalSign, or your own Windows Certificate Services. Cloud talks to the CA and to DNS.
  • Service agent: Windows and Linux servers fetch them from On-Premise on port 443.
  • Push installation: devices without a service agent get their certificates from On-Premise, for example FortiGate, F5, NetScaler, Palo Alto and other equipment.
  • Remote site: a service agent in a DMZ or at a remote site connects via sslbrain Cloud (EU), outbound on port 443 and E2E, with no connection to your network.

Start at step 1 and follow the next step on each page. You can skip step 4.

Under Getting started, each task gets a tick when it is completed:

  1. Connect a server.
  2. Make a domain ready.
  3. Create installation plans automatically.

Check the installed certificate as described in step 8. If the appliance cannot reach the server, see Servers outside your network.

Find the guide for your situation.

Keep track of certificates, updates and backups.

Look up features and settings.