morethanenough

Members
  • Posts

    36
  • Joined

  • Last visited

Recent Profile Visitors

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

morethanenough's Achievements

Noob

Noob (1/14)

4

Reputation

  1. Due to limitations from my ISP (and country), I am forced to run Prowlarr through PrivoxyVPN. The problem is that once I set up Prowlarr to connect though binhex/arch-privoxyvpn, it loses connection to all other ARRs (Sonarr, Radarr), because these are not routed through a VPN but are running ion the Bridge network instead. Is there a way to fix this please?
  2. Hi all, Long post ahead warning, there's no other way to explain what's happening... So I have followed the amazing TRaSH guide for the ARRs that explains everything in great detail, but I have a problem and I'd like to ask for your kind help please. A bit about how everything is set up: One pool called "Cache_arrs" that contains a single share called "ARRS". The "ARRS" share is set at Cache_arrs -> Array (if that makes any difference, which I think does not) Within the ARRS share, there is the following folder structure (inspired by the TRaSH guide) ARRS ├── usenet │ ├── incomplete │ └── complete │ ├── movies │ └── tv └── media ├── ANIMATED ├── DOCUMENTARIES ├── FILMS ├── MUSIC_VIDEOS ├── NEW_MOVIES ├── NEW_TV_SHOWS ├── STANDUP ├── TV_SHOWS └── XMAS I want SABnzbd to be downloading media into the relevant folders, depending on what I mark each item as before it's downloaded. For example, if I mark something as a Documentary, it should end up in the DOCUMENTARIES folder. I will be setting up SABnzbd's Categories settings (screenshot further below) to be able to do that, but I can't do it yet as I need to sort out this problem first. Also, content in all folders except NEW_MOVIES and NEW_TV_SHOWS will be retained long term and backed up elsewhere (and will need to be monitored by Radarr/Sonarr for quality upgrades), whereas anything that ends up in the NEW_MOVIES and NEW_TV_SHOWS folders is just to be watched once and then discarded. I have Sonarr, Radarr and SABnzbd installed (all are hotio's versions) Radarr's container settings are as follows: SABnzbd's container settings are as follows: Here are Radarr's Root Folders: Here are SABnzbd's Folder settings: And here are SABnzbd's Categories settings, which I suspect have something to do with the problem: I notice that under SABnzbd's Folder settings it says Default Base folder: /config whereas under SABnzbd's Categories settings it says Relative folders are based on: /data/complete. I don't understand what that means and if it is related to the problem. Now the problem: I am receiving an error message on Radarr saying: I have been trying for the past 6 hours to resolve this issue, which has resulted in exactly 6 wasted hours with no result other than a massive headache. Can someone please help me understand what I have messed up?
  3. Hi all, I received a notification email this morning to update unassigned.devices.plg so I went ahead and updated it to version 2023.08.17a I am running Unraid version: 6.11.5 When the update finished, I noticed I can no longer access the two unassigned devices I have. Here's a screenshot: Looking at each one (CCTV and TRANSIT), I can see they are not clickable, and next to them there is a faded button saying "REBOOT". I thought this signified the need to reboot Unraid so that the update will take effect or something, so I did. The problem remains though, and I cannot access these two devices. Both were working fine until this last update to version 2023.08.17a was installed. Any ideas what I did wrong?
  4. Yes, it is. Somehow it started working on the next day. Anyway, thank you for replying, all sorted now.
  5. Hi all, I seem to have a strange problem with the WebUI. I don't know when this started because I hadn't connected to it for a while, but the WebUI is not loading at all. The strange thing is that I have set Frigate to create RTMP feeds and these work perfectly fine. Also, recordings are being made as normal. The only thing that is not working is the WebUI. I have a Home Assistant instance on a different machine, and initially I thought there was some problem with that, but when I checked the WebUI on Unraid, I realised that's where the problem actually lies. I had installed the blakeblackshear frigate app quite a while ago, but I remember seeing somewhere that there were some breaking changes, so I removed it and installed the new version (for some reason the old one wasn't showing as installed in the Community Apps). Again, after setting everything up, everything works except the WebUI. The logs are below: Plus API Key is not formatted correctly. [2023-02-24 19:08:44] frigate.app INFO : Starting Frigate (0.11.1-2eada21) [2023-02-24 19:08:44] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:08:44] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:08:44] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:08:44] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:08:44] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' Starting migrations [2023-02-24 19:08:44] peewee_migrate INFO : Starting migrations There is nothing to migrate [2023-02-24 19:08:44] peewee_migrate INFO : There is nothing to migrate [2023-02-24 19:08:44] detector.coral INFO : Starting detection process: 216 [2023-02-24 19:08:44] frigate.app INFO : Output process started: 218 [2023-02-24 19:08:44] frigate.app INFO : Camera processor started for FrontGarden: 226 [2023-02-24 19:08:44] frigate.edgetpu INFO : Attempting to load TPU as pci [2023-02-24 19:08:44] frigate.edgetpu INFO : TPU found [2023-02-24 19:08:44] ws4py INFO : Using epoll [2023-02-24 19:08:44] frigate.app INFO : Camera processor started for Driveway: 237 [2023-02-24 19:08:44] frigate.app INFO : Camera processor started for BackGarden: 238 [2023-02-24 19:08:44] frigate.app INFO : Camera processor started for Kitchen: 240 [2023-02-24 19:08:44] frigate.app INFO : Camera processor started for TVRoom: 242 [2023-02-24 19:08:44] frigate.app INFO : Capture process started for FrontGarden: 243 [2023-02-24 19:08:44] frigate.app INFO : Capture process started for Driveway: 246 [2023-02-24 19:08:44] frigate.app INFO : Capture process started for BackGarden: 250 [2023-02-24 19:08:44] frigate.app INFO : Capture process started for Kitchen: 253 [2023-02-24 19:08:44] frigate.app INFO : Capture process started for TVRoom: 257 [2023-02-24 19:08:44] ws4py INFO : Using epoll [2023-02-24 19:08:54] frigate.video ERROR : Driveway: Unable to read frames from ffmpeg process. [2023-02-24 19:08:54] frigate.video ERROR : Driveway: ffmpeg process is not running. exiting capture thread... [2023-02-24 19:08:54] frigate.video ERROR : Kitchen: Unable to read frames from ffmpeg process. [2023-02-24 19:08:54] frigate.video ERROR : Kitchen: ffmpeg process is not running. exiting capture thread... [2023-02-24 19:08:54] frigate.video ERROR : BackGarden: Unable to read frames from ffmpeg process. [2023-02-24 19:08:54] frigate.video ERROR : BackGarden: ffmpeg process is not running. exiting capture thread... [2023-02-24 19:08:54] frigate.video ERROR : TVRoom: Unable to read frames from ffmpeg process. [2023-02-24 19:08:54] frigate.video ERROR : TVRoom: ffmpeg process is not running. exiting capture thread... [2023-02-24 19:08:54] frigate.video ERROR : FrontGarden: Unable to read frames from ffmpeg process. [2023-02-24 19:08:54] frigate.video ERROR : FrontGarden: ffmpeg process is not running. exiting capture thread... Plus API Key is not formatted correctly. [2023-02-24 19:09:05] frigate.app INFO : Starting Frigate (0.11.1-2eada21) [2023-02-24 19:09:05] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:09:05] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:09:05] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:09:05] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' [2023-02-24 19:09:05] frigate.config WARNING : The 'retain_days' config option has been DEPRECATED and will be removed in a future version. Please use the 'days' setting under 'retain' Starting migrations [2023-02-24 19:09:05] peewee_migrate INFO : Starting migrations There is nothing to migrate [2023-02-24 19:09:05] peewee_migrate INFO : There is nothing to migrate [2023-02-24 19:09:05] detector.coral INFO : Starting detection process: 216 [2023-02-24 19:09:05] frigate.app INFO : Output process started: 218 [2023-02-24 19:09:05] ws4py INFO : Using epoll [2023-02-24 19:09:05] frigate.edgetpu INFO : Attempting to load TPU as pci [2023-02-24 19:09:05] frigate.edgetpu INFO : TPU found [2023-02-24 19:09:05] frigate.app INFO : Camera processor started for FrontGarden: 236 [2023-02-24 19:09:05] frigate.app INFO : Camera processor started for Driveway: 238 [2023-02-24 19:09:05] frigate.app INFO : Camera processor started for BackGarden: 239 [2023-02-24 19:09:05] frigate.app INFO : Camera processor started for Kitchen: 241 [2023-02-24 19:09:05] frigate.app INFO : Camera processor started for TVRoom: 242 [2023-02-24 19:09:05] frigate.app INFO : Capture process started for FrontGarden: 243 [2023-02-24 19:09:05] frigate.app INFO : Capture process started for Driveway: 247 [2023-02-24 19:09:05] frigate.app INFO : Capture process started for BackGarden: 251 [2023-02-24 19:09:05] frigate.app INFO : Capture process started for Kitchen: 258 [2023-02-24 19:09:05] frigate.app INFO : Capture process started for TVRoom: 262 [2023-02-24 19:09:05] ws4py INFO : Using epoll [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Any ideas?
  6. Thank you @TimTheSettler, that solved the problem!
  7. That solved it! I had tried 3 different ones so far... You are a legend, thank you very much for your help.
  8. As soon as I changed the proxy, the machine lost all Internet connectivity. Yes, I am running it via "console" of the container.
  9. Also, I am trying the command curl ipconfig.io and it is still timing out without showing the public IP address acquired by the VPN provider. Shouldn't I be getting a response there?
  10. Sorry, I don't know how to configure Chrome to do that
  11. 10.13.88.8 (my PC, if that's what you mean)