Articles in this section

Resolving HTTPS Issues in Bold Reports Docker After Changing the Application URL from HTTP to HTTPS Behind a Reverse Proxy

Published:
Updated:

Problem

After changing the Bold Reports application URL from HTTP to HTTPS, users may experience issues such as:

  • Mixed HTTP and HTTPS requests.
  • Unexpected redirects.
  • Login or authentication issues.
  • Report Viewer or Report Designer loading failures.
  • Internal service communication errors.
  • Browser security warnings related to insecure content.

This behavior is commonly observed when Bold Reports is deployed using Docker behind a reverse proxy that terminates SSL traffic.

Cause

When SSL is terminated at the reverse proxy level, Docker containers receive requests through HTTP unless the reverse proxy information is explicitly forwarded to the Bold Reports services.

Without proper reverse proxy configuration, the application may incorrectly identify incoming requests as HTTP instead of HTTPS, resulting in protocol mismatches during internal and external communications.

Solution

Configure the BOLD_SERVICES_REVERSE_PROXY environment variable in your Docker deployment.

Example

BOLD_SERVICES_REVERSE_PROXY=true

This allows Bold Reports services to respect the protocol information forwarded by the reverse proxy and correctly generate HTTPS URLs during application interactions.

Steps

  1. Open your Docker deployment configuration.

  2. Add or update the following environment variable:

    BOLD_SERVICES_REVERSE_PROXY=true
    
  3. Save the changes.

  4. Restart the Docker containers.

  5. Verify that the application URL is accessible through HTTPS and all application components function correctly.

Reference

For more information about Docker environment variables, refer to the official documentation:

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

Conclusion

If issues occur after changing the Bold Reports site URL from HTTP to HTTPS, verify that the reverse proxy configuration is correctly communicated to the Docker deployment by enabling BOLD_SERVICES_REVERSE_PROXY.

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied