Documentation Index
Fetch the complete documentation index at: https://bloodhound.specterops.io/llms.txt
Use this file to discover all available pages before exploring further.
Pre-install checklist
The following checklist summarizes the install-blocking gates and pre-deployment work that must be completed before running the installer.Web-based installer
The web-based installer provides an interactive setup experience through a web interface. It guides you through configuration steps such as domain setup, certificate management, and database connectivity.Configure install options
The web-based installer is available through the SpecterOps - BloodHound Enterprise Portal. You’ll work with two interfaces during installation:- The Installer tab in the portal generates the download and install commands you run on your Linux host. The Update tab in the portal tracks active and inactive online installations.
- The Installation Wizard is a companion UI served from your Linux host on port
30080. After the initial install completes, you use the Installation Wizard to finish configuration (domain, certificates, database) and run .
Navigate to the web-based installer
- Log in to the SpecterOps - BloodHound Enterprise Portal.
-
Click the Install tab at the top of the page to open the Installation Guide.
The installation options displayed on this page depend on the licensing associated with your account.
Choose installation options
- Enter a name for your BloodHound Enterprise instance.
-
Choose one of the following Network Availability options:
Option Use this when Outbound requests allowed The Kubernetes cluster can make outbound internet requests. Outbound requests require HTTPS Proxy Outbound traffic must go through a proxy server. If you choose the proxy option, a Configure proxy URL field appears on the next page of the installer where you can enter your proxy URL.The installer also adds--proxy $YOUR_PROXY_URLto the download and install commands on the next page to ensure the installer can access the internet through your proxy. -
Click the toggle for Show instructions to relocate images to your private registry if your environment requires the cluster to pull container images from a private registry you control.
This is typically required for air-gapped or restricted networks, or to meet internal supply-chain and compliance requirements.
If you choose this option, the next page provides a field for entering your private registry URL and instructions for running the necessary commands on your Linux host to:
- Pull the necessary container images
- Tag them with your private registry URL
- Push them to your registry
--registry $YOUR_REGISTRY_URLto the install command on the next page to ensure the cluster pulls images from your registry during installation.
- Click Continue.
Install on the Linux host
The installation instructions page generates the exact download and install commands for your release, including a signed URL, a short-lived bearer token, and your specific version. The following screenshot shows an example of the install instructions page in the portal, which provides the commands you run on your Linux host to download and install BloodHound Enterprise.
Configure the install command in the portal
- In the Select Version field, choose the version of BloodHound Enterprise you want to install.
-
If you selected the proxy option in the previous installation options, enter your proxy URL in the Configure proxy URL field.
The installer uses this URL to access the internet for downloading container images and other dependencies. The URL must be accessible from the Linux host where you run the installer.
-
If you selected the private registry option in the previous installation options, enter your registry URL in the provided field.
The installer uses this URL to pull container images during installation. The URL must be accessible from the Linux host where you run the installer and from the Kubernetes cluster.
Download the installer archive
Extract the installer archive
Copy installation assets to your home directory
assets/ directory to the home directory on your Linux host.Example:Run the install command
license.yaml file is present alongside all installation assets.Set the Installation Wizard password
Generate the Installation Wizard certificate
30080. The install fails if you decline.Note the Installation Wizard URL
30080. If you haven’t already done so, expose this port on the Linux host.Configure the environment
The Installation Wizard guides you through the final configuration steps to complete the installation. Follow the prompts to enter the necessary information and complete each step.Log in to the Installation Wizard
https://<linux-hostname-or-ip>:30080 because the Installation Wizard uses the self-signed certificate generated during install; this is expected.If your browser blocks the self-signed certificate, export the certificate presented on port 30080, add it to the trusted root/intermediate certificate store as appropriate, then reload the page.Domain Configuration
- For production deployments, this should match the DNS A record you created for the BloodHound Enterprise FQDN in the pre-install checklist.
-
For testing purposes, this can be a hostname that resolves to the Linux host’s IP address in your local
/etc/hostsfile. For example:
Port443must be open on the Linux host and reachable from the browser you use to access the BloodHound Enterprise application.
Application Access
443 with the certificate you configure in the next step.Choose ClusterIP, NodePort, or LoadBalancer only if your environment already requires one of those Kubernetes service exposure patterns or you are integrating with your own frontend networking layer.
Certificates
443.Upload your own certificate if your organization requires a certificate issued by your internal or public certificate authority.
Database Configuration
5432 from the Linux host where BloodHound Enterprise is installed.
Set Up

Run Preflight Checks


Finish

Ctrl+C to exit the installation process and stop the web interface for the wizard.BloodHound Enterprise continues running and is accessible at the FQDN you configured in the Domain Configuration step.Access BloodHound Enterprise
The last step of the installation process is to access the BloodHound Enterprise application in a browser and log in with the default admin credentials.Access BloodHound Enterprise
-
The default username is
admin. Enter the username in the Email Address field. - The default password is written to the BloodHound application logs on the Linux host.
kubectl shell environment and inspect the deployment logs:-
Load the
kubectlshell environment: -
Print the initial admin password from the
bloodhounddeployment’s logs:Targeting the deployment avoids needing to look up the current pod name, which changes between installations and restarts.
Next steps
- Change the default admin password (Administration > Manage Users)
- Create users
- Configure collectors
Troubleshooting
When troubleshooting, you can inspect cluster state and view logs using thekubectl command-line tool.
Load the kubectl shell environment
kubectl shell environment:kubeconfig is exported, and the location of useful binaries like kubectl and Replicated’s preflight and support-bundle plugins is added to PATH.Run common troubleshooting commands
- Pods
- Services
- Logs