I updated some Dockers earlier this week and Airconnect seems to be broken - here's the log file:

AirConnect-AIRUPNP] AIRUPNP_VAR is present, launching with custom launch variables: -x /config/config.xml

/usr/bin/airupnp-docker: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

[AirConnect-AIRUPNP] Launching AIRUPNP ...

[AirConnect-AIRUPNP] AIRUPNP_VAR is present, launching with custom launch variables: -x /config/config.xml

Any ideas how to fix?

On 10/11/2025 at 10:00 PM, JT-DFW said:

I updated some Dockers earlier this week and Airconnect seems to be broken.

Any ideas how to fix?

I came here also looking for the answer. In the mean time, rolling back will fix it:

Edit the docker repository from 1activegeek/airconnect:latest to 1activegeek/airconnect:1.8.3

Here's how to fix - FYI - open a console window under the Airconnect docker and type:

apt-get update

apt-get install -y libatomic1

This installs the missing library

I had to do this for 2 or 3 releases in recent weeks but I think the latest Airconnect has this fixed because I didn't have to do the above

6 hours ago, JT-DFW said:

I had to do this for 2 or 3 releases in recent weeks but I think the latest Airconnect has this fixed because I didn't have to do the above

That's the problem with manual intervention. When the docker recreates, it will be lost. You could probably take advantage of the linuxserver.io base to installed that for you. I had to do that once to customize something.

Regardless, I don't know what the benefits of 1.9.x are, but I'm happy to wait for the repo fix. I'm pretty sure it was the latest as it updates every Friday, and I found it dead on Saturday still requiring libatomic.

tried installing Navidrome docker, and it is asking for a user password, but admin/admin and other variants are not working... how do I log in for the 1st time... according to the Navidrome docs it should ask me to MAKE an admin account, but I have a login prompt?

Backblaze_Personal_Backup Web UI after a fresh install displays an error "bzinst: Backblaze has detected that this is an unsupported operating system ..."

I apologize is this is the wrong place/way to post. Please correct me if I am wrong. Let me know where I should post this, if you would.

I previously had this working for a long time with a much earlier version, but I started having problems with backups not running, so I removed the container and image, deleted the config directory, and used the Unraid Backblaze_Personal_Backup App to install again. I assume this gets me the current version of Backblaze that no longer supports Windows XP, but it seems the WINE version and/or configuration hasn't kept up.

On 10/28/2025 at 8:39 PM, 4WoofGrrrr said:

Backblaze_Personal_Backup Web UI after a fresh install displays an error "bzinst: Backblaze has detected that this is an unsupported operating system ..."

I now know that running BackBlaze in a Docker on a non-Windows, non-MacOS system may be a violation of the Terms of Service and that BackBlaze actively "discourages" this.

Library manager the template is using the wrong repo location or it hasn't been uploaded to Docker hub yet. This is the current repo location ghcr.io/deucebucket/library-manager:latest

Update : https://github.com/deucebucket/library-manager/issues/10 The author of Library manager changed the repo location.

"When I first created the UnRaid template I pointed it at Docker Hub (deucebucket/library-manager) but then we switched to GitHub Container Registry and I updated the template in the repo... but Selfhosters already grabbed the old version before I fixed it.

The correct image URL is:"

ghcr.io/deucebucket/library-manager:latest

Edited December 13, 2025Dec 13 by yaggermr

On 10/27/2025 at 4:01 AM, questionbot said:

tried installing Navidrome docker, and it is asking for a user password, but admin/admin and other variants are not working... how do I log in for the 1st time... according to the Navidrome docs it should ask me to MAKE an admin account, but I have a login prompt?

I am hitting the exact same wall. Anyone got an answer to this?

EDIT: Fixed the issue. Stop the docker, then go into the app data folder and delete the navidrome.db file. Then restart the docker and it'll present you the ability to create an admin account.

Edited December 22, 2025Dec 22 by lutiana

Hello everyone,

