Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Skylord123

  • Rank


  • URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. What did you set nodered's appdata path to? Is it the same path you ran that ls command on? If you changed what the default install directory is you will need to LS that directory instead of the one I mentioned. /mnt/user/appdata/nodered is the default only if you didn't change it. If you didn't change the default path and it is missing now that is pretty alarming and points to either corruption or something deleted it. I actually use CrashPlan for backing up my entire appdata folder because I have had drives fail & accidents happen.
  2. Sounds like there is some sort of permission issue with your mounted /data volume. The /usr/src/node-red/node_modules/node-red/settings.js path is inside the container and wont exist on the host (which is why you probably didn't find it). This doesn't matter though because this is just copying the default config file if one doesn't exist. The real problem lies within your mounted appdata volume for node-red (default path on unraid host is /mnt/user/appdata/nodered (unless you specified some other path). I would run this command to see what the permissions are for this directory: ls -all /mnt/user/appdata/nodered My guess is it is a permission issue but it could be something else. This command should give you all the information you need to fix the problem. If you can't figure it out feel free to post the output here and I can help you out some more.
  3. This support thread is for the MQTT container (and Spant's other containers). I would recommend you head over to whichever project you are referring to and post on their thread. I haven't configured the unraid API to use MQTT myself so I wouldn't know. Good luck!
  4. You need to go to the path you installed your container's appdata path and modify the config file. Inside that config file you have two users defined. Just remove one of them.
  5. When you installed the container you chose your appdata location. It is wherever you selected for that. You can always edit your containers to see what paths you used (it should also display this from the docker list in Unraid).
  6. I don't know about the UnraidAPI stuff but the error you are getting indicates you have the same user defined twice in your config. I actually helped someone out that was having this same issue on my blog (scroll down to the comments): https://skylar.tech/installing-mqtt-under-docker/
  7. I wrote a post about installing MQTT in Unraid using your container. If anyone needs help they can check it out: https://skylar.tech/installing-mqtt-under-docker/ A good number of my readers requested this post. Figured it would be good to put this here for others.
  8. Can we get updated versions based on tags? This way we can keep this stable version under one tag but also be able to try out the newer versions. As nice as it is staying on one version the updates can be really important for security and performance.
  9. I don't know exactly which post you are referring to but as far as I can tell everyone is doing it the same way as me. You need a Redis instance running as the Nextcloud container doesn't come with one. EDIT: oops missed your link. That user just says he installed it by modifying the config but doesn't really go into detail about all the steps. You need a Redis instance running which you install via community applications.
  10. I created a post about using redis with this container in Unraid: https://skylar.tech/reduce-nextcloud-mysql-usage-using-redis-for-cache/ I recommend checking it out if anyone is getting performance issues with their database.
  11. If you mount the same parent directory that both input and output directories share you can get near instant file moves. An example is me using /mnt/user/media/filebot_process for input and /mnt/user/media/Videos for output and then mounting /mnt/user/media as /media instead of mounting the input and output separately. You then need to point filebot to the input and output directories and you are good to go. Now all my files are available within a second of being moved. I hope I explained this well. Let me know if not. I just moved to the other filebot container and got this same setup working with it (had to open a github issue to get it added but the guy got it done).
  12. Oh snap it actually is working I just wasn't able to query it correctly by hitting the other ports. I guess I missed this one. I should have tried just joining it in the game. Thanks, it is working great now
  13. Anyone have success getting a Killing Floor 1 server running? I've been trying for a while without any success. I tried forwarding all the ports mentioned in the docs and it still isn't working. I even gave it it's own IP address (so all ports are open) and still nothing. I'm wondering if something is wrong with the container. Can someone else try to start one and see if it works?
  14. oooooo, nice! I was going to add it but been pretty busy lately (especially with the Holidays). Btw, thanks for the steamcmd docker container that I used to create this one. Saved me a lot of work I also use your other containers and they have all been great. I was able to fix my issue with my sven co-op server by using the cache drive directly instead of the share (changing /mnt/user/appdata/svencoop to /mnt/cache/appdata/svencoop). I'm not sure exactly what broke _stat calls for share mounts. If anyone else has an idea of what it could be I would love to hear about it.
  15. I wrote a post about using Xeoma to trigger automatic lights by using Xeoma, Node-RED, and Home Assistant: https://skylar.tech/send-motion-events-over-mqtt-from-xeoma/ Hope some find it useful. It has been pretty handy. I did recently switch over to some PIR motion sensors in some areas and actually use my PIR sensors to trigger recording on the cameras (on top of motion detection). I may have to write another post about how to do that.