Community Developer
  • Content Count

  • Joined

  • Last visited

Everything posted by coppit

  1. This container stopped working a bit ago due to an API change. In updating it, I realized that FileBot went to a paid model, and that there's another better supported container available. I'm removing this container. Please use the other one. Personally, I'm switching to Sonarr.
  2. I also just stumbled across this thread. I have /etc/resolv.conf.avahi, where my static DNS entries are. Oddly, my resolv.conf has, which is my gateway. I'm going to disable avahi, which I expect will fix my problem.
  3. How about if I added a bash script to the config dir, and you could put any command you want in there, including "yum install comskip"?
  4. I reverted the Alpine Linux changes late last night, so things should be back to how they were.
  5. Are you saying that where it prints: Configuration: USERNAME=foo PASSWORD=<hidden> DOMAINS=bar INTERVAL=baz DEBUG=zap It displays your password in the USERNAME line? A couple of thoughts: Make sure that your password is within single-quotes like: PASSWORD='your password goes in here' However, if your password contains a single quote, then you have to escape it. LMK if that's the case. Second, make sure that you aren't defining environment variables for the container that are overriding the config file.
  6. Moved to Alpine linux, reducing the image size from 232MB to 90MB Also: Make the change monitors more like services that restart if they crash. Added a feature to use polling, so that Windows shares can be monitored too.
  7. Does the client connect and complain about the version? Or does it not connect at all to the port? Are you remapping 10090 or 8090, or both?
  8. I moved the image to Alpine linux, which drops the size from 229MB to 64MB. I also added the ability to configure it using env vars instead of the config file. This is a pretty big change, so let me know if you guys see any issues.
  9. I switched the container from the phusion base image to Alpine linux. The size dropped from about 250MB to about 16MB. It also handles options set using environment variables rather than the config file better. This is a pretty big change, so let me know if you guys see any issues.
  10. New update is out. I moved from the phusion (Ubuntu-based) base image to Alpine. The image is 5x smaller. Also, you can now specify all the settings using only environment variables. In this case you don't need the config file. Env vars take precedence over the config file values.
  11. Hi everyone, I found a bug in the container that causes the recordings to be saved inside the container, instead of to the attached disk volume. I'll release a fix soon. You must run the following command before updating your container, or your videos will be lost! docker exec -it Xeoma bash -c 'cd /usr/local/Xeoma/XeomaArchive; for n in *;do mv "$n"/* "/archive/$n";done' I'll wait about a day before releasing the fix, in case anyone has auto-update configured for their docker containers.
  12. The author (or moderators of Community Applications) of the plugin template ( has specified that this plugin is incompatible with your version of unRaid (6.5.3). You should uninstall the plugin here: Maximum OS Version: 6.4.1 I didn't specify any such thing. Tested as working with 6.5.3. How do I get this fixed?
  13. User reports it works: I installed it and it works as well. Are you the keeper of plugins? Can someone please point me to the latest plugin documentation? My plugin files aren't part of a txz like I see others have. When it gets installed by the system, the directory is missing "other" read and execute permissions, which means that emhttp can't read the icon. I also see that the latest plugin plg's don't have "iconfile". I'd like to renovate my plugin, but don't know how.
  14. Can someone please point me to the latest XML template for plugins, so that I can update my mosh plugin? It's currently not even showing up in CA, I guess because it's assumed to be incompatible with the latest version of UNRAID until I indicate otherwise.
  15. Whoa. My SageTV and UNRAID worlds are colliding! To be honest, I'm not very familiar with USB devices and docker. This post seems to suggest that you can pass the devices through. The container is based on Ubuntu, so you could try getting into it with "docker exec -it xeoma bash" and installing USB drivers there. Heck, maybe it will "just work" without any special drivers, being "universal" and all. If that works, I could see about including those drivers in the container. But to be honest, USB cameras are not that great. I would get HikVision cameras, which are afforda
  16. Sorry. That was a goof on my part. I just pushed a fix. As soon as the container rebuilds on the hub, you'll have the fix.
  17. Thanks everyone for helping folks to enable the UI. I appreciate the assistance. I've updated the first post to this thread, so hopefully people won't have to keep asking.
  18. I saw this too. After I rewrote the download code, it went away. Not sure if I really fixed it or not. I'll try to keep an eye on this thread in case anyone sees it again.
  19. They changed the format of the webpage that I was using to get the latest version information. Good news though... I did some sleuthing into how Xeoma itself learns about new versions, and found the XML endpoint where they publish the information. With that knowledge, I rewrote the code to use that endpoint, which should be a lot more reliable going forward. As a bonus, I also exposed port 10090, so if you want to add the web server feature to your camera workflows, you can access Xeoma through the web browser as well. See for m
  20. Yeah, it looks like the website switched from http to https. (That's why downloading it manually and saving it as the .tar.gz worked.) I just pushed an update that hopefully will fix it. However, I'm still having trouble getting my container to start. I'll work on it before I have to catch a plane. Let me know if the latest version fixes the "stable" and "beta" download methods, please. Be sure to delete the contents of the downloads folder and update your conf before trying it though. Otherwise it will use the cached .tar.gz
  21. After updating to the latest version, the container doesn't seem to lock up. (After 2 days, at least.)
  22. Did you set it up using the SpaceInvader One approach? I had to hard-reboot my server, and after a few days it ended up the same way. I'm wondering if a log or something is causing the container to lock up after a few days.
  23. Maybe if the feed can't be reached, issue a warning but let people use the cached app list? I'm all excited to try out pihole for the latest SpaceInvaderOne video, but instead I have to do Easter stuff with my family. :-)