DaSlinky

Just had to hard cycle my unraid machine, was notified one of my dockers was unresponsive. Tried to http and ssh to the machine, nothing. What logs and where do I start looking to see what happened? In the few years I've had this machine this is the first time I've had to bounce it like this.

When I go to load a .torrent file it fails. I sent the file to a buddy that has qBittorrent that's a standard windows app install and it works w/out issue.

How would one configure inbound OpenVPN connections to route through their Deluge Privoxy?

I have a win10 VM as my daily driver and use it for games so speed is somewhat a consideration. Would it be a huge issue to have domain set to PREFER (lose redundancy I assume) or should I have it set to YES (hope it crashes while on the array). I've considered just copying the image over to the array on a weekly basis. Is this even an issue as all my files / docs/downloads are stored on the array and I'd just have to install a base os and remap to them.

Funny enough. I bounced the entire server and it works now... 🤣. How does one close a topic?

Been using my Windows VM for several months w/out issue. Tonight it stuttered then I lost my mouse. After I killed the VM session and started it back up my AMD sound was no longer being detected by Windows. Its passed through, just not there in Device Manager or anywhere else. Anyone have this happen?

What's a good supported APC UPS for Unraid? I'm not looking to power the server throughout the night just 10-15 minutes enough for it to shutdown safely.

A reboot resolved the docket error. Lost all my VMware sessions but the images are still there at least. When I got off create a new image it threw the screenshot below. After I cycled the vm manager it tossed the liberty message. tower-diagnostics-20210318-0740.zip

This just started for me this morning. None of my vms will boot so I cycled the vm service and got this error message. seeing this recurring statement in logs, also attached system diag. tower-diagnostics-20210318-0723.zip

@binhex I moved all my ports from 6000 to 8088, still didn't work. There was an update to the container and I pushed it down. Now everything works! Seems funny that I still access Jackett on the native 9117 IP vs 8088. Not even questioning it though!

**I was getting restricted port on ios, so i moved it to 8088** added the additional ports variable, verified the key was proper, have 9117, 8088 I also have 9117, 8088 as VPN_INPUT_PORTS VPN_OUTPUT_PORTS is blank/empty added additional port JACKETT, container port 9117, host port 9117 connection type TCP

@theGrok Did you get it to work? I still can't get to my Jackett on :6000.

I tried my HP laptop, iPad, MacBook(intel) and a win10 VM from unraid machine itself(daily driver) on the 192.xxx network. Same thing. Tempted to send you vpn credentials so you can work on it directly [emoji1787] Sent from my iPhone using Tapatalk

So... out of freaking curiosity I did a route print and enclosed it. It did not work but I'm VPN'd into my home network (at this time) being assigned a 172.x.x.x address. 192.168.128 is my address scheme at the office. 172.27.224.9 is my VPN address into my home network, that is set to be the 192.168.1.x Just got home have 192.168.1.155 as a local address... still no UI when i goto 192.168.1.159:6000 😅 UPDATE! Not the best of news, but at this stage Sonarr / Deluge / Jackett are all talking to each other. The big rip is I can't see the Jackett webUI. Of all things I guess that's the LEAST of my worries, I'd rather not have to monkey with the port/network parameters to do a full reconfigure.. but once that's done its done? I hope you're still game to get the webUI working, I am 😁

sh-5.1# iptables -S -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -s 138.199.27.241/32 -i eth0 -j ACCEPT -A INPUT -s 138.199.27.221/32 -i eth0 -j ACCEPT -A INPUT -s 138.199.27.231/32 -i eth0 -j ACCEPT -A INPUT -s 138.199.27.232/32 -i eth0 -j ACCEPT -A INPUT -s 138.199.27.212/32 -i eth0 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9117 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 9117 -j ACCEPT -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -d 138.199.27.241/32 -o eth0 -j ACCEPT -A OUTPUT -d 138.199.27.221/32 -o eth0 -j ACCEPT -A OUTPUT -d 138.199.27.231/32 -o eth0 -j ACCEPT -A OUTPUT -d 138.199.27.232/32 -o eth0 -j ACCEPT -A OUTPUT -d 138.199.27.212/32 -o eth0 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9117 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 9117 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT sh-5.1#

Not to create a tangent, I would have to do this for Sonarr to talk to Jackett then? restarted and went to 192.168.1.159:6000 no web interface. ServerConfig.json

Done, Should I do something for VPN OUTPUT ports?

Please and Thanks BinHex

Configured the the ENV VAR as a VARIABLE as shown above, the Jackett entry as well, browse to http://192.168.1.159:6000 and nothing. Shutdown the array and rebooted the entire system (someone said that worked for them), same thing.

I see you stressing the ENV VAR pretty hard. In my earlier Deluge build I had the Additional Ports already supplied, apparently in the one from last night its no longer there. I need to add this as a VARIABLE and not a PORT with the below settings. I have Jackett PORT entry as Contrainer Port: 9117, HOST PORT 6000 Additional Entry as below. Save/apply all settings Start DelugeVPN, validate its getting different IP Start Jackett, validate its getting the same IP as Deluge No WebUI option

Trust me, been over that more times then <insert explicative>. I think its a knowledge barrier on my part. I went and removed the 9117 in Jackett. I leave the WebUI line alone or pull that out because the instructions in A24 say to remove all the ports. I was thinking those were 3 separate entries. They're to be two entries? One for all the container ports (additional_ports, multiple) and a single entry per container, like the one below. This will route the traffic within the Deluge VPN and over to Jackett?

I orphaned my DelugeVPN last night... so I'll have to recreate this. So i'm clear can you validate that the Jackett settings are correct above and I'll be doing the following to the DelugeVPN container. Creating the following ports in Deluge. Variable name in caps. ADDITIONAL_PORTS: this will have whatever ports I need to forward. 9117 for Jackett. This can/will house multiple ports. HOST PORT: Pick some random unused port (is there a range?) Is this what is used for the WebUI? This is a single or can house multiple ports. CONTAINER PORT: This has to match the container that's being routed. Assuming a new one to be created for each routed container. I owe you a few beers come payday BinHex!

@mbc0 What was your issue and how did you resolve it? Just curious because i'm having a hell of a time getting my WebUIs on the containers to work.

BUMP, I'm getting the same issue. about had kittens when I looked at mine. checked the sensor, rebooted, still off. Mine normally reports in ~30°C Please Fix

I've gone through all the setting, but for the life of me I cannot find where to do this from Q/A 25. Everything appears to be wanting to route through the VPN, but there's no WebUI on my dockers now.