Getting Started


If you bought a pre-assembled upribox from our online store you do not have to read this guide since everything is already set up and you only have to complete the simple tasks described in the enclosed manual.

In a few easy steps you can build your own upribox and won’t get bothered anymore by annoying ads and trackers (see Silent Mode). Additionally you can use your upribox to surf the web anonymously via Tor (see Ninja Mode) and set it up to be your OpenVPN server which secures your connection in unprotected WiFis and lets you benefit from the ad-blocking features on the road (see VPN Server).


You can download the latest upribox image from Github and verify its integrity and authenticity with the provided signature file and PGP key (see Signed Releases). See the official Raspberry Pi documentation for pointers on how to install the upribox image on the SD card. Upon the first boot the SSH/VPN keys are automatically re-generated (this will take a couple of minutes).

Hardware requirements

In the following you will find a list of required (and tested) hardware for the upribox software. On the Raspberry Pi 2 make sure that you use a compatible USB WiFi dongle!

User manual

Web Interface

Once you are connected to either of the upribox WiFi networks (Silent or Ninja) you can access the upribox web interface via the following URI: <>. (see Modes)

Default passwords

If you used the latest community upribox image for setting up your own privacy box you need the following passwords for accessing it:

Login User Default Password
Wifi (SSID: upribox)
Web Interface / SSH upri changethedefaults!

It is important that you change the passwords upon the first login in the admin section of the web interface. New passwords have to be at least 8 characters long containing lower-case, upper-case, numbers and special characters.

The upribox performs an auto-update every four hours. This includes:

  • Blocking rules for privoxy and DNS
  • Software updates via ansible + updates from github

Please note that this process overwrites manual changes to configuration files. To conduct persistent manual changes you have to use custom facts (see Customization).