docs
ProBind a domain with automatic HTTPS
Point the DNS record at your server, type the domain in MihraOps, and the certificate takes care of itself.
Prepare DNS first
Create an A record for your domain pointing at the server IP address, and let it propagate before you continue. The certificate authority has to reach the domain over the public internet to issue a certificate, so a DNS record that is not live yet is the single most common cause of failure here.
Bind the domain
- 01Open the container or application you want to publish.
- 02Add the domain name.
- 03Save. MihraOps writes the reverse proxy configuration and reloads it.
What runs on your server
The proxy is Caddy, running as a container named mihraops-caddy with its configuration in /opt/mihraops/caddy. Caddy requests and renews the TLS certificate on its own — there is no cron job for you to maintain and no renewal date for you to miss.
Ports 80 and 443 must be free on the server and reachable from the internet.
A broken configuration is never applied
The new configuration is validated before it replaces the running one, and the previous version is kept alongside it. If validation or the reload fails, MihraOps restores the previous configuration, so a mistake in one domain cannot take down every other site on the machine.