Skip to main content

Creating your first administrator account

Open OVERLEAF_SITE_URL followed by /launchpad, for example http://192.0.2.10:30080/launchpad, and register the administrator account as in the Toolkit’s post-installation tasks. Then create an example project and compile it. You can also create users from the command line:
It prints a link that sets the password.

Checking that compiles are sandboxed

Compile a project, then look at the node that runs the pod:
Each compile shows up as a short-lived container named project-<project id>-<user id>-....

Logs and a shell

The container writes one log file per service in /var/log/overleaf/ (web.log, clsi.log, real-time.log, document-updater.log, …); kubectl logs shows the startup output.

What survives a restart

kubectl rollout restart replaces the pods. Only what is on a volume stays. Changes made inside a pod through kubectl exec, such as installed packages or edited files, are lost with it, and so are the logs unless /var/log/overleaf is on a volume, see Logging. Make lasting changes in your manifests.

Q&A

Answer: Check, on the node running the pod, that Docker is running and has the image named in TEX_LIVE_DOCKER_IMAGE, and that SANDBOXED_COMPILES_HOST_DIR_* match the hostPath paths. /var/log/overleaf/clsi.log in the pod names the failing step.
Answer: OVERLEAF_SESSION_SECRET is missing from the Secret overleaf-secrets, see step 2.
Last modified on November 11, 2026