HTTPS SNI Gateway & Managed TLS
Publishing HTTP/TLS applications with managed certificates under <vm>.msrv.space subdomains.
Publishing web services
Every VM provisioned in microsrv automatically reserves a dedicated public hostname:
https://<vm-name>.msrv.space
How inbound routing works
- Start your HTTP server or API binary on any internal port (e.g.,
80,8080, or3000). - The HTTPS gateway accepts external requests to
<vm-name>.msrv.spaceand forwards them to the application port on the VM.
Verification Example:
microsrv:~$ curl -I https://demo-web.msrv.space
HTTP/2 200
server: microsrv-ingress/1.4
content-type: text/html[!TIP] TLS certificate issuance and renewal are fully automated at the gateway level—no ACPI scripts or
certbotdaemons are needed inside guest OS images.