Overcast is alpha — behaviour and APIs may change between releases. Pin your version and read the changelog before upgrading.

overcast

HTTPS and the trust store

overcast https enable sets up browser-trusted TLS in one command; overcast trust manages the Overcast CA in the system trust store on its own.

overcast https enable is the one command most people run: it creates the local Overcast CA, installs it into the system trust store, and mints the server certificate. overcast trust exposes the trust-store half on its own.

overcast https enable            # once per machine
OVERCAST_TLS=auto overcast serve # HTTPS + HTTP/2 on both listeners

Part of the CLI reference. The full guide, including the Docker and WSL routes, is HTTPS and HTTP/2.

overcast https enable|disable|status

overcast https enable
overcast https status
overcast https disable

With --endpoint, enable fetches the CA from a running daemon instead of minting one — the Docker route, where the container owns the CA. Installing a CA fetched from a non-loopback endpoint additionally needs --trust-remote, an explicit acknowledgement that the remote host could then impersonate any TLS site to this machine.

overcast trust install|uninstall|status

Lower-level management of the Overcast CA in the system trust store, which https enable/disable build on. Reach for it when scripting the pieces separately.

overcast trust install
overcast trust status
overcast trust uninstall

install takes the same --endpoint and --trust-remote pair as https enable, and for the same reason.