Jump to content

Jason Harris

Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Jason Harris

  • Rank
    Member
  • Birthday 08/11/1979

Recent Profile Visitors

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

  1. Or, if support is critical for you, purchase a RHEL license so you can call up Red Hat if you have issues and roll RHEL 8.1 instead of CentOS.
  2. Yea, sickrage / sickbeard is a great tool. And I may have mixed them up above - I forget which one was first. I ran sickrage for quite some time but for my particular requirements I found much more compatibility with Sonarr. But again, everyone has different requirements, so gotta go with what works best for you!
  3. I agree with this. Look at something like oVirt (or pay for VMWare if your company has the cash). Or if this is just a single server, install CentOS 8.1 and KVM and set up the disks in a RAID-5 with proper backups. UnRAID is great for us hobbyists but I wouldn't put it into a production environment for business data.
  4. I used to run Sickbeard but after the drama between the original dev for Sickrage picking fights w/ the Sickbeard folks that forked I just moved on to Sonarr/Radarr/Jackett. As mentioned above, they just 'work'. And no dev drama. But try them all out, see what's right for you.
  5. I used to run FreeNAS with MediaTomb for my media server, but the support community was horrible. Everything came down to "Learn this stuff yourself" or "You need ZFS and ECC otherwise you're a dumb***". UnRAID's community has been the complete reverse of that. Sure, technically FreeNAS is the better solution, in "theory", but the community is just horrible. That said, there are use cases for one (or both) solutions, just depends on what you want to do. For me, I like UnRAID because it makes management of my server seamless and easy. I don't have to constantly tinker with things, and I can go months without having to even touch the server. FreeNAS required much more attention, which is probably fine for some folks that like to tinker. /shrug
  6. I can tell you that my old Ivy Bridge 3770k can run at least 3-4 h.265 streams just fine before hitting around 90%. A NUC probably can't cope w/ that though, or probably any ARM processor.
  7. Hey now, I don't have my flying Delorean or hoverboard.
  8. This will be huge for things like Stadia, remote Steam gaming, and streaming solutions like Netflix / CBS All Access / etc. Will cut down on 4k stream data transfers like crazy. Hopefully it's not licensed like H.264 was. Neat news for sure!
  9. If that meets your needs, yep. Not that I want to steal away a license from UnRAID lol. You could just run Plex on a bare-metal Windows 10 system and use Docker to do what you want. You'll want to look up 'Storage Spaces' on Windows 10 so you can set up a RAID-5 array (software RAID), or use the Intel RAID controller if you have one for a pseudo-hardware RAID array. Then you could just run games from the server, while it serves media to everything else in the background. There will be some overhead for CPU cycles while you're using it for gaming, but it shouldn't impact Plex or Emby or anything.
  10. Correct, if using Steam. You install the Steam client on the VM and pass through the GPU to the VM. Then, on the 'client' (laptop, whatever), you launch Steam and use the in-home streaming feature. You can stream the game, and the VM does all of the work, while the client just displays what the VM is presenting. Not sure if Epic or GOG or other launchers support this. Edit: And that's not just on UnRAID, that's on any solution you choose to go with if UnRAID doesn't work for you.
  11. Yea, I think you're better suited for running two systems - one for UnRAID and a 2nd system for gaming. You can run Windows 10 in a VM in UnRAID and pass through the GPU, but now you have a new challenge of how to properly stream the game from the VM to another computer. Advantage there is that you can play any game you want from any computer you want. I do this. Disadvantage is that you now have an extra layer of complexity that can fail, and if it fails you'll probably spend more time trying to fix it than you'd like. And trust me, as a father and husband, an angry wife and kids is no way to spend a weekend Edit: Another disadvantage is that video streaming will be horrible. Watching an h.264 or h.265 video using a remote desktop viewing program, no matter the tech, is very problematic and introduces a lot of jitter.
  12. What do you mean "Windows 10 on top of UnRAID"? I don't follow that.
  13. Yea, keep the VPN on UnRAID IMO. I personally use this and it works just fine. I just point my containers to this container for VPN access and it works fine. https://hub.docker.com/r/binhex/arch-delugevpn/ Video if you're uncomfortable or unfamiliar with the UnRAID GUI or infrastructure: https://www.youtube.com/watch?v=5AEzm5y2EvM For remote VPN connectivity if you're not at home, use the ASUS router with the MerlinRT firmware. https://www.asuswrt-merlin.net/ I use it and it is a lifesaver, and works just fine with Windows' default VPN client (if you use Windows). Or your OpenVPN client of choice. Hopefully Wireguard support is added soon, to either Merlin or Asus' builds.
  14. Jason Harris

    VPN Provider?

    I use https://www.privateinternetaccess.com/ and they work fine. They also forward, but only from some sites. They have docs on how to guide you. Works great for me. Edit: https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn That will tell you which sites to use for whatever VPN solution you have in your setup. You will need to follow the setup guide for whatever container you're using to configure the VPN client on your end. This usually means hacking it on the command line, or configuring the setup file beforehand using Notepad or something on Windows and then overwriting the file of the same name on your container's VPN setup and restarting the container so it loads the new configuration. Check the support threads for your VPN container of choice on further instructions.