MyOwnPKI documentation Source on GitHub

Try the demo

The demo is a complete, disposable instance that you can start with Docker to see MyOwnPKI work before you install anything. It is not for production: the instance is marked as a demo (the web UI says so in a banner and the log says so at every start), and every one of its secrets is in one file. When you are done, one command removes everything.

What it does

The names www.demo.test and web.demo.test exist only inside the network that Docker creates for the demo. Only the web UI is published, on 127.0.0.1:9443 of the host, with a self-signed certificate.

What you need

Run it

The demo lives in deploy/demo of the repository. Take the files of the release you want to try:

git clone --depth 1 --branch "v0.9.0" https://github.com/Der-Felix/MyOwnPKI.git
cd MyOwnPKI/deploy/demo
./demo.sh run

run starts the server, unseals it, creates the domain, runs certbot and checks the result. Each of these steps (up, unseal, domain, certbot, verify) can also be run alone; the table in deploy/demo/README.md says what each does and what to look at in the web UI afterwards.

The image tag in docker-compose.yml is the release the files belong to. To try a snapshot or an image you built yourself, copy .env.example to .env and set MYOWNPKI_IMAGE in it.

Look at it in the browser

Open https://127.0.0.1:9443/. The browser warns about the certificate, which is self-signed; for a demo on your own machine you can accept it. Sign in with the demo admin, whose password and TOTP secret are in the secrets file. The scripts never print them, so copy the file out on purpose:

docker compose -f docker-compose.yml cp myownpki:/var/lib/myownpki/init-demo-secrets.txt "$HOME/init-demo-secrets.txt"

Add the TOTP secret to an authenticator app; its first code confirms it. Keep the copy outside the repository, never post it anywhere, and delete it when you are done.

Note: A script reads the unseal passphrase from a file only because this is a demo instance. The server itself never does that: a real instance is unsealed by a person. Do not copy the pattern.

The second act

It needs the first act: the agent trusts the root that certbot fetched.

./demo.sh agent

The script creates an agent CA (an intermediate that may sign client certificates only), restarts the server with the agent listener, unseals it again and starts web: nginx with myownpki-agent, taken from the release’s own package and checked against its checksums.txt. The agent enrolls as web.demo.test. One click is left: Agents → Enrollment requests, Approve web.demo.test. The agent then gets its certificate, orders one for web.demo.test by http-01, deploys it and reloads nginx. Watch it in Agents and with ./demo.sh logs. The second act is not checked by CI.

Clean up

./demo.sh down

removes the containers, the network and all demo volumes: the CA keys, the secrets file and the certificates. docker volume ls should then show no myownpki-demo_* volume.

If something fails

When you have seen enough, install it for real, or read how the first certificate in the web UI goes.