Burizado
-
Posts
113 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Burizado
-
-
8 hours ago, ionred said:
If this happens, you can cold reset the BMC from the command line from your machine. I'm pretty sure it's
ipmitool mc reset cold
but I could be wrong on that. I've had hte same issue you described with this board before with the BMC login loop and the BMC just needed a reset. Never lost any uptime on the machine itself.
@ionred would you do this from the Unraid terminal session? Also, you mention this can be done while the server is running with no downtime?
-
Yeah, I have a similar issue where the IPMI would just keep going back to the login screen as well. I thought it was something odd in my network setup, but since nothing else seemed to be effected it wasn't high on my priority list to track down.
Sounds like this might be the same as what you both listyed above. I will have to try reflashing next time I take the server down. Thanks for the heads up!
-
56 minutes ago, Mattti1912 said:
Hello again:)
Anyone who know how to get the privoxy working again??
Thanks..
You need to be more descriptive in your question. Post what the symptoms are, your logs (with user and password redacted), what have you tried to resolve the issue, etc.
For me (and I may just be lucky, and I am touching wood right now) this app has been working fine for me through several app/docker updates, and a recent Unraid upgrade from 6.9 to 6.11 (yes I know I was overdue).
I am guessing the common reply is going to be follow the FAQ documents that are linked in Binhex's signature, probably the VPN FAQ based on what it seems you are having issues with.
-
12 hours ago, nickp85 said:
I think I saw something about Plex downloads going entirely into the transcode folder. If you’re doing like 4K HDR stuff bigger than 32GB you’ll blow out the RAM and it won’t work
Don't downloads go to the device you are downloading them on? Like if I was traveling and wanted to download episodes/movies, they would go onto the tablet/phone I am taking with me, not the Plex server.
Am I wrong in my thinking here?
-
12 hours ago, dcarpenter85 said:
When you add Sonarr and Radarr to Prowlarr as 'Apps', wait 5-10 minutes and you should see new Indexers automatically appear in those apps. This happens automatically and seems to be sporadic as far as the amount of time it takes to sync up. When I added Sonarr, it appeared pretty much right away but Radarr took about 10 minutes before finally showing up.
TL;DR: Configure your preferred indexers in Prowlarr. Grab the API keys from Sonarr and Radarr, add them as Apps in Prowlarr. Wait.Thanks! Yeah, I spun up a test Radarr to see how it works, and saw all the Indexers start appearing in Radarr.
So it seems Radarr/Sonarr/Lidarr will use the Indexers defined in their individual apps, but the Indexers are managed by Prowlarr. I like that there is more control over each Indexers individual settings with this setup, and you only have to manage them in 1 app (Prowlarr). Since I have 5 apps to manage the Indexers for it makes it nice to be all in one spot.
-
Firstly, thanks for all your hard work on all your dockers Binhex.
I just installed this Docker and I am trying to understand how it works with Deluge and other the *ARR dockers. If I wanted to use this as my main Indexer, do I need to set anything up in Sonarr/Radarr?
Currently I have Jackett setup in each of the applications as the only Indexer. Do I just delete that in Sonarr/Radarr, and have Prowlarr setup as 'Full Sync' for both applications?
My Sonarr and Radarr dockers are also connected to my Trakt lists as well as my Plex docker. So when new content is added to Sonarr/Radarr via my Trakt lists does Prowlarr just know to look for the missing content?
I guess I'm not understanding how Prowlarr would know to search for the missing content without a connection setup in Sonarr/Radarr, unless it is via the 'Full Sync' connection and it is always looking for changes in those applications (i.e. new content added or missing content found).
So then in my Sonarr/Radarr dockers I would just have the download client, Trakt list, and Plex as my defined connections I am thinking.
-
On 11/22/2021 at 6:39 PM, tjb_altf4 said:
Emby updated overnight, but I had to roll back to 4.6.4.0-3-01 this morning as some (but not all) of my client devices couldn't connect.
I believe this is an emby issue, but I thought I'd give people a heads up incase they face similar issues
Same here. I don't use the docker much (setup as a secondary media docker). I started it after updating, and when I open the WebUI I just get a page with 'Forbidden'. I rolled back to 4.6.4.0-3-01 and the WebUI loads fine. I didn't see any errors in the log with version 4.6.6.0-1-01 or latest.
Not a huge issue for me since as I mentioned this is a secondary docker I have just to test out other media library front ends. Plex is my main media front end. I just wanted to post that I see a similar issue and heads up if anyone else has a similar issue.
-
10 minutes ago, Big Dan T said:
Hi All,
Is PIA down for everyone else too ?
I keep getting:-
Nope. Working fine for me. I am using one of the CA endpoints FYI.
-
8 minutes ago, LTM said:
For those with the startup script errors:
I just redownloaded a configuration file from PIA website, deleted the old one, and restarted Deluge and it seems to have fixed it. It looks to me that they renamed it to exclude the "nextgen-" from the file name. I don't know if that matters.
Do you have a link to the download? I am assuming this is only if you are using the ovpn files and not using Wireguard?
-
Is anyone else seeing any issues with queued up torrents disappearing?
I am noticing this happening every morning when checking my downloads. I did some testing and it seems when Deluge restarts (this occurs everyday due to my nightly backup) it seems to loose all the torrents queued up. Any torrents that have started at least a little download are not removed. Only torrents that have not started downloading anything.
I just noticed this happening after updating Deluge. I was using the new version with the proxy updates from a few weeks ago successfully, and only noticed this after updating late last week sometime.
For reference in my setup I am using 2 Radarr containers, 1 for normal content, and the other exclusively for 2160p content. I do this to keep both versions of a single movie, but in separate directories and libraries in Plex. I don't think the issue is with these applications as I see this occur for both Radarr instances and for Sonarr as well, and they only disappear when Deluge is restarted not Radarr, Sonarr, or Jackett. Radarr, Sonarr, and Jackett are all setup using Deluge as the privoxy.
-
29 minutes ago, RollinDolan said:
So I tried that earlier, but I tried again just to confirm.
There's the start of Q24 from the FAQ...
Here's what I changed my Jackett container to:
- Added the extra parameter as dictated. I assume "binhex-delugevpn" is the VPN container name? If not, I don't know what is.
- Switched Network type to none
- Removed what used to be the first environment variable. It was the port setting, which was previously 9117.
Unfortunately, this results in a failed Docker restart. "The command failed." And then my docker page shows an orphan image where binhex-jackett used to be. So something isn't right.
Thanks for the help so far. I'm eager to go down the path of binding Jackett to the VPN container. However, it seems awfully strange that Jackett literally has a setting for this (which would allow me to tell Jackett to just use privoxy), and we're unable to do that anymore...
The SpaceInvader video did not delete the port variable. I'm not sure if that makes a difference. I know it is contrary to what the instructions specify. -
26 minutes ago, MothyTim said:
Why is it not accurate??
It is not accurate because some, like myself, have privoxy working successfully with the Deluge upgrade. You have to make some changes to the settings namely adding your network range to the 'Ignored Addresses' but it does work.
I agree there are some bugs, and I do see the privoxy restarting in the logs as well, but that does not mean it is not working. I am also hoping for a fix for any bugs, and Binhex has posted that they are being worked on (at least the ones that can be replicated).
Adding captures of my setup to hopefully help anyone that needs to get privoxy working.
Deluge Docker Settings:
Radarr Settings:
Sonarr Settings:
Jackett Settings:
-
1
-
-
55 minutes ago, MothyTim said:
Hi, so a few hours of reading and trying things out leads me to think that privoxy is broken!
This is not accurate. I have everything still running under the privoxy setup. The change that is needed though is you need to add your network IP range into the 'Ignored Addresses' parameter in Radarr/Sonarr. There is not an option in Jackett for this that I found.
For reference I tested the new setup routing Jackett/Radarr/Sonarr through Deluge but Radarr and Sonarr are unable to communicate with containers outside the VPN, mainly Plex in may case. I did not want to run my Plex container through Deluge, but I am assuming it might work if you did that. Also I run 2 containers of Radarr and the new setup did not like having 2 of the same container running through Deluge.
-
17 hours ago, Ericjr said:
I have deluge up and running with the new version. Sab/Radarr/Sonarr can all communicate and I changed everything to local host and added the additional ports. All good. I run curl they all come out of the VPN. Containers are connected to Deluge with --net=container:Delugevpn. I saw some other posts but no resolution on how to get Radarr/Sonarr to talk to plex for media updates that are not running through a VPN. I would prefer not to have plex run through the VPN. Any advice out there?
My solution to this is to keep running the privoxy until a solution is developed. You can do this with the new version of Deluge, you just need to add your network IP range to the 'Ignored Addresses' parameter in Radarr/Sonarr.
-
1
-
-
4 hours ago, storagehound said:
Looking at my logs I am seeing this as well.
2021-02-26 18:45:14,261 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...
2021-02-26 18:45:15,272 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...
2021-02-26 18:45:15,278 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118
2021-02-26 18:45:45,335 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running
I see the same in my logs and I am setup to use the privoxy in Deluge, with Radarr/Sonarr/Jackett all setup to use it. I am assuming they are using it but I don't know of a way to test if they are actually using it. I think Jackett is the only container that truely is going outside my network as Radarr and Sonarr I think just connect within my network.
-
1 hour ago, abisai169 said:
Here is my dilemma. Up until the latest update I was running Radarr and Sonarr through DelugeVPN without issue. Both Radarr and Sonarr were able to communicate with my Plexserver (Host Network) and NZBGet (Bridge Network). After this recent update things broke.
I was able to fix things enough that I could communicate with the WebUI for for both Radarr and Sonarr. However, I still can't communicate from Radarr/Sonarr to my Plexserver or NZBGet. I have zero desire to run either of these through the VPN. How can I maintain communication between all the containers running through deluge and the ones that don't?
This is the reason I decided not to run my Radarr/Sonarr/Jackett directly through my DelugeVPN container and continue to use the privoxy within the applications. You can still do this you just need to add your network to the 'Ignored Addresses' parameter in the Proxy section of the app. There are details some posts above that I found helpful, but I can post screens if needed.
Another reason I am not running them directly through the VPN container is I saw an issue when running 2 versions of Radarr with this setup. I think because the internal port on my 2nd Radarr is still 7878 in the application settings even though the WEBUI container port is 7879.
Overall I would like to run the containers without the potential leaks described that pushed this update/fix but as long as I can stay on an updated version and still have everything working I am happy. I say that until a potential leak causes a major issue of course. 😄
-
I got it to work thanks to Spaceinvader's Video and the VPN FAQ Instructions Q24 at the bottom. Essentially I followed the video, added the 'ADDITIONAL_PORTS' variable, and then just updated the settings inside Radarr for example to be 'localhost' for Download Clients (Deluge) and Indexers (Jackett).
One thing I am noticing is that the containers I change will not connect to Plex Media Server any more. This makes sense since all the dockers using the VPN have an IP address outside my network now, when I use 'curl ifconfig.io' in their consoles. For those that have this setup working, do you have an issue with containers not connecting to others not using the VPN?
This is my setup for Plex in Radarr, under the Connect settings. I could route my Plex container through the VPN but then I am guessing anything I direct play will go out through the VPN and back to my TV.
-
32 minutes ago, storagehound said:
I think I got it.
Yes! I think I stumbled on it too, then I came here and saw your post.
I remember SpaceinvaderOne had a video similar to what was being described and found the video you linked.
Putting that together with the steps in Q24 on the VPN FAQ doc helped too.
What's not mentioned in the video or FAQ is I had to change my downloader entry in Radarr to 'localhost'.
-
2 hours ago, jpcom said:
I had same trouble with update done today. Tried to read few pages here and nothing worked. Finally rolled back to 2.0.4 dev38 and its golden again...
Just curious, how do you go about rolling back to the previous version?
I looked through the Github and Dockerhub for the information, but not finding it.
-
Sorry for the barrage of questions.
I also setup my Windows 10 VM to use the DelugeVPN connection by setting it up according to Spaceinvader's video. Is there a way to route the VM through the DelugeVPN with this new update? I was not sure if I needed to add a port to the 'ADDITIONAL_PORTS' var and if so what port.
Image from Internet Options > Connections tab > LAN settings inside my Win 10 VM.
-
8 hours ago, binhex said:
IMPORTANT:- As part of the tightening up if you run multiple containers through a single vpn container then please ensure you define all web ui ports (if more than 1 port then use comma to separate) for all routed containers in 'ADDITIONAL_PORTS' env var for the vpn container.
I ran the manual force update. I am not seeing the 'ADDITIONAL_PORTS' var in the docker config in unRAID, but I did see it in the logs when I started Deulge. Do we need to add it manually in the unRAID config for the docker, or specify it in the 'Extra Parameters' section?
-
6 minutes ago, binhex said:
works for me and @JimmyGerms 🙂
make sure you specify the container side port number as well, NOT the host side port, as you are talking directly within the same network.
Is this only for the new updated Deluge setup?
I was trying to use 'localhost' before I updated Deluge and I get an error, but when I specify the IP 192.168.0.178 it tests good. I understand what you are saying about it being inefficient, and would like to make it more so. The screens show my setup in Radarr. It doesn't show in the bottom option in the download client setup, but I don't have 'Use SSL' checked.
-
1 hour ago, binhex said:
IMPORTANT:- As part of the tightening up if you run multiple containers through a single vpn container then please ensure you define all web ui ports (if more than 1 port then use comma to separate) for all routed containers in 'ADDITIONAL_PORTS' env var for the vpn container.
Thank you for your continued work on this docker!
If I am understanding correctly, I will need to add the port for the WebUI of the other dockers that are using my Deluge docker VPN (Privoxy?) into the 'ADDITIONAL_PORTS' variable, correct?
So if I am running your Jackett (9117), Radarr (7878), and Sonarr (8989) dockers as different ports on the same IP I would add the ports these are on into the variable separated by a comma (9117,7878,8989).
-
On 5/10/2020 at 2:32 PM, Armed Ferret said:
I ended up fixing it. I had to do the following:
Bridge mode was enabled but in Settings > Docker "Host Access to custom networks" was disabled.
So I needed to stop the docker service and enable that.
.....
After that I was able to see the br0 interface.
This was the key for me. THANK YOU! Docker is up and running successfully now.
Intel Socket 1151 Motherboards with IPMI AND Support for iGPU
in Motherboards and CPUs
Posted · Edited by Burizado
@Hoopster Thanks for the info! I don't have a test Unraid server, but I could load up one of my RasPis and probably do it from there, if it doesn't work directly on my server. I'll give it a try once I have my server in a quiet time, in case something goes horribly wrong. 😅