Internal Server Error: No Secrets Match ORG_NAME in Self-Hosted Deployments

Last updated: January 27, 2026

Applicable To

Plans: Enterprise

Deployments: Hybrid

Use case: Self-hosted deployments with Terraform-managed configurations

Summary

When accessing projects or resources in a self-hosted Braintrust deployment, you encounter an Internal Server Error with the message No secrets match ORG_NAME. This error occurs when the organization name in your Terraform configuration doesn't exactly match the organization name configured in the Braintrust UI. The resolution requires updating your Terraform configuration with the correct organization name and applying the changes.

Resolution Steps

Step 1: Retrieve your exact organization name

Log into your Braintrust UI and navigate to organization settings. Note the exact organization name, including capitalization and special characters. Organization names are case-sensitive and must match character-for-character.

Step 2: Compare with your Terraform configuration

Open your Terraform configuration files and locate where the organization name is defined. Compare this value with the organization name from Step 1.

# Check current configuration
terraform output -raw braintrust_org_name

Step 3: Update the Terraform configuration

If the names don't match exactly, update your Terraform configuration to use the correct organization name:

variable "braintrust_org_name" {
  description = "Organization name - must match exactly as shown in Braintrust UI"
  type        = string
  default     = "YourExactOrgName"  # Update this to match UI exactly
}

Step 4: Apply the Terraform changes

Run your Terraform workflow to apply the updated configuration:

terraform plan   # Review the changes
terraform apply  # Apply the configuration

Step 5: Verify the fix

After the Terraform apply completes, test accessing your projects and resources in the Braintrust UI. The internal server error should be resolved.

Additional Notes

  • Data Safety: This operation only updates environment variables in Lambda functions. Your data in Postgres and Brainstore remains completely safe.

  • Propagation Time: Allow a few minutes for the new configuration to propagate through all services before testing.

  • Common Issues: Watch for trailing/leading spaces, incorrect capitalization, or character substitutions in organization names.

Helpful links