- Folding@Home - Use processing power to assist with disease research
- Tor Relay - Add a node to the Tor network
- YaCy - Decentralized open source search engine
- IPFS Node - Contribute to a decentralized internet
How do I run DietPi-Software and install optimised software items?
To install any of the DietPi optimised software items listed below run from the command line:
Choose Browse Software and select one or more items. Finally select
DietPi will do all the necessary steps to install and start these software items.
To see all the DietPi configurations options, review the DietPi Tools section.
Folding@home is a project focused on disease research.
The problems which are solved require so many computer calculations that help from the community is needed to find the cures!
By default, our installation will add you to the DietPi team group, however, you can change this in the web interface at any time.
The web interface is accessible via the port 7396, e.g. this could be:
- URL =
The configuration is located in the file
You can change the configuration with the following steps:
- Stop services with
- Save changes and restart services with
Folding@Home has a logging feature which outputs into the journal logging system. The logs can be viewed via:
journalctl -u fahclient
In addition to the power slider in the web interface the user can influence the number of jobs that run on the system.
The example config given below has 3 job slots, ideal for a 6 core CPU (allowing 2 CPU cores per job slot):
<config> <!-- Slot Control --> <power v='FULL'/> <!-- User Information --> <user v='Fourdee'/> <!-- Folding Slots --> <slot id='0' type='CPU'/> <slot id='1' type='CPU'/> <slot id='2' type='CPU'/> </config>
Contribute a node to the Tor network, which allows people to be anonymous on the internet.
You can run many types of relay, each with their own technical requirements and legal implications.
Bridges are the safest relay to run from home, and are relatively easy, low-risk and low bandwidth, but they have a big impact on users, especially in censored countries. Normally, IP addresses and other information of Tor relays is published, making it easy for websites to blacklist the relay, and anything else using that IP address. Since a bridge isn’t listed publicly, it is unlikely to be blocked by websites or receive abuse complaints.
Guard/Middle relays are the first and second relays connected to, respectively. Information about them is listed, but they are unlikely to receive abuse complaints. However, they may be blocked by certain services that don’t understand how Tor works or deliberately want to censor Tor users. If you have one static IP address, consider running a bridge instead.
Exit relays are the final relay connected to, and the one that actually sends traffic to its destination. The website will see the exit relay’s IP address instead of the real IP address of the Tor user. Exit relays have the greatest legal exposure and liability of all the relays, and should not be run from home.
Exit relay preparation
Running exit relays requires some preparation. Before running an exit relay, you should set a reverse DNS (and, if possible, WHOIS) record to make it clearer that your IP address is a Tor exit relay. Also, it is recommended that you run an exit relay on its own server, with its own IP address.
The simplest way to monitor the Tor relay is to use the DietPi-CloudShell scene, for this run
dietpi-cloudshell from the command line and select the “Tor Relay” scene. It uses the Tor monitor nyx which can be called in standalone mode by executing
nyx from command line.
You can also monitor it with the Tor relay search. Just paste either the fingerprint (found at
/var/lib/tor/fingerprint) or nickname of your relay.
Note for bridge operators
The Tor relay search will not always work for bridges, sometimes showing them as down when they are running. In that case, use the specific Tor bridge monitoring URL:
Keeping Tor relays updated is important to the safety of both the users and the operator. Because of this, automated upgrades are recommended and asked about when first installing. Otherwise, regularly run the following commands to keep your system packages up-to-date:
apt update apt upgrade
Official documentation: https://community.torproject.org/relay/setup
YaCy is a decentralized open source search engine.
Essentially, it is a “peer-to-peer” Google search engine, not controlled by Google.
The web interface is accessible via port 8090:
- URL =
Set password with:
Login details are then:
- Username =
- Password =
YaCy is extremely CPU intensive, coupled with constant background processing, we highly recommend using
dietpi-services to reduce process priority.
Recommended setting: Nice = 19
IPFS (InterPlanetary File System) is a peer-to-peer hypermedia protocol designed to make the web faster, safer, and more open. This node lets you download files through IPFS and add your own files to the network.
The web interface is accessible via port 5003, and the gateway through 8087:
- WebUI =
- Gateway =
You can use your IPFS node with the IPFS Companion browser extension to automatically download IPFS-hosted files through your node. In the settings page of the extension, change “IPFS API URL” to
http://<your.IP>:5003, and “Local Gateway” to
Chromium and derivatives: https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch
Note for using with extension
IPFS content will not load on
https:// pages without an SSL certificate. We recommend a free one from LetsEncrypt using DietPi-LetsEncrypt.
You can view the service logs via
journalctl -u ipfs
You can update your IPFS node by running
dietpi-software reinstall 186
IPFS has a built in update command (
ipfs update), but this requires the
ipfs-update binary found at https://dist.ipfs.io/#ipfs-update.
Official documentation: https://docs.ipfs.io
Do not expose to internet
The IPFS web interface requires no authentication to use. Do not expose it to the internet without taking proper security measures, like an authenticated reverse proxy, VPN or similar.