Configuring Prometheus, I had to figure out some items. This might or might not be documented elsewhere, but if someone is looking for some extra info with some configs and parameters, I have documented most of my Unraid config, as well as Prometheus setup. This might help others get more out of Unraid.

My Github Repo: https://github.com/HisEvilness/Unraid/tree/main

Can I suggest that the Technitium docker container be updated to add the network port 53443 which is required to use the new clustering feature.

Edited December 31, 2025Dec 31 by DataBitz
Add screenshot

I have a problem with my Backblaze Personal Wine container.

After about an hour the VNC Screen is black.

Backblaze is not uploading anymore. (I see that in the Uplink Stats)

The only thing fixing the black screen is restarting the docker.

The container is up to date.

Unraid Version: 7.2.0

Does anyone have an Idea how to fix that?

It seems the latest versions of cAdvisor are not compatible with Unraid v7.2 and above. I've pinned cAdvisor to v0.49.1 and cAdvisor works. But above this version, cAdvisor does not connect to the docker backend. Is there an alternative to cAdvisor for Unraid 7.2? Or is there a way to get the latest versions of cAdvisor working with Unraid 7.2?

Here is some summary output from ChatGPT on the matter:

How cAdvisor ≥0.53 works

• Modern cAdvisor routes Docker metrics through containerd:

  • Docker itself runs on top of containerd internally.

  • The old Docker stats API (directly via /var/run/docker.sock) is deprecated in cAdvisor ≥0.53.

  • If containerd socket is not accessible → cAdvisor cannot get container metrics at all.

• On Unraid 7.2:

  • Docker uses containerd internally.

  • containerd socket is hidden / in a private namespace.

  • /var/run/docker.sock alone is not enough for cAdvisor v0.53+.

Anyone having issues with Invoice Ninja v5? I'm getting an Execution Error code 403. This started a couple months ago, but I don't use the software often and just didn't deal with it. I can't load logs on it, the log pop up window immediately closes. I'm running the database in mysql 9.5 in another docker. I'm running unraid 7.2.3.

I don't see this version of invoice ninja in the unraid community app store anymore...

Edited January 12Jan 12 by DG1M

On 1/12/2026 at 6:33 AM, DG1M said:

Anyone having issues with Invoice Ninja v5? I'm getting an Execution Error code 403. This started a couple months ago, but I don't use the software often and just didn't deal with it. I can't load logs on it, the log pop up window immediately closes. I'm running the database in mysql 9.5 in another docker. I'm running unraid 7.2.3.

I don't see this version of invoice ninja in the unraid community app store anymore...

I figured out my issue.

Step 1. Stop being an idiot

Step 2. Assign an IP to the docker container that isn't in use by another docker container

On 6/20/2024 at 12:49 PM, trauby3620 said:

 I have been trying to solve the issue on my own and figured out a way to fix it. Not saying it is the easiest or prettiest, but it seems to work (for now). So if anyone is having trouble, here are all the steps to set up a working Overleaf container in Unraid:

