• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About SRB

  • Rank


  • Gender
  • Location
    Waterloo, Canada

Recent Profile Visitors

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

  1. Just recently, I am getting errors when trying to connect to certain indexers in Sonarr/Radarr when going through this container's Privoxy. Some indexers work, and some don't (I've found that Rarbg and don't). Disabling the proxy in Sonarr/Radarr fixes the issues. Any ideas on what might be causing this? The Sonarr logs just give a generic protocol error Unable to connect to indexer: Error: ProtocolError: ''
  2. Excellent, thanks for the clarification
  3. I had the same question as I switched from PIA to Mullvad. I think I have port forwarding setup correctly as I am seeing a big improvement in speeds after I did the following: 1. Got a port assigned from Mullvad (My Account > Manage ports and WireGuard keys > OpenVPN Forwarded Ports) 2. Stop and modify DelugeVPN docker container. Everything stayed the same from my PIA configuration, except: VPN_user: [Mullvad account #] VPN_pass: m VPN_PROV: custom STRICT_PORT_FORWARD: no (only required for PIA) 3. Download ovpn file and crt file fr
  4. Hey everyone, Hoping I can get some help with pfSense running as a VM within Unraid. The VM has been freezing causing all network traffic to die, and it all stems from this error in the pfSense syslog Nov 18 10:52:47 kernel calcru: runtime went backwards from 2843 usec to 1269 usec for pid 0 (kernel) Nov 18 10:52:47 kernel calcru: runtime went backwards from 2831 usec to 1268 usec for pid 0 (kernel) Nov 18 10:52:47 kernel calcru: runtime went backwards from 2689 usec to 1200 usec for pid 0 (kernel) Nov 18 10:52:47 kernel calcru: runtime went backwards from 29
  5. Done and fixed. Thanks. Not sure what caused it because I don't have any VMs on this machine.
  6. I have the following error on my VM page: Warning: syntax error, unexpected '&' in /boot/config/domain.cfg on line 10 in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 460 which also breaks the VMs section on the Dashboard page.
  7. I struggled with InvoiceNinja as a docker for a while, never got it to work and so decided to run it as an Ubuntu VM. Been running smoothly for over 6 months now and I have no complaints. Followed this guide to get it up and running: Did a little bit of customizing to get it to work with the Linuxserver letsencrypt docker, which I'd be happy to share if anyone is interested.
  8. One issue I've noticed after point unmanic to my entire tv shows library is that the dashboard page becomes unresponsive. Tested on both firefox and chrome. I've queued up several hundred jobs, all of which are trying to be displayed on the dashboard which the browser cannot handle. The conversions continue on just fine and the work around is to check progress on the history page.
  9. Thank you, upgraded with no issues. Love this plugin and appreciate all the hard work put into it.
  10. I remember seeing a notification when the 6.7.1 Unraid Nvidia build was released? Maybe I'm misremembering. Either way, I have Unraid update and plugin notifications disable and enabled, respectively, so we'll see if a notification comes through when 6.7.2 Unraid Nvidia is released.
  11. Doesn't a work around for this already exist? In Settings > Notification Settings, set Unraid update notification to never check. Then make sure the Plugin update notification is set to something other than never check, since I'm assuming the notifications sent by Unraid Nvidia are considered 'plugin notifications', right @CHBMB?
  12. After the update, I am still getting the same ffmpeg convert error on certain files. Let me know if there are any debugging steps/logs I can provide that can help.
  13. What Boniel said. /mnt/disks is from UD, I'm using it to mount my TV share on my main Unraid box through NFS. I've wavered back and forth between using /mnt/cache and /mnt/user for my appdata folder since I usually always have it set to cache only. But that one time I switched it to use the array and didn't clean up the references to /mnt/cache, oh man the headaches...