HTTPS is required — Rapid BI Catalog will not start without it. Choose one of two modes: the app terminates TLS itself (Direct HTTPS), or a reverse proxy terminates TLS in front of it (TLS-offload).
Direct HTTPS
The application terminates TLS itself. Before starting the service, place your certificate and private key (in PEM format) on the server at these paths, then set their permissions to 0600:
# place your PEM certificate and private key:
# ~/.bicatalog/ssl-cert.crt (certificate)
# ~/.bicatalog/ssl-key.key (private key)
chmod 600 ~/.bicatalog/ssl-cert.crt ~/.bicatalog/ssl-key.keyThen start (or restart) the service to enable HTTPS on port 3333:
sudo systemctl start bicatalogui.serviceTLS-Offload (Reverse Proxy)
A reverse proxy (nginx, AWS ALB, HAProxy, or Cloudflare) terminates TLS in front of the app. Set the following in ~/.bicatalog/bicatalog.env:
BICATALOG_TLS_OFFLOAD=1Then restart the service to apply the change:
sudo systemctl restart bicatalogui.serviceThe app then serves plain HTTP bound to loopback only (127.0.0.1) and still treats the deployment as HTTPS for all client-facing decisions (Secure cookies, HSTS, and HTTPS CORS origin).
3333 is reachable only through your TLS-terminating proxy.Accessing Rapid BI Catalog Over HTTPS
Once configured and restarted, users reach Rapid BI Catalog at your HTTPS domain (or, for direct HTTPS):
https://<server-host>:3333Next Steps
- Activate your license: Activation
- Outbound connectivity: Egress Allowlist