DNS Setup (Azure)
The DNS Setup step configures domain name routing and enables secure HTTPS access for the Hivel platform.
By default, the Hivel UI container serves unencrypted traffic over HTTP on port 3000. However, modern web browsers enforce strict security boundaries and disable essential Web Crypto APIs (such as crypto.randomUUID, used for user authentication and onboarding flows) unless the application is accessed over a secure context (HTTPS or localhost). Accessing the UI directly via an IP address over HTTP will cause these browser APIs to fail, breaking core application features.
Configuring DNS maps your custom domain (e.g., hivel.yourcompany.com) to your deployment VM. This allows a reverse proxy (such as Caddy) to terminate TLS, manage automatic SSL certificate issuance, and safely route encrypted HTTPS traffic to the UI.
This page walks through enabling HTTPS for the Hivel UI using a Caddy reverse proxy - pick the setup path that matches whether you have a domain yet, Use the list below to understand the documentation structure or jump directly to any page as you work through the guide.
Why HTTPS is needed and what must be ready on VM before choosing an option.
Point DNS at VM, open ports 80/443, and let Caddy auto-issue a trusted certificate.
Temporary self-signed HTTPS for testing before a domain is ready - not for production.
Switching to a real domain later, plus day-to-day Caddy container commands (logs, restart, stop).
Fixes for certificate issuance failures, connection refused on 443, and blank page/502 errors.
Ports, certificate source, config file path, and data volume at a glance.
Last updated