Custom Domains & SSL

Every site you create in Blaze gets a custom .local domain with HTTPS enabled automatically. No manual certificate management or configuration needed.

How It Works

When you create a site named “myproject”, Blaze:

1. Adds myproject.local to your /etc/hosts file (pointing to 127.0.0.1)
2. Generates a trusted SSL certificate using mkcert
3. Configures Nginx to serve the site on https://myproject.local

Your browser will show a valid HTTPS connection with no security warnings.

Privileged Helper

Custom domains on port 80 require a privileged helper service. Blaze asks for your password during first-time setup to install this. The helper:

• Allows Nginx to bind to port 80 (normally restricted to root)
• Manages /etc/hosts entries for your .local domains

The helper is installed once during initial setup and runs in the background.

Regenerating an SSL Certificate

Occasionally a site’s mkcert certificate can end up missing or out of sync — for example, if the certificate was deleted, if a Pull provisioned a linked local before the certificate finished generating, or if the bundled mkcert binary couldn’t run during setup.

When that happens, the site responds with a 502 over HTTPS (HTTP usually still works) because Nginx falls through to the wrong :443 server block.

To recover without re-creating the site:

1. Open the site from the sidebar
2. Go to the Overview tab
3. On the Site Domain row, click Regenerate SSL
4. Blaze removes the existing certificate, mints a fresh one with mkcert, and — if the site is running — cycles stop → start so Nginx picks up the new certificate paths
5. A confirmation alert appears when finished

Reload the page in your browser if it was open during the regeneration.