Skip to content
BILLETKnowledge Base

Server

Run the portal and the relay on your own Linux servers.

  1. Before you install the serverWhat the portal and relay are, what servers, names, certificates and ports they need, and what is in the server download.For Administrators
  2. Install the portalUnpack the server release, set up PostgreSQL, the portal's account, folders and secrets, create its database and run it as a systemd service.For Administrators
  3. Put the portal behind a reverse proxyAn nginx site for the portal, with its TLS certificate, the paths that must reach the portal, and what changes for Cloudflare and Amazon DCV.For Administrators
  4. Sign in to the console for the first timeCreate your own system administrator account, or use the first-run account the portal makes, and replace it.For Administrators
  5. Create the certificate authorityCreate the portal's own certificate authority once, on the first portal node, and keep it safe. Hosts and relays are issued certificates from it.For Administrators
  6. Activate your licenseEnter your license key and deployment ID in the console, what the License page shows, and what the portal sends when it checks in.For Administrators
  7. Install a relayInstall the relay on a Linux server, give it a certificate for browser sessions, enroll it with the portal and run it as a service.For Administrators
  8. Networking: the DCV gateway and the Billet relayWhat the Amazon DCV Connection Gateway and the Billet relay each carry, who connects to whom, and the ports and firewall rules each one needs.For Administrators
  9. Create a tenant and connect single sign-onCreate the organization people belong to, connect it to your identity provider over SAML 2.0, and optionally provision people automatically with SCIM.For Administrators
  10. Restrict who can reach the consoleMove administrator sign-in to a name of its own, and allow it only from your own networks, so the console is not there to find from the internet.For Administrators
  11. Give tenants their own addressesLet each tenant sign in at a name of its own, such as acme.desktops.example.com, and the DNS record, certificate and proxy settings that needs.For Administrators
  12. Check the deployment is readyThe console's Readiness list and the matching server command, which say whether every required piece of a new deployment is in place.For Administrators