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. Listen to his story.

Moderated and Vetted

Moderators ensure that apps listed in the store offer a safe, compatible, and consistent experience. Learn more about our guidelines.


NoIp's Icon

No-Ip is a dynamic DNS service, with a free tier supporting up to three domain names. Unfortunately, those domain names have to be renewed periodically. This container implements the new noip2 protocol, which uses a noip client provided by no-ip.com.

ntp's Icon

This container runs chrony on Alpine Linux. chrony is a versatile implementation of the Network Time Protocol (NTP). It can synchronise the system clock with NTP servers, reference clocks (e.g. GPS receiver), and manual input using wristwatch and keyboard. It can also operate as an NTPv4 (RFC 5905) server and peer to provide a time service to other computers in the network.

Nyuu's Icon

Nyuu(https://github.com/animetosho/Nyuu) is a command-line binary usenet poster. It's designed primarily to be fast/efficient, reliable and customizable, exposing all the interesting bits and pieces. From what I’ve seen, Nyuu excels more than any other usenet posting client in these aspects. Includes patches to fix the yenc header filename obfuscation with a new --obfuscate-articles setting (credits for anon for the original fix). Note: No WebUI is available for Nyuu, so Console usage is a must. See quick start guide in Support Thread.

OAuth2-Proxy's Icon

A reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. Please visit support thread for install / setup instructions

obfs4-bridge's Icon

obfs4-bridge

Network ServicesOther

obfs4-bridge is a container that allows you to run a Tor Bridge relay to help censored users connect to the Tor network. Configuration: - OR_PORT: Your bridge's onion routing (Tor) port. - PT_PORT: Your bridge's obfs4 port. - EMAIL: Your email address. Note: - Make sure that both ports are forwarded in your firewall. - Make sure that you create the DATA_DIR and change its owner before running the container: mkdir /mnt/user/appdata/tor && chown 101:101 /mnt/user/appdata/tor.

observium's Icon

Observium is an autodiscovering network monitoring platform supporting a wide range of hardware platforms and operating systems. Directions: /config : this path is where Observium will store its PHP config file and the database which contains data for users, devices, and data. /opt/observium/logs : this path is where Observium will store its logs. /opt/observium/rrd : this path is where Observium will store its Round-Robin Database (RRD) data.

ollama-webui's Icon

ChatGPT-Style Web Interface for Ollama IMPORTANT: Make sure to add the following environment variable to your ollama container - OLLAMA_ORIGINS=* Set your OpenAI API key (not persistant) - OPENAI_API_KEY

ombi's Icon

Ombi(https://ombi.io) allows you to host your own Plex Request and user management system. If you are sharing your Plex server with other users, allow them to request new content using an easy to manage interface! Manage all your requests for Movies and TV with ease, leave notes for the user and get notification when a user requests something. Allow your users to post issues against their requests so you know there is a problem with the audio etc. Even automatically send them weekly newsletters of new content that has been added to your Plex server!

OpenConnectServer's Icon

OpenConnect server is an SSL VPN server. Its purpose is to be a secure, small, fast and configurable VPN server. It implements the OpenConnect SSL VPN protocol, and has also (currently experimental) compatibility with clients using the AnyConnect SSL VPN protocol. The OpenConnect protocol provides a dual TCP/UDP VPN channel, and uses the standard IETF security protocols to secure it. This container is an automated build linked to alpine. The dockerfile was written to always download and compile the latest release of OpenConnect VPN server when built.

openldap's Icon

A docker image to run OpenLDAP, The container default log level is info. Available levels are: none, error, warning, info, debug and trace. To use this container with phpldapadmin, create a custom network that both containers are on and then link them using --link openldap:PHPLDAPADMIN_LDAP_HOSTS in the extra parameters of the phpldapadmin docker container (which should be equal to HOSTNAME in this container). Any other docker that wants to use LDAP credentials will need the same extra parameter including Let's Encrypt if you are using linuxserver.io's ldap-auth container.

openobserve's Icon

a simple yet sophisticated log search, infrastructure monitoring, and APM solution. It is a full-fledged observability platform that can reduce your storage costs by ~140x compared to other solutions and requires much lower resource utilization resulting in much lower cost.

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

OpenVPN-HyDeSa's Icon

OpenVPN Client with integrated (NZB)Hydra2-Deluge-Sabnzbd (and HTTP + SOCKS5 proxies). Now with a Web GUI quick launch. High-level instructions: (1) Create an appdata folder in host and create a openvpn subfolder. (2) Copy your OpenVPN configuration to the above openvpn subfolder (must include openvpn.ovpn + credentials + certs). (3) Don't forget to map /data in the docker to the host (you can map the parent or individual subfolders depending on needs). (4) Start docker (other apps should configure themselves on first run). DON'T FORGET THE OVPN FILE!!! Default password for deluge is deluge 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-hydesa).

OpenVPN-HyRoSa's Icon

OpenVPN Client with integrated (NZB)Hydra2-RTorrent (Flood GUI)-Sabnzbd (and HTTP + SOCKS5 proxies). Now with a Web GUI quick launch. High-level instructions: (1) Create an appdata folder in host and create a openvpn subfolder. (2) Copy your OpenVPN configuration to the above openvpn subfolder (must include openvpn.ovpn + credentials + certs). (3) Don't forget to map /data in the docker to the host (you can map the parent or individual subfolders depending on needs). (4) Start docker (other apps should configure themselves on first run). DON'T FORGET THE OVPN FILE!!! Default login to flood is admin/flood 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-hyrosa).

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.