Skip to content

Use sslbrain Cloud (EU) for your account, licence and access to your appliances.

  • An email address for the account.
  • Access to the appliance if you need to activate it.
  1. Create an account at sslbrain.com/cloud/register with an email address and password.
  2. Confirm the email address using the link in the email.
  3. Sign in at sslbrain.com/cloud/login.

You can open Appliances and Licences and units. The appliance fetches its licence from sslbrain Cloud. Your certificates, private keys and settings are held on the appliance.

  • No activated appliance in the list → complete First-time setup.
  • You can see invoices but no appliance → ask the account’s Owner or Administrator for access under Team.
  • The appliance cannot reach sslbrain Cloud → check the connection from the console menu.
  • Two-Factor Auth protects sslbrain Cloud sign-in with an authenticator app (TOTP). Save the recovery codes so you can sign in without the app. The account can remember trusted devices. Local passwords and AD sign-in on the appliance do not use Cloud two-factor authentication.
  • Notifications holds the email addresses, at most 10, that alerts from the appliance’s E-mail (Cloud) channel go to. If none are listed, they go to the account owner. See Keep an eye on your certificates.

Each user enables two-factor authentication individually. Organisations cannot require it for all users.

RoleCan
OwnerEverything
AdministratorThe same as Owner, except renaming the AutoDNS name
OperatorDay-to-day work and certificate setup. Sees licences and the team, nothing to do with payment
ViewerView, not change
BillingLicences, purchases, invoices, the data processing agreement and payment events in the Audit log. No access to appliances

When you sign in to the appliance with sslbrain Cloud, the role here also sets the role on the appliance. See Users and sign-in.

Appliances shows every appliance activated with the account: hostname, tier, licence, version and last contact. An appliance appears in the list when someone signs in to it with the account and chooses a licence.

Click an appliance to see:

  • Overview: appliance id, IP address, registration date, and the Display name the appliance is shown with in the portal.
  • Licence: the licence history, and Switch licence to another of the account’s licences. The appliance keeps its identity, data and certificates.
  • Certificates: the certificates sslbrain Cloud has issued to the appliance.
  • AutoDNS names: the names the appliance uses for CNAME delegation.
  • Danger zone: release the licence. See Move the licence to another appliance.

Only Owner and Administrator can switch and release licences.

Downloads and requirements at the bottom of the menu has the files and requirements for a new appliance. Every role except Billing can open the page once the account has accepted the licence terms and the data processing agreement. Your licences shows the licences a new appliance can take.

FileFor
OVAVMware and other hypervisors that import OVF
qcow2KVM, libvirt and Proxmox
docker-compose.ymlDocker on your own Linux server
  • Docker: follow the installation guide. For an existing Compose installation, see adding the controller.
  • OVA and qcow2: the page lists version, size and SHA-256. The VM image version is the date the image was built. The first time the machine starts, it installs the newest signed version of sslbrain. The OVA and qcow2 files are not signed; the appliance image they fetch is. See Security.

ACME is the protocol a CA uses to issue certificates automatically.

Requirements:

  • Virtual appliance: 2 vCPU, 4 GB RAM and 40 GB disk (thin provisioned).
  • Docker: Docker 24.0 or newer, Docker Compose v2, 4 GB RAM, 20 GB disk space and access to the CAs’ ACME endpoints.
  • Outbound HTTPS (443) to registry.sslbrain.com, cloud.sslbrain.com and acme.sslbrain.com.
  • The virtual appliance also needs outbound HTTP (80) to archive.ubuntu.com and security.ubuntu.com for operating system security updates.
  • No inbound ports from the internet.

All ports, including those on your own network, are under Security.

A licence belongs to one appliance and sets how much it can manage. There are four tiers: Free, Basic, Professional and Enterprise.

LimitFreeBasicProfessionalEnterprise
Servers55050 to 500 by licence100 to 1,000 by licence
Installation plans10100two per servertwo per server
Logins1310No licence limit
Domains per account2No licence limitNo licence limitNo licence limit
Names per certificate100CA limitCA limitCA limit
Certificate profiles13No licence limitNo licence limit
Own integrations13No licence limitNo licence limit

CA limits and the daily issuance limit still apply where the licence has no limit. Certificates and renewals are included at no extra charge, except commercial certificates paid for with units.

FeatureFrom
Alerts by E-mail (SMTP) and WebhookBasic
Certificate uploadBasic
Alerts in Slack, Microsoft Teams and TelegramProfessional
Service agents via sslbrain CloudProfessional
Maintenance windowsProfessional
Audit log exportProfessional
Alerts in PagerDuty and OpsGenieEnterprise
Windows CAEnterprise, plus an add-on that FairSSL switches on for the licence
  • Servers: the licence covers the oldest servers up to the limit. Servers beyond the limit are deactivated and shown as unlicensed. A new server is never refused.
  • Installation plans: capacity is listed in the table. A paused installation plan counts; the appliance’s own does not.
  • A paid licence expires: the appliance falls back to Free. The licence becomes a Free licence on the appliance it was on, and cannot be used on another.

Every account has a Free licence from the start. The appliance’s page Appliance › Licence and status › Licence opens Licences and units in sslbrain Cloud.

Units pay for the commercial DV certificates sslbrain Cloud issues. Cloud sells DV certificates only. The same unit calculation applies to every CA:

  • One name uses one unit. Its www.<name> companion is free.
  • One wildcard uses three units. Its base domain is free.
  • Several names use one base unit plus one unit per name and three per wildcard name. Two names use three units. One name and one wildcard use five units.
  • Each further name uses one unit. Each further wildcard uses three.

A 20 % unit surcharge applies when the domain can only be validated with DigiCert’s persistent TXT record. AutoDNS (CNAME) removes the surcharge. See unit prices.

  • Units are deducted when a paid certificate is issued, and are held by open orders.
  • The balance plus the credit limit FairSSL has set must cover the order.
  • Buy units creates an invoice straight away. Pay by card or bank transfer.
  • Owner, Administrator and Billing can buy.
  • The account receives an email when the balance is low.

Which certificates a profile can fetch: Choose where certificates come from.

Give colleagues access to one or more appliances.

The Operator and Viewer roles come with Professional and Enterprise, both in sslbrain Cloud and on the appliance.

  1. Open Team and find Add a person.

  2. Enter the email address, choose the appliances, and choose the role: Administrator, Operator or Viewer. If the person should only see licences and invoices, choose Billing and no appliance.

  3. Click Add.

If the person is already a member of the account, they have access straight away. Otherwise an invitation is sent that is valid for 7 days. It can be resent or revoked.

  • The Owner role cannot be assigned.
  • Nobody can change their own role.
  • Owner and Administrator manage the team. Operator can see it.

The team page shows, for example, “3 of 10 logins”. The count is every user plus pending invitations, across all the account’s appliances. The appliance counts its own logins, see Users and sign-in.

Data does not move with the licence. Certificates, private keys, service agents and settings stay on the appliance you are leaving.

  1. Open Appliances in sslbrain Cloud and click the appliance you are leaving.

  2. Find the card Move this licence to another machine under Danger zone, and click Release the licence. This needs Owner or Administrator.

  3. Type release and click Release it. The appliance keeps running until the new one takes over the licence.

  4. Set up the new appliance as in First-time setup. When you choose a licence, choose Move the licence from and the name of the appliance you are leaving.

  5. Set up the rest as in steps 3 to 8, starting from A name and certificate for the appliance.

When the new appliance takes over the licence, the one you are leaving is retired. It shows This installation has been retired and no longer serves anything. Its local data can still be opened with the 12 backup words.