Browse documentation
Local HTTPS and certificates
Set up localhost and project HTTPS and distinguish trust from website health.
On this page
Local HTTPS and certificates
Open Services → Apache → HTTPS / SSL. The app manages local certificates with mkcert. Project HTTPS can also be selected from project details.
Localhost setup and repair
- Review the HTTPS status and configured port.
- Use the setup or repair action offered by the screen.
- Review any Windows certificate-trust prompt yourself. Trust applies to the local certificate authority, not an internet certificate provider.
- Start or restart Apache as required, then refresh the status and test the displayed HTTPS URL.
A process listening on the HTTPS port, a certificate on disk and a trusted response are different checks. If another service owns the port, resolve that conflict first.
Project hostnames
- Connect the site with its intended hostname and aliases.
- Enable HTTPS in Manage project → Website settings and save.
- Inspect the HTTPS result separately from the website response.
- Open the exact hostname covered by the certificate.
Localhost certificates cover localhost addresses; a project needs coverage for its hostname/aliases. A trusted HTTPS connection can still return HTTP 404 or 500. Check the document root, dependencies, application routes and logs.
Diagnose trust failures
Confirm the hostname, certificate status, system time and whether the local CA was trusted in the environment used by the client. Browser trust policies can differ. Use the app's repair/status workflow and the reported error; do not bypass certificate warnings to declare setup complete.
Changes to site configuration are validated and can fail or roll back. If project details reports configuration that needs review, preserve the saved records and recovery copies before reconnecting or repairing the intended site.
Backup and privacy
Do not publish local CA private keys or certificate private material. Full backups exclude the HTTPS/SSL directories, so restored configuration may require HTTPS provisioning again. The app's local HTTPS does not make DevStackBox a production internet-hosting service.
See Projects, PHP & HTTPS, Full backup and the contributor HTTPS design notes.
Native 1920 × 1032 capture of the v0.1.19 production build, 26 October 2026, using an isolated demonstration profile. Screenshots document the interface; download availability is shown separately on the website.