Where Does Pritunl Store Config and Data?
Pritunl stores everything in MongoDB, with the connection URI in /etc/pritunl.conf and host ID in /var/lib/pritunl.
Last updated
Pritunl keeps almost nothing in files. Users, servers, routes, and keys all live in MongoDB. The two local files that matter are /etc/pritunl.conf (the Mongo URI and ports) and /var/lib/pritunl/pritunl.uuid (this host cluster identity).
The uuid file deserves respect far above its size. Changing it makes the host rejoin as a stranger while the old entry lingers for manual deletion. Setup keys in the same directory are single use bootstrap material with no backup value.
Where Pritunl stores this, by platform
/etc/pritunl.conf
Mongo URI plus ports and setup state. Manage it with pritunl set commands or the setup web flow, not bare edits mid run.
/var/lib/pritunl/pritunl.uuid
Cluster host identity plus setup key. Losing the uuid orphans the host entry. Back up alongside database dumps, never alone.
Frequently asked questions
How do I back up Pritunl?
Dump the pritunl database with mongodump and archive it. Config files alone restore nothing, since users, servers, and keys all live in Mongo.
I lost pritunl.uuid. How do I recover the host?
Retrieve the old ID from the console (shift click the red host label) or accept a new host entry and delete the stale one. Never hand edit the uuid file.
Which paths persist in Docker?
Mount all three paths: the conf file, the lib dir, and the mongo data dir. Remote Mongo setups drop the third mount and set the URI variable instead.
Notice an outdated path? Let us know.