1. From the apps-tab in Unraid:
   1.1  Install “Redis” (The default options should work fine)
   
   1.2 Install “MongoDB” (You can also use the default options, but don't forget to set Host Path 1 to your desired appdata location)
   
   1.3 You probably need to add a database in MongoDB. Please refer to another guide for detailed instructions.
    

2. Load the “Overleaf”-template from the apps-tab. Here, some modifications are needed before you can finish the install:
   2.1  All variables need to be edited to start with OVERLEAF_ instead of SHARELATEX_
   The result should look a little something like this:
   
   
   2.2 Optionally, you can add any of the options listed on the official overleaf git-page as variables: https://github.com/overleaf/overleaf/wiki/Configuring-Overleaf (e.g. I added the variables needed for Overleaf to be able to send emails)
   
   2.3 You must add the following path (by clicking on the little blue plus at the bottom of the template), to install texlive in a location that is outside your dockerfile. If you don't do that, 8 GB of data is being installed in your dockerfile, which is not recommended.
   
   
   Also add the following where we can save some commands later, that otherwise you would need to type manually after every restart of your server:
   
   
   Note: You might want to adjust the Host Path to point to your desired location on your array. The entry in “Name” can be whatever you like.
   
   2.4 Also optional, but recommended: free up even more space in your Dockerfile by adding the following path, which tells Overleaf to store the uploaded user data in the directory specified:
   
   
   2.5 Once all of these steps are complete: Apply the changes and finish installing the container. In the docker tab, you should now see the three containers we just installed.
    

3. Create a file named “set_path.sh”  and add the following contents to the file using nano or a text-editor of your choice (I use Notepad++):

   export PATH="/usr/local/texlive/2024/bin/x86_64-linux:$PATH"
   chmod +x /mnt/user/appdata/overleaf/set_path.sh

   Hint: You might need to adjust the year in the first line.
   
   Save the file in the location set by the variable “PATH location” from step 2.3.
    

4. Open the Overleaf WebUI and finish the set-up of Overleaf by creating an admin account like described in the wiki: https://github.com/overleaf/toolkit/blob/master/doc/quick-start-guide.md (replace “localhost” with the IP-adress of your docker installation or the domain you use for it)
   
   Once you finished the setup, everything seems to be working fine. But as soon as you try to compile a document with packages that are not shipped with the standard overleaf-container, you will see a critical error along with messages that certain packages were not found.
    

5. To fix this, we need to install the full texlive-installation, by opening the Overleaf-console and running the following commands:
   
   5.1  Download texlive by typing the following command:

   wget https://mirror.ctan.org/systems/texlive/tlnet/update-tlmgr-latest.sh

   
   5.2 Install all texlive packages (This might take a long time, since over 4,000 packages are being installed):

   tlmgr install scheme-full

   
   5.3 Once the installation is finished, run the following command (most packages might work without it, but I had problems with biblatex):

   tlmgr path add

    

6. Test if everything works:
   
   6.1  Go to your Overleaf-site and refresh the page (log in again if necessary)
   
   6.2 Create/Upload a latex-project which uses different packages like biblatex or microtype
   
   6.3 If the compile works without any critical error, you are done!

 

 

Hope this helps, and you can install and use Overleaf without any problems. If you have any suggestions on how to improve the procedure, feel free to reply and let me (and the others) know.

So I revisited this topic once again yesterday and decided to reinstall everything related to Overleaf from scratch, since I still had some trouble at times...

I changed the procedure a bit, which is now as follows:

0. NEW! Create a custom network for Overleaf:

   0.1 Open the terminal

   0.2 Type the following command (you can change "overleaf" to any name you want):

   docker network create overleaf

1. From the apps-tab in Unraid:

   1.1 Install “Redis” (default options should work fine, but change "Network Type" to "Custom: overleaf")

   

   1.2 Install "MongoDB"

   1. Toggle view to "Advanced view" in the top right corner

   2. Type "--replSet rs0" into the field "Post Arguments"

   3. Change "Network Type" to "Custom: overleaf"

   4. Delete variable "Host Port 1"

   5. Set Host Path 1 to your desired appdata location

      

   6. Apply the changes and start the container

   7. Open the console again and type the following command

      docker exec -it mongo mongosh --eval "rs.initiate()"

   1.3 --skipped/unnecessary--

2. Load the “Overleaf”-template from the apps-tab. Here, quite a few modifications are needed before you can finish the install:

   2.1  Change "Network Type" to "Custom: overleaf"

   2.2 All variables need to be edited to start with OVERLEAF_ instead of SHARELATEX_

   The result should look a little something like this:

   

   2.3 Optionally, you can add any of the options listed on the official overleaf git-page as variables: https://github.com/overleaf/overleaf/wiki/Configuring-Overleaf (e.g. I added the variables needed for Overleaf to be able to send emails)

   2.4 Type "mongodb://mongodb/overleaf" into the OVERLEAF_MONGO_URL field:

   2.5 Add the following path (by clicking on the little blue plus at the bottom of the template), which tells Overleaf to store the uploaded user data in the directory specified in "Host Path":

   

   2.6 You must also add the following path (by clicking on the little blue plus at the bottom of the template), to install Texlive in a location that is outside your dockerfile specified by the entry in "Host Path":

   

   2.7 Once all of these steps are complete:

   1. Apply the changes and finish installing the container

   2. In the docker tab, you should now see the three containers Redis, MongoDB and Overleaf all running on the custom network "overleaf".

3. --skipped/unnecessary--

4. Open the Overleaf WebUI and finish the set-up of Overleaf by creating an admin account like described in the wiki: https://github.com/overleaf/toolkit/blob/master/doc/quick-start-guide.md (replace “localhost” with the IP-adress of your docker installation or the domain you use for it)
   
   Once you finish the setup, everything seems to be working fine. But as soon as you try to compile a document with packages that are not shipped with the standard overleaf-container, you will see a critical error along with messages that certain packages were not found.
    

5. To fix this, we need to install the full Texlive installation by opening the console and running the following commands:
   
   5.1  Type the following command:

   docker exec -it overleaf bash

   5.2 Update tlmgr by running the following command:

   tlmgr update --self

   5.3 Install all Texlive packages by running the following command (NOTE: This will take up to an hour) or more:

   tlmgr install scheme-full

   Alternatively, install only the packages you need using the following guide: https://docs.overleaf.com/on-premises/installation/upgrading-tex-live

   5.4 Run the following command next:

   tlmgr update --all

   5.5 Exit the container:

   exit

   5.6 Copy the data to your desired location to make it permanent:

   docker cp overleaf:/usr/local/texlive /mnt/user/appdata/overleaf/texlive

6. Test if everything works:
   
   6.1  Go to your Overleaf site and refresh the page (you need to log in again)
   
   6.2 Create/upload a LaTeX project that uses different packages like biblatex or microtype. You can use the following example:

   \documentclass{article}
   \usepackage{tikz}
   \begin{document}
   It is working! You just successfully installed Overleaf on Unraid!
   \begin{tikzpicture}
     \draw (0,0) circle (1cm);
   \end{tikzpicture}
   \end{document}

   
   6.3 If the compile works without any critical error, you are done!

 

 

Hope this update helps you install and use Overleaf without any problems. If you have any suggestions on how to further improve the procedure, feel free to reply and let me (and the others) know.

Hi guys, I need support for setting up Technitium using the here mentioned docker template. I found nowwhere info about how installing it. Can anyone briefly let me know how to proceed? You can PM me to not get out the scope of this thread. Once I have everything setup I will write a guide here on the forum on how to proceed. I just found posts for pihole. Then just a few posts about Technitium where people only mentioned where they got stuck and how they solved that issue. Could not find anything outside unraid forum too. Btw do I need to install it using Network_Type=Host? or Custom:br0?

The YouTubeDL Material template installs fine, but I get this when I open the webui. Not really sure what I need to do now.

On 3/9/2026 at 2:48 AM, scottygood said:

To fix this change your docker repository to voc0der/ytdl-material:nightly

The YouTubeDL Material template installs fine, but I get this when I open the webui. Not really sure what I need to do now.

Same issue for me. Reinstalled but same error.

On 3/9/2026 at 2:48 AM, scottygood said:

The YouTubeDL Material template installs fine, but I get this when I open the webui. Not really sure what I need to do now.

On 2/3/2026 at 10:48 AM, trauby3620 said:

So I revisited this topic once again yesterday and decided to reinstall everything related to Overleaf from scratch, since I still had some trouble at times...

I changed the procedure a bit, which is now as follows:

0. NEW! Create a custom network for Overleaf:

   0.1 Open the terminal

   0.2 Type the following command (you can change "overleaf" to any name you want):

   docker network create overleaf

1. From the apps-tab in Unraid:

   1.1 Install “Redis” (default options should work fine, but change "Network Type" to "Custom: overleaf")

   

   1.2 Install "MongoDB"

   1. Toggle view to "Advanced view" in the top right corner

   2. Type "--replSet rs0" into the field "Post Arguments"

   3. Change "Network Type" to "Custom: overleaf"

   4. Delete variable "Host Port 1"

   5. Set Host Path 1 to your desired appdata location

      

   6. Apply the changes and start the container

   7. Open the console again and type the following command

      docker exec -it mongo mongosh --eval "rs.initiate()"

   1.3 --skipped/unnecessary--

2. Load the “Overleaf”-template from the apps-tab. Here, quite a few modifications are needed before you can finish the install:

   2.1  Change "Network Type" to "Custom: overleaf"

   2.2 All variables need to be edited to start with OVERLEAF_ instead of SHARELATEX_

   The result should look a little something like this:

   

   2.3 Optionally, you can add any of the options listed on the official overleaf git-page as variables: https://github.com/overleaf/overleaf/wiki/Configuring-Overleaf (e.g. I added the variables needed for Overleaf to be able to send emails)

   2.4 Type "mongodb://mongodb/overleaf" into the OVERLEAF_MONGO_URL field:

   2.5 Add the following path (by clicking on the little blue plus at the bottom of the template), which tells Overleaf to store the uploaded user data in the directory specified in "Host Path":

   

   2.6 You must also add the following path (by clicking on the little blue plus at the bottom of the template), to install Texlive in a location that is outside your dockerfile specified by the entry in "Host Path":

   

   2.7 Once all of these steps are complete:

   1. Apply the changes and finish installing the container

   2. In the docker tab, you should now see the three containers Redis, MongoDB and Overleaf all running on the custom network "overleaf".

3. --skipped/unnecessary--

4. Open the Overleaf WebUI and finish the set-up of Overleaf by creating an admin account like described in the wiki: https://github.com/overleaf/toolkit/blob/master/doc/quick-start-guide.md (replace “localhost” with the IP-adress of your docker installation or the domain you use for it)
   
   Once you finish the setup, everything seems to be working fine. But as soon as you try to compile a document with packages that are not shipped with the standard overleaf-container, you will see a critical error along with messages that certain packages were not found.
    

5. To fix this, we need to install the full Texlive installation by opening the console and running the following commands:
   
   5.1  Type the following command:

   docker exec -it overleaf bash

   5.2 Update tlmgr by running the following command:

   tlmgr update --self

   5.3 Install all Texlive packages by running the following command (NOTE: This will take up to an hour) or more:

   tlmgr install scheme-full

   Alternatively, install only the packages you need using the following guide: https://docs.overleaf.com/on-premises/installation/upgrading-tex-live

   5.4 Run the following command next:

   tlmgr update --all

   5.5 Exit the container:

   exit

   5.6 Copy the data to your desired location to make it permanent:

   docker cp overleaf:/usr/local/texlive /mnt/user/appdata/overleaf/texlive

6. Test if everything works:
   
   6.1  Go to your Overleaf site and refresh the page (you need to log in again)
   
   6.2 Create/upload a LaTeX project that uses different packages like biblatex or microtype. You can use the following example:

   \documentclass{article}
   \usepackage{tikz}
   \begin{document}
   It is working! You just successfully installed Overleaf on Unraid!
   \begin{tikzpicture}
     \draw (0,0) circle (1cm);
   \end{tikzpicture}
   \end{document}

   
   6.3 If the compile works without any critical error, you are done!

 

 

Hope this update helps you install and use Overleaf without any problems. If you have any suggestions on how to further improve the procedure, feel free to reply and let me (and the others) know.

Just to be clear. If anyone gets the banner on top of the docker edit your docker and change the repository to voc0der/ytdl-material:nightly and this will fix the banner issue.

Anyone set up Forgejo CI Runner? I took a quick scan, looks like you will need to run a new container that will run either podman or docker in it? Anyone made anything that plugs straight into unraid?

https://forgejo.org/docs/latest/admin/actions/runner-installation/ https://dbushell.com/2025/08/15/self-hosted-forgejo-actions-runner/

Why does traccar only allow 5000-5150 it needs up to 5300, per this:

https://www.traccar.org/docker/

and this:

https://www.traccar.org/devices/

Anyone get Autobrr working?

I'm trying to get it to work with Lidarr/Sonarr and qBittorrent.

In Lidarr (for example) it finds the new release, but it never sends it to qBt. I'm not sure why not?

Any help would be greatly appreciated.

On 1/4/2026 at 3:30 PM, Kreuter said:

I have a problem with my Backblaze Personal Wine container.

After about an hour the VNC Screen is black.

Backblaze is not uploading anymore. (I see that in the Uplink Stats)

The only thing fixing the black screen is restarting the docker.

The container is up to date.

Unraid Version: 7.2.0

Does anyone have an Idea how to fix that?

This is (possibly) two problems being encountered independently.

1. Regarding the black screen issue :
   
   In the Backblaze docker settings, instead of the default value of 99 set :-

   
   User ID: 0
   Group ID: 0
   

   Explanation: The Docker container may have insufficient permissions to download and install Backblaze."

   
   Context:

   This is an old problem which several people in this thread (including me) have encountered. I've just lived with for about a year since my backups succed anyway, I just can't see it ;)
   I relooked at the problem recently because of an unrelated issue with my setup, and found that there has been some additional discussion on the Github repo. Github repo page

   This resulted in additional troubleshooting info being added to the Docker Hub page for the project . Docker Hub page

   It worked for me, and now I can see the Backblaze application in the VNC viewer (which allowed me to fix the unrelated issue I mentioned)

   
   

