morethanenough

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by morethanenough

  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)
  12. Thank you @binhex, here's the log. supervisord.log
  13. Bump please. @binhex, is the development/support of this container dead?
  14. Hi all, just facing a problem with PrivoxyVPN that appeared out of the blue. Using Spaceinvader One's video here, I set up MeTube to use PrivoxyVPN when downloading stuff. The system has been working great for a year now. Today, I tried to download another video but MeTube said it cannot connect. I removed and reinstalled both MeTube and Privoxy but still nothing. I am using Mullvad and I created new config files to try, again with no result. I understand that if I open PrivoxyVPN's console and type: curl ipconfig.io this should show me the public IP address as acquired by Mullvad, but the command times out after a while with the error: curl: (28) Failed to connect to ipconfig.io port 80 after 214681 ms: Connection timed out This tells me there is no connection to Mullvan VPN, which is the reason why MeTube won't connect. Here are the logs: 2022-10-16 10:50:36,011 DEBG 'start-script' stdout output: -------------------- 2022-10-16 10:50:36,015 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2022-10-16 10:50:36,032 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2022-10-16 10:50:36,045 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2022-10-16 10:50:36,047 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2022-10-16 10:50:36,049 DEBG 'start-script' stderr output: [#] ip -4 address add 10.67.14.202/32 dev wg0 2022-10-16 10:50:36,056 DEBG 'start-script' stderr output: [#] ip link set mtu 1420 up dev wg0 2022-10-16 10:50:36,059 DEBG 'start-script' stderr output: [#] resolvconf -a wg0 -m 0 -x 2022-10-16 10:50:36,087 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2022-10-16 10:50:36,088 DEBG 'start-script' stderr output: [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 2022-10-16 10:50:36,090 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2022-10-16 10:50:36,091 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2022-10-16 10:50:36,097 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2022-10-16 10:50:36,098 DEBG 'start-script' stderr output: [#] iptables-restore -n 2022-10-16 10:50:36,101 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2022-10-16 10:50:37,216 DEBG 'start-script' stdout output: [info] Application does not require external IP address, skipping external IP address detection 2022-10-16 10:50:37,217 DEBG 'start-script' stdout output: [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment 2022-10-16 10:50:37,218 DEBG 'start-script' stdout output: [info] WireGuard interface 'up' 2022-10-16 10:50:37,284 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2022-10-16 10:50:37,286 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2022-10-16 10:50:38,293 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2022-10-16 10:50:38,300 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 Has something changed? Is there a way to resolve this please?
  15. Hi @ich777 Ok, it seems the issue was indeed with the TPU reaching high temperatures. shutdowntemp0=104800 shutdown_en0=1 shutdowntemp1=104800 shutdown_en1=1 shutdowntemp2=104800 shutdown_en2=1 shutdowntemp3=104800 shutdown_en3=1 Now it's much better as I allowed some more ventilation in the case. 2022-04-13 09:19:44 Coral Temp: 45.80C 2022-04-13 09:19:59 Coral Temp: 45.55C 2022-04-13 09:20:14 Coral Temp: 45.55C 2022-04-13 09:20:29 Coral Temp: 46.80C 2022-04-13 09:20:44 Coral Temp: 47.55C 2022-04-13 09:20:59 Coral Temp: 48.30C 2022-04-13 09:21:14 Coral Temp: 48.55C 2022-04-13 09:21:29 Coral Temp: 49.05C 2022-04-13 09:21:44 Coral Temp: 49.30C 2022-04-13 09:21:59 Coral Temp: 49.55C 2022-04-13 09:22:14 Coral Temp: 49.80C 2022-04-13 09:22:29 Coral Temp: 49.80C 2022-04-13 09:22:44 Coral Temp: 49.80C 2022-04-13 09:22:59 Coral Temp: 50.30C 2022-04-13 09:23:14 Coral Temp: 50.05C 2022-04-13 09:23:29 Coral Temp: 50.05C 2022-04-13 09:23:44 Coral Temp: 49.80C 2022-04-13 09:23:59 Coral Temp: 49.80C 2022-04-13 09:24:14 Coral Temp: 50.05C 2022-04-13 09:24:29 Coral Temp: 49.80C 2022-04-13 09:24:44 Coral Temp: 49.55C 2022-04-13 09:24:59 Coral Temp: 50.05C 2022-04-13 09:25:14 Coral Temp: 49.80C 2022-04-13 09:25:29 Coral Temp: 49.55C 2022-04-13 09:25:44 Coral Temp: 49.80C 2022-04-13 09:25:59 Coral Temp: 49.80C 2022-04-13 09:26:14 Coral Temp: 50.05C 2022-04-13 09:26:29 Coral Temp: 50.05C 2022-04-13 09:26:44 Coral Temp: 49.80C 2022-04-13 09:26:59 Coral Temp: 49.80C 2022-04-13 09:27:14 Coral Temp: 50.05C 2022-04-13 09:27:29 Coral Temp: 49.80C 2022-04-13 09:27:44 Coral Temp: 49.80C 2022-04-13 09:27:59 Coral Temp: 49.80C 2022-04-13 09:28:14 Coral Temp: 50.05C 2022-04-13 09:28:29 Coral Temp: 49.80C 2022-04-13 09:28:44 Coral Temp: 50.30C 2022-04-13 09:28:59 Coral Temp: 49.80C 2022-04-13 09:29:14 Coral Temp: 49.80C 2022-04-13 09:29:29 Coral Temp: 49.80C 2022-04-13 09:29:44 Coral Temp: 50.05C The script works great. I will monitor how things go and get back to you. Thank you for your assistance!
  16. I have a Google Coral M.2 Accelerator A+E key. I don't understand why it would work fine for 4 months and now it started overheating. I don't recall changing something in Frigate. Yes, I'd like to have that script please (and instructions on where to type it if you have them).
  17. Hi @yayitazale I've been running Frigate for the past 4 months and it's been working great. In the last week though, the container stops after 1-2 hours (don't know the timeframe exactly). When I check the Coral TPU Driver, I get this message: I haven't made any changes at all to either Frigate or the cameras themselves. Of course, if I try to restart the container it still crashes because it cannot locate the Coral. The only way to make it work is to restart Unraid. The logs say: Apr 9 23:10:59 SERVER kernel: apex 0000:07:00.0: RAM did not enable within timeout (12000 ms) Apr 9 23:11:12 SERVER kernel: apex 0000:07:00.0: RAM did not enable within timeout (12000 ms) Apr 9 23:11:12 SERVER kernel: apex 0000:07:00.0: Error in device open cb: -110 Apr 9 23:11:23 SERVER kernel: veth540f305: renamed from eth0 Apr 9 23:11:23 SERVER kernel: docker0: port 2(vethcdfa559) entered disabled state Apr 9 23:11:23 SERVER avahi-daemon[4173]: Interface vethcdfa559.IPv6 no longer relevant for mDNS. Apr 9 23:11:23 SERVER avahi-daemon[4173]: Leaving mDNS multicast group on interface vethcdfa559.IPv6 with address fe80::c8e6:35ff:fe10:a4d. Apr 9 23:11:23 SERVER kernel: docker0: port 2(vethcdfa559) entered disabled state Apr 9 23:11:23 SERVER kernel: device vethcdfa559 left promiscuous mode Apr 9 23:11:23 SERVER kernel: docker0: port 2(vethcdfa559) entered disabled state Apr 9 23:11:23 SERVER avahi-daemon[4173]: Withdrawing address record for fe80::c8e6:35ff:fe10:a4d on vethcdfa559. Apr 9 23:28:47 SERVER kernel: hrtimer: interrupt took 13700 ns Apr 10 00:00:43 SERVER emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 10 00:01:34 SERVER emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Any idea what might be causing this and how I can fix it? Is there a way to restart the Coral TPU Driver without restarting Unraid?
  18. Of course I do, that was so silly of me @JonathanM! Everything works now, except for the "curl ipconfig.io" command. Since this isn't working, is there a way for me to check if the download is indeed using the vpn or not?
  19. Thank you @JonathanM. Yes, it is port 8081. Did as you said. Here's the run command for binhex-privoxyvpn updated: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='binhex-privoxyvpn' --net='bridge' --privileged=true -e TZ="UTC" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='vpn_username' -e 'VPN_PASS'='vpn_password' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'SOCKS_USER'='admin' -e 'SOCKS_PASS'='socks' -e 'ENABLE_SOCKS'='no' -e 'ENABLE_PRIVOXY'='yes' -e 'VPN_INPUT_PORTS'='8081' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8118:8118/tcp' -p '9118:9118/tcp' -p '8081:8081/tcp' -v '/mnt/user/appdata/binhex-privoxyvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-privoxyvpn' Same issue. After restarting both containers, I tried the curl command on MeTube's console, but got the same result: /app $ curl ipconfig.io sh: curl: not found /app $ Also, trying to access the WebUI at: 192.168.1.6:8081 192.168.1.6/metube 192.168.1.6:8081/metube None works. When I tried 192.168.1.6/metube it took me to the UNRAID login page (so I think this wouldn't work anyway) Any ideas?