Website activation

The platform automatically activates product websites once all requirements are met.

Activation requirements

A website activates when ALL of these are true:

• ✅ Customer is active
• ✅ Subscription is Active or Trial
• ✅ Domain is verified (A record resolves)
• ✅ Provisioning is completed
• ✅ Product is active
• ✅ Gateway is enabled
• ✅ Maintenance mode is off

Activation states

State	Description	Action
Ready	All requirements met, not yet activated	Click “Activate”
Activating	Activation in progress	Wait
Active	Website live with HTTPS	Monitor
Activation Failed	Activation error	View error, click “Retry”
Suspended	Manually suspended	Reactivate

Activation process

When you click “Activate” (or automatic activation runs):

1. Generate Caddy config - Reverse proxy to product port
2. Validate config - Caddyfile syntax check
3. Reload Caddy - Apply new configuration
4. Verify HTTPS - HTTP → HTTPS redirect + 200 OK
5. Update status - Mark Active, record timestamp

Automatic activation

Enable in Platform Settings → Gateway Activation:

• Enable Automatic Activation - Auto-activate Ready websites
• Retry interval - Minutes between retries (default: 60)
• Max retries - Maximum retry attempts (default: 5)
• Health timeout - HTTPS verification timeout (default: 30s)

Manual activation

From the Website Status page:

1. Find website in “Ready” state
2. Click “Activate”
3. Monitor progress in real-time
4. Check HTTPS verification result

Retry logic

If activation fails:

1. Error recorded with step + message
2. Status → “Activation Failed”
3. Scheduled for retry (per interval)
4. Max retries reached → Manual intervention

SSL provisioning

During activation:

1. Let’s Encrypt certificate requested
2. HTTP-01 challenge via Caddy
3. Certificate stored in Caddy config
4. Auto-renewal 30 days before expiry

Troubleshooting

Activation fails

• Check Caddy logs in Gateway Execution
• Verify domain DNS resolves to platform IP
• Ensure product port is correct
• Check maintenance mode is off

HTTPS verification fails

• Firewall blocking port 443
• Caddy rate limited by Let’s Encrypt
• DNS not fully propagated
• Conflicting Caddy configs

Website shows “Not Secure”

• Force Caddy reload: click “Reactivate”
• Check certificate expiry in browser
• Verify CAA record allows Let’s Encrypt