2. Further the to the not uploading part - it may also be kinda-sorta related.
   With later client versions Backblaze have stopped supporting older "legacy" operating systems ... which is a problem for the containerised Wine approach.
   New container installs, or automatic updates within existing ones will fail with an "Operating System Not Supported" message (which you may not currently be absle to see, what with black screen :)
   This can be worked around with some messing about with manually downloading an older, supported, client version from a 3rd party mirror and installing it as per user danvctr's posts on Github.

   Github issue: Backblaze 10 - x64 only
   

   Make sure to set the docker option of:
   Force Latest Update: false

Edited May 4May 4 by kurai

Further steps for Backblaze docker

The previous steps got Backblaze started and running ... for a while.

The Backblaze binaries seem to have some inbuilt mechanism for triggering detection of old executable versions and downloading of an update, despite the docker parameters 'Force Latest Update: False' and 'Disable Autoupdate: true' being applied.

Two hours after container start it would download a new .exe binary (interestingly, not the current version v.10.0.1.1037 but v.9.2.2.897). This would unpack and run an .msi installer, which would then abort after failing to satisfy a .NET dependency. This seems to have a greater than even chance of causing the main bzserv.exe service and/or bzbui.exe application to crash out. It would continue to retry this update process every 2 hours until the inevitable crash & black-screen.

The solution (that's been working for over 24 hours now) seems to be to replace the downloaded binary with an empty zero byte file and set it to root read-only (-r-------- [400]) so that it can't be replaced by the updater.

/appdata/Backblaze_Personal_Backup/wine/drive_c/Program Files (x86)/Backblaze/bzupdates/bzinstall-win32-9.2.2.897.exe [root -r-------- 0 B]

This seems to sidestep the issue by not allowing the installer process to begin at all.

Of course, this may not work forever ... the application does do a version check call-in at startup, and logs that it recieved a version obsolescence notice. Backblaze seem to be making definite steps to move forward with client versioning and may eventually reject connections from old enough clients rather than simply warning and trying to force an update.