Configuring Bold Reports Docker for SSL/TLS Termination Scenarios

Overview

SSL/TLS termination is commonly performed by infrastructure components before requests reach the Bold Reports Docker containers.

Examples include:

• Reverse Proxies
• Load Balancers
• Cloudflare
• Azure Application Gateway
• AWS Application Load Balancer (ALB)
• HAProxy

If Bold Reports is not configured for SSL termination scenarios, the application may not correctly recognize the original HTTPS request context.

Solution

Configure the following environment variable:

BOLD_SERVICES_REVERSE_PROXY=true

How It Works

This setting enables Bold Reports Docker to correctly operate in environments where SSL/TLS termination occurs before requests reach the application.

When enabled, Bold Reports automatically processes the forwarded protocol information and handles X-Forwarded-Proto related behavior internally.

Docker Compose Configuration

environment:
  - BOLD_SERVICES_REVERSE_PROXY=true

Docker Run Configuration

docker run -d   -e BOLD_SERVICES_REVERSE_PROXY=true   boldreports/bold-reports

Benefits

• Prevents protocol mismatch issues
• Avoids redirect loops
• Resolves authentication-related issues
• Prevents mixed-content warnings
• Ensures proper HTTPS URL generation
• Improves compatibility with SSL-terminating infrastructure

Reference

For more information about Docker environment variables, refer to:

https://github.com/boldreports/boldreports-server-in-docker/blob/master/docs/environment-variable.md

Conclusion

For deployments where SSL/TLS termination occurs before requests reach Bold Reports Docker, configure:

BOLD_SERVICES_REVERSE_PROXY=true

This allows Bold Reports to correctly process HTTPS request information and automatically handle X-Forwarded-Proto related behavior.