Portainer Templates logo

Portainer Templates

Pritunl Pritunl

Stack

VPNToolsOtherWeb

Pritunl container built on Alpine Linux. Supports IPv6 and running behind a reverse proxy. This container requires an external Mongo DB and should be run via Docker Compose or other orchestration.

Configuration

Type
Compose
Platform
linux
Env vars
REVERSE_PROXY=falsePRITUNL_OPTS=''MONGODB_URI=mongodb://mongo:27017/pritunlWIREGUARD=false
Source
Repo

Template by SelfhostedPro·Source

Notes

Documentation on this containier can be found here: https://hub.docker.com/r/goofball222/pritunl

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Pritunl, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Required settings are blank

PRITUNL_OPTS has no default value, and pritunl may crash or misbehave if left empty.

  • Fill it in on the deploy screen before hitting deploy.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Pritunl is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Pritunl takes 4 of them, and one needs a value before it'll start properly:

  • REVERSE_PROXY, defaults to false
  • PRITUNL_OPTS, needs a value
  • MONGODB_URI, defaults to mongodb://mongo:27017/pritunl
  • WIREGUARD, defaults to false

Networking

Nothing custom is set, so Pritunl sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container pritunl. That's what you'll spot in the containers list and use in commands like docker logs pritunl.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Pritunl up. Add the template list to Portainer once, then deploying Pritunl is a click rather than a wall of config.