imagoodusername

Members
  • Posts

    24
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

imagoodusername's Achievements

Noob

Noob (1/14)

3

Reputation

  1. Thank you for posting this. I landed here on a Google search. Yesterday I stupidly made a change to my wireguard setting to try to get remote access to a custom network through wireguard. The change crashed my entire server. Had to pull my USB drive and manually edit wg0.conf to delete my change just to get unRAID to boot again. Then I changed my docker settings to allow "Host access to custom networks" -- which allowed my two dockers to talk to one another (and for me to have wireguard access to the custom network docker) but it killed internet access for me. My output on the githubusercontent showed that my issue was not the issue in the thread, but in fact solved by you mentioning "disabled 'Host access to custom networks' in Docker settings". Wireguard is working again. My adguardhome-sync dockers are no longer working after disabling "Host access to custom networks" -- but whatever, I can manually sync things if needed.
  2. I *think* I was able to successfully update the build version to 1.0.0 by changing the repository from exadel/compreface:0.6.1 to exadel/compreface. I was able to boot to the webgui and login to Compreface, although I haven't tried to actually do anything with it yet. However making that change did cause the "Version" cell for CompreFace in the Docker tab to show "not available". I confess that my understanding of docker is not nearly as good as many people on here -- so apologies if I'm stating something incredibly obvious.
  3. For those who are still struggling to get Compreface running with the internal database, I think this is a step by step on how to fix the issue. If you are starting fresh, skip the first three lines. If you installed this docker already, start from the beginning. On the Docker tab in the unRaid webgui, stop CompreFace if running. On the Docker tab in the unRaid webgui, delete CompreFace docker installation. THIS IS VERY IMPORTANT: delete the default compreface folder that was created in your appdata folder. IF YOU DON’T DO THIS, YOU WILL CONTINUE TO GET ERRORS NO MATTER WHAT YOU DO. Go back to the apps tab and install Compreface (I’ve only tested the CPU version — I don’t know about the GPU version). DO NOT JUST BLINDLY HIT APPLY AND START THE INSTALL WITH THE DEFAULT PARAMETERS Instead, toggle on Advanced View (top right of the Compreface docker installation page). THEN GO TO “SHOW MORE SETTINGS”. DELETE ALL FOUR OF THE CUSTOM SETTINGS THERE BY USING THE BUTTONS TO THE RIGHT OF THE TEXT BOX Those settings are for using an external database, but if you are trying to use the internal database it will create a series of errors. Hit apply on the docker install page, and let docker/unraid do its thing. Go get a cup of coffee and let compreface go through its installation. After successful installation, you should be able to access the webgui for compreface without issue. These fixes do appear in this thread already, but I had to read through the thread several times and do a bunch of trial-and-error to figure out that I needed to delete the docker and the appdata before trying to reinstall sans database parameters.
  4. I have the exact same fault at the same time (which is a few minutes after my Plex Media Scanner starts) with the same library. Plex docker logs show "PLEX MEDIA SCANNER CRASHED, CRASH REPORT WRITTEN". Log folder was empty because apparently I have "Send crash reports to Plex" enabled. If the crash happens again tonight, I'll hopefully have more info in the morning. After doing a bit more searching, it looks like this may be a semi-known issue on the Plex forums. Either a lot of us have faulty RAM, or there may be an issue with Plex more generally. https://forums.plex.tv/t/server-1-23-2-4656-unable-to-scan-movies-seg-fault-external/721328/163
  5. I also ran into a problem where the webgui stopped working after the recent update, and I was also using CyberGhost. Nuked the docker container/image and reconfigured using my original credentials -- no improvement. The only thing that worked for me was revoking my CyberGhost credentials, generating new credentials, using those credentials in the docker setup and then manually copying over the contents of the OpenVPN configuration folder from CyberGhost to Docker's openvpn config folder.
  6. First off, a huge thank you to the LSIO team for all their work on this docker and all the other dockers that they do. Secondly, with Plex Live TV announcement, Plex (for me) might finally free me from Kodi/TvHeadEnd for Live TV. The holy grail for me would be to be able to use Plex for my media, Live TV, and DVR with Comskip. Having searched the forums, it looks like Comskip support for this Plex docker has stymied folks in the past. I ran across this how-to by a dev / network engineer that makes it seem pretty simple to get Comskip up and running inside a Plex docker. Has anyone got this running? If so, do you have to re-enable the Comskip, Plexcomkip and Dependencies every time you update the docker (maybe this is a stupid question, but I don't know much about Docker other than how to get one running and set variables/paths)? Is this a solution that could be integrated into the LSIO docker eventually? I would try playing around with this myself, but I recently fried my HDHR Connect. Note to self, don't plug the wrong AC Adapter into the HDHR. I plugged in an adapter outputting way too many volts and suddenly it smelled like burning...
  7. EDIT: Disregard post. I'm leaving it up in case anyone else comes across the issue. I was able to fix issue by adding year name of the film in parentheses in the file name (folder name did not need to be changed). Source of fix was this Reddit thread. I think the AVI format was a red herring...a lot of those files just happened to be very old and not organized as well as they should have been. Thanks so much for putting this together. I noticed that some of my movies aren't being recognized. From what I can tell, it looks like it's only AVI files with Codecs that are either MSMPEG4V3 or MPEG4. However, other AVI files with MPEG4 show up without issue. I searched this thread for AVI but didn't find any hits. Anyone else noticing similar behavior?
  8. That was it. 11G log from a linuxserver/couchpotato. EDIT: It appears you can set a /tmp directory for logs under advanced settings in CouchPotato. Going to try to map /tmp to something on the cache disk and see what happens. I'd be just as happy to disable logs entirely, but don't see an easy way to do that.
  9. Hi all, Are dockers and plugins safe to use? Specifically I'm thinking about malware or security vulnerabilities. What, beyond the benevolence of the repository maintainer, would stop someone from creating a rogue plugin or docker that effectively turns your unRAID box into a bitcoin miner (eg). Is there any sort of screening for the software in the default plugin/docker list that is enabled in Community Applications? Am I being paranoid?
  10. That's silly, of course you can use an aftermarket CPU cooler in the PC-Q25b. In fact, I'd argue that it's preferred. I used the Noctua NH-L9I in my last Lian Li build (PC-Q18) since it is lower profile than the stock Intel cooler. I like that it gives more room for airflow between the PSU and the CPU cooler fan. Did I mention than an SFX PSU is *highly, highly* recommended ? What you can't do in a PC-Q25b (or any of the SFF cases, really) is use one of the crazy big CPU coolers that look like a refrigeration unit mounted on a pedestal. I've never really bought into that style of cooler anyway, truthfully. Agreed on the fridge style fans. I bought one and don't understand the big deal. How much better (cooling and noise) is the Noctua than the stock Intel fan? I had planned to just go with the stock for the CPU, but I am replacing both case fans with Noctuas in order to get this as quiet as possible.
  11. Thanks for all the help everyone. I think I've decided to go with the Xeon e3-1245v5 and stick with the Lian-Li for now. I know that the venting isn't as ideal as larger cases, but the Lian-Li seems to be the best in its class for what I'm trying to accomplish and the e3 gives me more than sufficient CPU power for my needs (while keeping heat/power low) while also allowing me to later do ECC RAM if I change my mind there. Now to start ordering parts, and find the time to put it all together. Once I've got it up and running, I'll try to write a summary and post to this thread in case anyone finds this later and wants to know the thrilling conclusion.
  12. Wow. Looks interesting, but not sure I can stomach wading through this all again. So if I understand correctly, that mini-ITX board can do 6x SATA? But this e-ITX (which apparently can fit in that case) could do 14? http://www.newegg.com/Product/Product.aspx?Item=N82E16813157486 14k passmark just is absurd for my uses. I'd start to worry about power usage. Also, e5s don't have integrated graphics, right? If so, that kills my ability to do VM passthrough of the graphics card.
  13. Thanks. I think I'm going to start with non-ECC and move up to ECC once prices come down / availability increases. $200+ for 32GB of RAM is hard to swallow when I got 32GB of non-ECC RAM for under $100 -- the other alternative would be 16GB of ECC RAM for about $100, but I like the idea of having plenty of RAM to allocate to VMs. The truly important data that I am going to be saving to the build have multiple points of redundancies (family photos/movies, and those have additional redundancies outside of unRAID and outside of my home; Dropbox is cached to multiple computers, etc.). Nothing that is absolutely critical to me will be solely living on unRAID. I've looked at Broadwell/Haswell but (i) I can't seem to find 8 SATA mini-ITX boards and (ii) power consumption seems higher. I actually like the idea of a Broadwell/Haswell build because I understand it's possible to pass the integrated GPU through to a VM on those boards. If you know of an 8 SATA mini-ITX board supporting Broadwell or Haswell, I'm all ears Why am I so committed to mini-ITX? Form factor. This is a living room build, and, no, I don't have a spare closet to put a server rack (and yes, I know how much cheaper it would be if I did). Yes, I want to keep the 8 SATA ports (because I don't want to have to swap everything out out of a 6 SATA port board if I decide to do dual parity, dual cache parity, more SSDs, etc). Yes, I know I can get a SATA controller for a PCI slot, but I want to keep that free so I can pass a GPU to a VM in the future if need be. Barring a suitable Broadwell/Haswell option, I think I'll go with the e3-1245v5 -- it just seems to give me a bit more flexibility.
  14. I'm going to pass on ECC RAM for now (just don't want to spend $100 more on RAM right right now). The price difference between the i7-6700 and the e3-1245 v5 is negligible. It seems like e3 has slightly higher CPU benchmarks, and the i7 has slightly higher GPU benchmarks, but within a very close margin in both cases. i7 sounds like it might be more power efficient and run a bit cooler. Sounds like the only real difference on my build is that if I go with the e3 I could later upgrade the RAM to ECC. Otherwise it's all the same? I'm finding it hard to believe that Intel released two chips that seem to be damn near identical but just badged slightly differently and with slightly different mobo and RAM compatibility. All things being equal I think I'll grab the i7 for power consumption / temperature reasons, and just forgo the ECC RAM. Stupid idea? EDIT: I went ahead and made the mistake of reading this thread https://techreport.com/forums/viewtopic.php?f=36&t=117667 It seems like the differences between the i7-6700 and e3-1245 are non-existent if not running ECC RAM (and then that thread devolves into a discussion of whether or not there's any point to running ECC RAM -- which I still don't understand). I'm just...uh...gonna go lie down now and forget that I ever bothered asking the question.