Jump to content

lovingHDTV

Members
  • Content Count

    477
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lovingHDTV

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. is anyone running this docker in anything other than bridge mode?
  2. I'm trying to move all my dockers to my IOT vlan. I've successfully moved plex, deluge and nzbget. I can access them via their web interfaces fine. I also moved Sonarr and can access its web interface fine. However I cannot get Sonarr to connect to either of the downloaders. I did update the ips to the new ips, they are all on the same subnet. I opened a console into the Sonarr docker and can ping the IPs for the two download clients. Any ideas what I need to do to get Sonarr to be able to connect to the download clients? Essentially I've moved everything from bridge to br0.10. One additional comment: it connects to jackett just fine after I moved jackett as well. thanks david
  3. Ok how do I change that? I don't see that option in the VM settings any longer. I do see the btrfs as 20GB. NM figured it out
  4. OK I changed the disk size from 1GB to 20 and now it created the file. thanks
  5. I'm trying to setup VM for the first time and cannot find the libvirt file. Do I need to download that somewhere? I didn't see that step in the wiki. thanks, david
  6. I just built a similar system except I used E5-2680v3. So far it has been good. The IOMMU grouping is pretty good out of the box and I can use my GPU in the plex container without issues. I have had one time that samba went unresponsive, but I'm hoping that isn't a common occurrence. I do wish the board had IPMI, but it isn't a deal breaker for me.
  7. I was trying to copy a small file over to my cache drive. It took several minutes to copy, instead of a few seconds. I took at look at the processes and see find mdrecoveryd unraidd taking 200% of the CPU and a 2% wa. Any ideas what kicks off find, mdrecoveryd and unraidd? Nothing else was running. thanks david
  8. I've been using this in my box, but with my recent upgrade of hardware I no longer need it. It has been flashed to IT mode and ran without issues with UnRaid. $40+ Shipping CONUS thanks, david
  9. I'm looking for the block-off plate for the bottom power supply of the original Cooler Master Stacker case. I know that LimeTechnology sold a lot of these as preconfigured systems and I'm hoping someone may have an extra blocker plate laying around. It let's you put 2x80mm fans in down there. Mine has been a gaping hole for years after I went from dual power supplies to a single. If so please PM me, david
  10. Nevermind, I found that my .htpasswd was located at /config/nginx/site-confs/.htpasswd. moved it to the correct place and everything started working.
  11. OK I narrowed it down to my password file. If I remove it from the site-confs/default I can access everything internally and externally. If I put in: auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; I immediately get a 403 Forbidden message. no chance to even enter the password. I tried Edge, as I hadn't use it and I did get the password prompt before getting the 403 message.
  12. I tested the hole and can't discern which direction the air is flowing. It isn't extreme in any condition. I'm not too worried as it has been functioning for 12 years this way. It has been on my list to block off, but obviously not very high up on the list
  13. I mistakenly clobbered my letsencrypt docker. Hint don't install two dockers with the same name, even mistakenly. So I started over new and followed the same walk through as I did last time, but things didn't work this time. https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/ I filled in the docker just like the tutorial says, but using my data which is also on duckdns.org. It first went wrong after I started the docker and I couldn't even connect to get the "Welcome to our server" message. When I connect to port 81 I get "site cannot be reached, connection refused". I continued, thinking that now I may need more configuration to get it working. After completing the setup and adding a /sonarr subdirectory I still get that message for port 81, but now for port 444 I get a password prompt, which I enter and then it gives me 403 Forbidden NGINIX 1.16.1. I was happy to see the username/password prompt, but the 403 is annoying. It happens for every subdirectory. Any ideas? thanks david
  14. There are fans in front of the drives pulling air in from the outside and over them. As I have 3x120mm fans pulling in fresh air and only 2 exhausting air, I suspect that air exits the hole in the bottom. I'll test that out and see.
  15. I tried every hyper visor I could find. None of them shared the GPU in a manner that the unraid-nvidia plugin would recognize the GPU. Good question on the airflow. I did my best to draw it up. There are 3x120mm fans in the 4-in-3 adapters, one 80mm fan in the top, the power supplies fan and the 120mm in the back of the case. The final fan is an 80mm in the side panel that brings in fresh air immediately below the cpu fans. The CPU fans move air upwards.