grantbey

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

grantbey's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I had this same issue today. The only real changes I'd made recently were upgrading to 6.12.6. For me, restarting nginx solved the problem: /etc/rc.d/rc.nginx restart Unclear if this will be a persistent problem with subsequent reboots.
  2. This tuner supports ATSC and clear QAM, which are North American standards. I'd need the version of this tuner which supports DVB-T2, DVB-T and DVB-C. As such, this will be posted in the BUY, SELL, TRADE forum but if anyone reading this is interested feel free to DM me!
  3. Hi All, I've been an Unraid user for several years now, but I'm currently in between setups. I moved from NYC to London two years ago and in the process I had to disassemble my server and put it in storage. Now, I'm looking to reconstitute the system, albeit with a bit of an update. Previous Build The old server was as follows (some are approximate guesses due to a lack of records!): MB: ASUS Z97-A ATX CPU: 4th or 5th Gen Intel Core i5 or i7 (honestly can't remember exactly what I had, and I inherited it so there are no old order histories to consult!) RAM: 20GB of DDR3 memory (one 2x8GB Kingston kit and a random 4GB Samsung stick) PSU: Thermaltake Toughpower PF1 850W (PS-TPD-0850FNFAPU-1) GPU: GTX1080Ti HDDs: 8x 3.5" SATA drives (a mix of 5400/7200 RPM and a mix of vendors) SSD: Samsung EVO 970 Pro 1TB M2 NVME Extension card: LSI LSI00301 (9207-8i) SATA Host Controller Card Enabling 8x SATA connections via two x4 mini-SAS connectors and mini-SAS to SATA breakout cables, running on PCIe3.0 x8 Tuner: Hauppauge WinTV-quadHD PCI Express TV Tuner Card 1609 The setup was great, albeit I know it had some issues. It was cobbled together over time, and on a serious budget, but it did what I needed it to do. Now, a couple of years later, only the underlined items have survived 😢 There's a great story about going through airport security with carry-on bag containing eight HDDs, a GPU, a PSU and a couple of extension cards wrapped in bubble wrap and being asked to "remove any large electronics" 🤣 But let's not dwell on that sad story, because out of the ashes a phoenix shall (hopefully) rise! New Build I've ordered some components to rebuild and I wanted to see if anyone here had any gotchas with the component list: MB: Gigabyte B760M AORUS ELITE AX Has just enough PCIe lanes for me: one x16 for the GPU and one x4 (size x16) for the SATA controller I'm aware that the SATA controller is PCIe 3.0 x8 and will be going into an x4 slot, so half the bandwidth it requires It's capable of hosting 8x6Gbps SATA connections, but I'll only be using four (the other four HDDs will go into the MB) So by my calculations the 4x8Gbps PCIe bandwidth should be enough to handle those four HDDs, right? CPU: Intel Core i3-13100 Went for the cheapest option here with a view that in a couple of years I might upgrade to an i5/i7 but wanted to keep the cost low. Planning to use the stock CPU cooler until I upgrade or if I notice any performance issues. Correct me if I'm wrong but this should be about as capable as the 4th/5th Gen Core i5/i7 that I might have had before? HW transcoding: from memory, Plex wasn't able to HW transcode using the CPU - I had to make special efforts to use the GPU for transcoding. I'm not sure if this was simply because the CPU didn't have an iGPU or because the architecture didn't support it. This should be different now, right? RAM: 32GB of DDR5 memory (CORSAIR Vengeance 2 x 16GB DDR5 4800 CMK32GX5M2A4800C40) Limited to 4800Mz by the Core-i3 Case: Fractal Design Node 804 Questions Now that the details are out of the way, I'll summarise the major questions: Given that the MB only has four SATA ports, the SATA controller is pretty important. Are there any major reasons to think it won't work now, given that it did work before in the old system? Did I sacrifice too much going for the Core i3, or will it be about parity with what I had before (4th/5th Gen core i5/i7 idk sorry)? Is it really as simply as plugging everything back in and my array going back to how it was? I'd hate to lose all the data that's on those drives and have to wipe them and start from scratch, but also nothing on there is critically important so I'll survive if that's the case. Is there a strategy here? Thanks in advance for reading and helping! Grant
  4. I'd like to add that for anyone having problems, check out the the syslog immediately after trying a log in: tail /var/log/syslog Mine had this line: Authentication refused: bad ownership or modes for directory / Which was easily fixed by doing this: cd / chown root:root .
  5. Hey @kocane I stumbled across your post in this forum after researching the same thing. I'm not sure if you ever found a solution, but I did. I implemented a workaround for @binhex's arch-qbittorrent container, but the same should apply for Deluge. I posted as it an issue on the github for that container, and you can read the solution here. In brief, it's similar to the ADDITIONAL_PORTS method available in the arch-sabnzbdvpn container. The extra variable is parsed by the iptable.sh script and adds a new iptable rule which allows incoming and outgoing connections on the ports you specify on the LAN subnet. That last part is important - these newly permissive rules only allow connections to/from the ports you specify if they're on the local subnet, i.e. they're on your local network or your VLAN. Feel free to reply here or PM me if you want any help. As a disclaimer: I'm fairly certain this doesn't sabotage the iptables rules and create a leak. I did enough reading and I'm confident enough in my own competence, but of course I don't guarantee anything. I'm sure someone here will soon offer a strict warning on messing with the iptables rules, and they'd be correct - in the wrong hands the entire point of the VPN could be nullified, and it would happen silently. If anyone actually looks at what I did and finds flaws, I'd REALLY appreciate the heads-up!
  6. RE my above post, consider is SOLVED. The problem was quite simple: I use nginx to reverse proxy my various application interfaces to subdomains which are accessible over the internet. Because of this, Jackett was generating a torznab host address of the form https://jacket.mydomain.com/. Simply changing this to my local IP address when adding it to Sonarr (eg http://10.0.1.7:port/) solved the problem.
  7. I'm having issues, hopefully you guys can help. My configuration is set as below on the Jackett admin page: My container is set up as follows: If I run a manual search and select "download locally" the torrent is sent to deluge, however if I select "save to server blackhole directory" I get the error "request to jacket server failed" on the screen, but no mention in the logs. Additionally, if I run a search in sonarr I get shown releases from my indexer, but selecting them for download gives the error "invalid torrent file specified" Any help would be appreciated.
  8. Yes, I originally set it from the web interface. I double checked that the core.conf file was being updated by the web interface too. Is this for manually added torrents, or automatically sent from another application like sonarr? Good catch: this has been using DelugeSiphon to handle magnet links. Adding .torrent files to the watched folder results in correct behaviour. Follow up question: how do I use DelugeSiphon, or is there a better chrome extension that others use? Thanks!!
  9. I'm having some trouble getting the downloads to go to the correct folder. I have the following mappings: /data -> /mnt/user/deluge /config -> /mnt/user/appdata/deluge My core.conf file has the following entries (in their correct positions in the file): "download_location": "/data/incompleted" "move_completed_path": "/data/complete" "autoadd_location": "/data/torrent-files" Yet still new downloads are downloaded in /home/nobody/Incompletes. I've checked the permissions of the /data folder multiple times, they're owned by nobody:users (99:100) which is the user deluge runs under. Deluge seems to willfully ignore my instructions for some reason. Weirdly, completed downloads are moving correctly. I just don't want incomplete downloads to accumulate inside the docker image. Does anyone have any ideas?