Community Apps

Browse our large and growing catalog of applications to run in your Unraid server. 

Download the Plugin  |  Become a Community Developer


Community-built

All the applications you love—built and maintained by a community member who understands what you need on Unraid. Love a particular app or plugin? Donate directly to the developer to support their work.

Created by a Legend

Andrew (aka Squid) has worked tirelessly to build and enhance the experience of Community Apps for users like you.

Moderated and Vetted

Moderators ensure that apps listed in the store offer a safe, compatible, and consistent experience. 


OpenRA's Icon

Mudislanders Template for mounting OpenRA's dedicated server by rmoriz OpenRA is a project that recreates and modernizes the classic Command & Conquer real time strategy games. We have developed a flexible open source game engine (the OpenRA engine) that provides a common platform for rebuilding and reimagining classic 2D and 2.5D RTS games (the OpenRA mods).

OpenVPN-AIO-Client's Icon

OpenVPN-AIO-Client

Network ServicesWeb, Other, Security

An "all-in-one" docker for all your private browsing needs (including OpenVPN client with nftables kill switch ; Socks5 + HTTP proxy to both VPN and TOR (the onion router) ; DNS server to DoT (DNS-over-TLS) services). NOTE: you must place your own OpenVPN configuration to the host path that is mapped to /etc/openvpn (The ovpn file must be named openvpn.ovpn. Credentials + certs can be in the same file or split out into multiple files - the flexibility is yours.) Set DNS_SERVERS to 127.2.2.2 to use DNS-over-TLS (use google and cloudflare services by default). Your DNS query out of the VPN exit will also be encrypted for even more security. Set it to other services IP's will use normal unencrypted services. Set HOST_NETWORK to your Unraid server network in CIDR format e.g. 192.168.1.0/24. For more detailed instructions, refer to the support thread (https://forums.unraid.net/topic/96233-support-testdasi-repo/) or project page (https://github.com/testdasi/openvpn-client-aio).

OpenVPN-AIO-Client-Torless's Icon

OpenVPN-AIO-Client-Torless

Network ServicesWeb, Other, Security

