Environment Variables
Some features of Bitwarden are not configured by the bitwarden.sh installer. Configure these settings by editing the environment file, located at ./bwdata/env/global.override.env. This .env file comes pre-baked with configurable variables (see Included variables), however there are additional variables which can be manually added (see Optional variables).
Whenever you make changes toglobal.override.env, perform a./bitwarden.sh restartto apply your changes.
note
The information in this article may not apply to Bitwarden Lite self-hosted deployments.
The following variables are among those that already exist in global.override.env:
Variable | Description |
|---|---|
| Enter the domain of your Bitwarden instance. If not configured, domain will default to localhost. Must not include a trailing slash. |
| Use this field to connect to an external MSSQL database. |
| A randomly generated OpenID Connect client key. For more information, see OpenID Documentation. |
| A randomly generated Duo akey. For more information, see Duo's Documentation. |
| Client ID for YubiCloud Validation Service or self-hosted Yubico Validation Server. |
| Secret Key for YubiCloud Validation Service or self-hosted Yubico Validation Server. |
| Email address used for invitations, typically |
| Your SMTP server hostname (recommended) or IP address. |
| The SMTP port used by the SMTP server. |
| (Boolean) Whether your SMTP server uses an encryption protocol: |
| A valid username for the |
| A valid password for the |
| Specify |
| Your HaveIBeenPwned (HIBP) API Key, available here. This key allows users to run the Data Breach report and to check their master password for presence in breaches when they create an account. |
| Email addresses which may access the System Administrator Portal. |
The following variables do not already exist in global.override.env, and can be manually added:
Variable |
|---|