An "all-in-one" docker for all your private browsing needs (including OpenVPN client with nftables kill switch ; Socks5 + HTTP proxy to the VPN ; DNS server to DoT (DNS-over-TLS) services). It's the same as OpenVPN AIO Client docker but without TOR. NOTE: you must place your own OpenVPN configuration to the host path that is mapped to /etc/openvpn (The ovpn file must be named openvpn.ovpn. Credentials + certs can be in the same file or split out into multiple files - the flexibility is yours.) Set DNS_SERVERS to 127.2.2.2 to use DNS-over-TLS (use google and cloudflare services by default). Your DNS query out of the VPN exit will also be encrypted for even more security. Set it to other services IP's will use normal unencrypted services. Set HOST_NETWORK to your Unraid server network in CIDR format e.g. 192.168.1.0/24. For more detailed instructions, refer to the support thread (https://forums.unraid.net/topic/96233-support-testdasi-repo/) or project page (https://github.com/testdasi/openvpn-client-aio).

OpenVPN-Client's Icon

OpenVPN-Client

Network Services

This OpenVPN container was designed to be started first to provide a connection to other containers (using '--net=container:OpenVPN-Client'), see the documentation for further help here: https://github.com/ich777/docker-openvpn-client The basic steps for a OpenVPN connection that requires a Username and Password are: 1) Rename your *.ovpn to 'vpn.ovpn' and place it in your OpenVPN-Client directory, 2) Create in the same directory a file named 'vpn.auth' and place your Username in the first line and the Password for the connection in the second line and save it 3) Restart the container open the logs and see if the connection to your VPN establishes successfully. To tunnel traffic from another container through this container edit the template from the other container, set the 'Network Type' to: 'None', enable the advanced view in the top right corner and at 'Extra Parameters' add the following: '--net=container:OpenVPN-Client' (replace 'OpenVPN-Client' with the name of this container if you choose a different name for it) and write down the port(s) that you need to connect to. After that go back to edit this containers template and add the port that you have noted in the above step to this container and click 'Apply' now you can connect to the container that you tunneld the traffic though this container. You can route the traffic from multiple containers through this container with the steps above, if you need more ports then simply add more ports in this containers template. DNS: By default this container uses Googles DNS Server: 8.8.8.8 if you want to edit this turn on 'Advanced View' and edit this setting at 'Extra Parameters'. IPv6: By default IPv6 is disabled in this container. If you want to enable it turn on 'Advanced View' and delete the entry: '--sysctl net.ipv6.conf.all.disable_ipv6=1' from the 'Extra Parameters' or simply set it to: '--sysctl net.ipv6.conf.all.disable_ipv6=0'. ADVANCED CONFIG: If you leave the appdata directory for this container empty it will start up and you have to manually configure it with the builtin comand: 'openvpn.sh', see: https://github.com/ich777/docker-openvpn-client

OpenVPNAccessServer's Icon

OpenVPNAccessServer

Network Services

The username is openvpn You can find the auto-generated password in the docker logs with this command: docker logs -f OpenVPNAccessServer

OrbitalSync's Icon

Orbital Sync synchronizes multiple Pi-hole instances for high availability (HA) using the built-in "teleporter". In other words, it performs a "backup" in the Pi-hole admin interface of your primary Pi-hole instance, and then "restores" that backup to any number of "secondary" Pi-holes also via their admin interface. As a result, it supports the synchronization of anything currently supported by Pi-hole's "teleporter". If you have more than one slave instance you can add extra variables for SECONDARY_HOST_2_BASE_URL: SECONDARY_HOST_2_PASSWORD: SECONDARY_HOST_3_BASE_URL: SECONDARY_HOST_3_PASSWORD: If one or all of your pihole instances use a custom path which isn't '/admin' (ie. you are running them behind a reverse proxy) you can specify a custom path with SECONDARY_HOST_X_PATH variable, where X is the slave numer or PRIMARY_HOST_PATH for the primary. There is no web UI for this app, check the logs to see if it has run successfully.

OVPN_Privoxy's Icon

OVPN_Privoxy

Network Services

openvpn with privoxy in docker with cron after docker start check your config folder, add your *.ovpn file(s) and edit logindata.conf LOCAL_NET - CIDR mask of the local IP addresses which will acess the proxy and bypass it, comma seperated OPENVPN_FILE - full path to ovpn file OVPN_SOCKS - set to off if not wanted OVPN_PRIVOXY - set to off if not wanted ONLINECHECK - set to off if not wanted ONLINECHECK_IP - default 8.8.4.4, change if wanted use privoxy on ip:8118 use socks on ip:1080

ownCloud's Icon

OwnCloud provides universal access to your files via the web, your computer or your mobile devices — wherever you are. Mariadb is built into the image. Built with php 7.2, 7.3, and 7.4 (selectable), mariadb 10.4 and nginx 1.18 Configuration /config - Where ownCloud should store its config files. /data - Where ownCloud should store its data files. Note: Set Network to br0 and assign a static IP address.

ozwdaemon's Icon

Container for running the OpenZWave MQTT Adapter (for Home Assistant via the new Z-Wave Integration) You will need a running MQTT instance and a z-wave controller in order to use this container. For more information see: https://github.com/OpenZWave/qt-openzwave https://www.home-assistant.io/integrations/ozw/ Or visit the unraid forum support thread for more configuration/info

packetstream-psclient's Icon

packetstream-psclient

Network ServicesWeb

Residential Proxies Powered By Peer-To-Peer Bandwidth Sharing.

phpldapadmin's Icon

A docker image to run phpldapadmin. It provides a user interface to an openldap database. It must be on the same custom network as openldap and must be linked via --link openldap:PHPLDAPADMIN_LDAP_HOSTS e.g. --link openldap:example.org An example config.php can be found here: https://github.com/commandprompt/phpldapadmin/blob/master/config/config.php.example

pia-wireguard

Network Services

A Docker container for using WireGuard with PIA. Can output the wiregard conf file to a directory

pictshare's Icon

pictshare

Network ServicesWeb

Host your own images / gifs / mp4s / text / bins and stay in control. Self-hosted imgur/pastebin-like. See https://github.com/HaschekSolutions/pictshare/blob/master/rtfm/DOCKER.md for extra variables that can be added if required.

Pihole-Sync-Sender's Icon

Pihole-Sync-Sender

Network Services

A Docker Container To Sync Two Piholes. This is the Sender/Master, you will need a receiver/secondary on the host who is running the receiver/secondary Pi-Hole. Note: after starting this container the first time please check the log for the public Key.

pipework:1.1.3's Icon

This is the version 1.1.3 of the pipework docker container, the latest container maybe broken so this might work better. Pipework allows you to have a static or dynamic ip for a docker container. This is the Unraid implementation of the dreamcat4 pipework docker container

Pomerium-Proxy's Icon

Pomerium-Proxy beta

Network Services

Pomerium Nginx Proxy - Secure, identity-aware access from anywhere.

Portainer-Agent's Icon

Portainer consists of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine. Portainer uses the Portainer Agent container to communicate with the Portainer Server instance and provide access to the node's resources.

Portainer-BE's Icon

Portainer Business Edition is a fully featured service delivery platform for containerized applications that can be used to manage single and multi-cluster Docker, Swarm, Kubernetes and ACI environments. It is designed to be as simple to deploy as it is to use. The application allows you to manage all your orchestrator resources (containers, images, volumes, networks and more) through a ‘smart’ GUI and/or an extensive API. Notes: • If you would like to extend the capabilities of Portainer, getting extra features over containers, networks, volumes and images, you will need to install the Portainer Agent separately. Search for 'Portainer-Agent' in the Community Apps. • This container needs a license to operate, for additional information on obtaining a FREE license visit https://www.portainer.io/pricing/take5

PortainerCE's Icon

Portainer is a lightweight management UI which allows you to easily manage your different Docker environments (Docker hosts or Swarm clusters). Portainer is meant to be as simple to deploy as it is to use. It consists of a single container that can run on any Docker engine (can be deployed as Linux container or a Windows native container, supports other platforms too). Portainer allows you to manage all your Docker resources (containers, images, volumes, networks and more) ! It is compatible with the standalone Docker engine and with Docker Swarm mode.

poste's Icon

FREE version of Poste.io, full mail server solution. POP3, SMTP, IMAP, Spamassassin, WebMail, WebAdmin. INITIAL SETUP: 0. Requires registered FQDN to send/receive external email. 1. Following ports are used by container for mail: 25, 110, 143, 443, 465, 587, 993, 995 2. Following ports are used by container for webui: 443, 8280 (These may conflict, check your ports) 3. Make a user share for mail data, default is /mnt/user/poste 4. Some or all mail ports may need to be opened, forwarded, or dmz for mail send/receive to work. Optional arguments -e "HTTPS=OFF" To disable all redirects to encrypted HTTP, its useful when you are using some kind of reverse proxy (place this argument before image name!) NOTE: Marked as BETA, simply because author is not an expert in email exchange servers -- software itself looks pretty good.

Postfix-Relay's Icon

Postfix-Relay

Network ServicesOther, Productivity

This runs Postfix (as a relay) in Docker. Most home ISPs block port 25, so outbound emails must be relayed through an external SMTP server (e.g., Gmail). This container acts as a single collections point for devices needing to send email. ⚠️ Postfix acts as an open relay. As such, this is not meant to be run on the internet, only on a trusted internal network! ⚠️ Requirements You must already have a account on an external SMTP server (e.g., Gmail, AWS SES, etc...). Your external SMTP server must be using encryption (i.e., plaintext is not allowed)