huladaddy

I can't seem to access the webui from outside my lan like I have been able to previously when I have installed sabnzbd on other non-unraid machines. I am able to access the webui of a bunch of other dockers, and I understand the port mapping etc. I just can't access this webui. Is it something to do with the VPN aspect of this docker. Can you please help?

So I've tried: 1. deleting the container and reinstalling 2. deleting the container & image and installing 3. deleting the docker.img and reinstalling the container and even: 4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory and still cannot open the webui!!! What is going on??? Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas? Geez that was a frustrating one to solve... But I did it! You recently made some changes and told us to modify the environment variable like this: LAN_NETWORK 192.168.1.0/24 My network is different, so I typed this by mistake: LAN_NETWORK 192.168.0.1/24 instead of this: LAN_NETWORK 192.168.0.0/24 Can't believe how hard that was to track down. Sorry for wasting your time...

So I've tried: 1. deleting the container and reinstalling 2. deleting the container & image and installing 3. deleting the docker.img and reinstalling the container and even: 4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory and still cannot open the webui!!! What is going on??? Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas? Not without a supervisord.log file :-) 2016-02-11 00:05:53,504 CRIT Set uid to user 0 2016-02-11 00:05:53,514 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2016-02-11 00:05:53,583 INFO supervisord started with pid 1 2016-02-11 00:05:54,586 INFO spawned: 'privoxy' with pid 7 2016-02-11 00:05:54,590 INFO spawned: 'start' with pid 8 2016-02-11 00:05:54,598 INFO spawned: 'webui' with pid 9 2016-02-11 00:05:54,608 INFO spawned: 'deluge' with pid 10 2016-02-11 00:05:54,626 DEBG 'privoxy' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2016-02-11 00:05:54,626 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-02-11 00:05:54,627 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-02-11 00:05:54,627 DEBG 'privoxy' stdout output: [info] checking VPN tunnel local ip is valid... 2016-02-11 00:05:54,640 DEBG 'deluge' stdout output: [info] VPN enabled, configuring Deluge... 2016-02-11 00:05:54,640 DEBG 'deluge' stdout output: [info] checking VPN tunnel local ip is valid... 2016-02-11 00:05:55,030 DEBG 'start' stdout output: [info] VPN is enabled, beginning configuration of VPN 2016-02-11 00:05:55,100 DEBG 'start' stdout output: [info] VPN provider defined as pia [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2016-02-11 00:05:55,193 DEBG 'start' stdout output: [info] Env vars not defined for remote host, port and protocol, will parse existing entries from ovpn file... 2016-02-11 00:05:55,272 DEBG 'start' stdout output: [info] VPN provider remote gateway defined as nl.privateinternetaccess.com [info] VPN provider remote port defined as 1194 [info] VPN provider remote protocol defined as udp 2016-02-11 00:05:55,289 DEBG 'start' stdout output: [info] VPN provider username defined as ######## 2016-02-11 00:05:55,319 DEBG 'start' stdout output: [info] VPN provider password defined as ######## 2016-02-11 00:05:55,460 DEBG 'start' stdout output: [info] Default route for container is 172.17.42.1 2016-02-11 00:05:55,478 DEBG 'start' stdout output: [info] Adding 192.168.0.1/24 as route via docker eth0 2016-02-11 00:05:55,479 DEBG 'start' stderr output: RTNETLINK answers: Invalid argument 2016-02-11 00:05:55,479 DEBG 'start' stdout output: [info] ip route defined as follows... -------------------- 2016-02-11 00:05:55,479 DEBG 'start' stdout output: default via 172.17.42.1 dev eth0 2016-02-11 00:05:55,480 DEBG 'start' stdout output: 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.8 -------------------- 2016-02-11 00:05:55,562 DEBG 'start' stdout output: [info] iptable_mangle module not supported, attempting to load... 2016-02-11 00:05:55,581 DEBG 'start' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.1.17-unRAID 2016-02-11 00:05:55,582 DEBG 'start' stdout output: [warn] iptable_mangle module not supported, you will not be able to connect to Deluge webui or Privoxy outside of your LAN 2016-02-11 00:05:55,732 DEBG 'start' stdout output: [info] iptables defined as follows... -------------------- 2016-02-11 00:05:55,732 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-02-11 00:05:55,733 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-02-11 00:05:55,735 DEBG 'start' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT 2016-02-11 00:05:55,737 DEBG 'start' stdout output: -------------------- [info] nameservers 2016-02-11 00:05:55,738 DEBG 'start' stdout output: nameserver 8.8.8.8 nameserver 8.8.4.4 2016-02-11 00:05:55,739 DEBG 'start' stdout output: -------------------- [info] Starting OpenVPN... 2016-02-11 00:05:55,812 DEBG 'start' stdout output: Thu Feb 11 00:05:55 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015 2016-02-11 00:05:55,812 DEBG 'start' stdout output: Thu Feb 11 00:05:55 2016 library versions: OpenSSL 1.0.2f 28 Jan 2016, LZO 2.09 2016-02-11 00:05:55,812 DEBG 'start' stdout output: Thu Feb 11 00:05:55 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-02-11 00:05:55,848 DEBG 'start' stdout output: Thu Feb 11 00:05:55 2016 UDPv4 link local: [undef] 2016-02-11 00:05:55,848 DEBG 'start' stdout output: Thu Feb 11 00:05:55 2016 UDPv4 link remote: [AF_INET]109.201.152.245:1194 2016-02-11 00:05:55,991 DEBG 'start' stdout output: Thu Feb 11 00:05:55 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this 2016-02-11 00:05:56,467 DEBG 'start' stdout output: Thu Feb 11 00:05:56 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]109.201.152.245:1194 2016-02-11 00:05:58,356 DEBG 'start' stdout output: Thu Feb 11 00:05:58 2016 TUN/TAP device tun0 opened Thu Feb 11 00:05:58 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Thu Feb 11 00:05:58 2016 /usr/bin/ip link set dev tun0 up mtu 1500 2016-02-11 00:05:58,359 DEBG 'start' stdout output: Thu Feb 11 00:05:58 2016 /usr/bin/ip addr add dev tun0 local 10.198.1.6 peer 10.198.1.5 2016-02-11 00:05:58,370 DEBG 'start' stdout output: Thu Feb 11 00:05:58 2016 Initialization Sequence Completed 2016-02-11 00:05:58,372 DEBG 'deluge' stdout output: [info] VPN interface (tun0) ip address format correct 2016-02-11 00:05:58,388 DEBG 'privoxy' stdout output: [info] VPN interface (tun0) ip address format correct 2016-02-11 00:05:58,389 DEBG 'deluge' stdout output: [info] VPN interface (tun0) is UP [info] All checks complete, starting Deluge daemon... 2016-02-11 00:05:58,394 DEBG 'deluge' stdout output: [info] configuring Deluge listen port... 2016-02-11 00:05:58,394 DEBG 'deluge' stdout output: [info] Configuring Deluge listen interface... 2016-02-11 00:05:58,396 DEBG 'privoxy' stdout output: [info] VPN interface (tun0) is UP [info] Privoxy set to disabled 2016-02-11 00:05:58,396 DEBG fd 8 closed, stopped monitoring (stderr)> 2016-02-11 00:05:58,396 DEBG fd 6 closed, stopped monitoring (stdout)> 2016-02-11 00:05:58,396 INFO exited: privoxy (exit status 0; expected) 2016-02-11 00:05:58,397 DEBG received SIGCLD indicating a child quit 2016-02-11 00:05:58,428 DEBG 'deluge' stdout output: [info] Manually setting Deluge listen interface to 10.198.1.6 2016-02-11 00:06:05,489 DEBG 'webui' stdout output: [info] Starting Deluge webui... 2016-02-11 00:06:08,608 DEBG 'deluge' stdout output: [info] Deluge incoming port 41059 2016-02-11 00:06:11,573 DEBG 'deluge' stdout output: [info] PIA incoming port 33882 [info] Deluge incoming port 41059 and PIA incoming port 33882 different, configuring Deluge... 2016-02-11 00:06:12,471 DEBG 'deluge' stdout output: Setting random_port to False.. Configuration value successfully updated. 2016-02-11 00:06:13,351 DEBG 'deluge' stdout output: Setting listen_ports to (33882, 33882).. Configuration value successfully updated.

So I've tried: 1. deleting the container and reinstalling 2. deleting the container & image and installing 3. deleting the docker.img and reinstalling the container and even: 4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory and still cannot open the webui!!! What is going on??? Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas?

So I've tried: 1. deleting the container and reinstalling 2. deleting the container & image and installing 3. deleting the docker.img and reinstalling the container and even: 4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory and still cannot open the webui!!! What is going on??? Took my problem over here https://lime-technology.com/forum/index.php?topic=46447.0. Seems that I may have bad data cable(s) or bad drive(s) on my cache. Replaced the data cable and am preclearing the cache drives again. I'll continue on that other thread for now, since this does not seem related to your containers.

So I've tried: 1. deleting the container and reinstalling 2. deleting the container & image and installing 3. deleting the docker.img and reinstalling the container and even: 4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory and still cannot open the webui!!! What is going on???

ive never seen anything like that before, got no idea what is going on!?, is your docker image file full by any chance?. I was afraid of that. No, the docker image is not full. Over 10 GB free. Any suggestions? Can/should I reinstall the container, and keep my settings/list of torrent downloads? If so, how?

I just had my unRAID machine lock up on me. Couldn't telnet in. Couldn't access the GUIs of any of my dockers, etc. I was forced to hit the reset button on the machine. After the reboot, I am not able to open the Web GUIs of Delugevpn and Sabnzbdvpn. I can open the web guis of my other dockers, and they seem to be running ok... HELP!

Interesting. I'm using Pale Moon. I'll try restarting my browser if I have that problem again...

General question... What should we do about apps like couchpotato that have their own internal updating mechanism... What happens when couchpotato updates itself, then there is a container update? Should we force couchpotato (and others like sickrage, etc.) to not automatically update themselves?

Ah. OK. Seems like the ports are still available from the outside world... they are just mapped one-to-one... 8096 --> 8096 and 8920 --> 8920. Another question, when I set up this new container, I was not able to modify the default host mapping of /mnt, i.e. couldn't change it to /mnt/media... After adding the container, it now appears that I can edit it. Any idea why?

I made this change but my GUI will not come up. I made the same changes to DelugeVPN and had no problems... Nothing interesting in the log other than "ionice binary... NOT found!". Just thought I would report back with the solution to the problem I was having. Turns out that my f#$&!ing docker.img filled up!! That created all kinds of problems. I ended up recreating my docker.img and reinstalling a bunch of containers... Now to research why docker.imgs are filling up... seems like it is a problem for a lot of people...

So what happened to port mappings in the new emby-server docker? Why did they disappear?

Hmm. this privoxy stuff looks interesting. What is involved in getting it running? Just enabling it by changing the environment variable from no to yes? And I don't quite understand what to do if I am running both sabnzbdvpn and delugevpn.

Sorry for being a Docker noob, but I don't really understand the differences between container and template... Do I just apply the update to my container the regular way within the unRAID GUI, or will that not "update the template"?

So, I'm a bit confused. I am not interested in playing with the version that is in testing, but when the new stable version comes out, I would like to get updated. I am currently using the version from here: https://registry.hub.docker.com/u/emby/embyserver/ What will I need to do when the new stable version is released?

I made this change but my GUI will not come up. I made the same changes to DelugeVPN and had no problems... Nothing interesting in the log other than "ionice binary... NOT found!".

Sure. You can certainly get into trouble if you don't know what you're doing! And as I mentioned above, I don't really need to do any of this. The array is working just fine... Different personalities have different needs...

I agree! I have no idea why anyone would ever want to do this! Right. The second reason. I just created my unRAID machine. Copied a ton of stuff off another old NAS, and stuff from elsewhere. Once everything was copied to unRAID, and all my old disks were precleared and added, I ended up with 4 empty disks, and a bunch of nearly full disks, and the data wasn't well organized. Of course, it is just working fine as is, but I wanted to move stuff onto certain disks or groups of disks according to data type, and I wanting unRAID's allocation methods to be involved. So, therefore, I'm moving data, disk by disk, to either new temporary shares, or directly to a new disk. My plan seems to be working just fine. Especially that I just solved an annoyance the rsync was giving me. All good.

Yup. Completely tracking with you. There is a case where moving from a disk to a share is safe, as long as its a different share, such as: mv /mnt/disk1/media/stuff/a /mnt/user/different_share/stuff/

Nope. Not confusing. I am doing something similar. I have made a new, temp share and am moving everything into it, one disk at a time. At the end I will rename the share back to the original.

Thanks gundamguy. That wa exactly my understanding. NO! If you exclude the disk globally it won't be included in any share ... even if it's listed in that share's "Includes" Arg. This is frustrating. I'm quite sure I have a thorough understanding, but then I read your comment and don't understand what you are trying to say. Let me try this. This is what I said in the part that you quoted by me above. If you have this: /mnt/disk1/media/stuff/a /mnt/disk2/media/stuff/b you had better not do this: mv /mnt/disk1/media/stuff/a /mnt/user/media/stuff/ but apparently, what I have read elsewhere, if you exclude disk1 globally, not in media's share settings, then you can do the mv above. So then you say "NO!", but proceed to agree with me, I think?

Ah. I'm not actually wanting to do what I mentioned in the line above that you have bolded. I just cited that as an example of something that I read. Basically, I am just wanting a better understanding of how unRAID works. But I am doing something similar. I am copying files from a single disk to a share. The share I am copying to does not include the source disk and never has. I believe that is completely safe.

I am wanting a better understanding. For instance, I have read that when copying from a single disk to a share that includes that disk, you must exclude that disk globally, and not by just using the individual share settings. There seems to be a difference there. Also, it seems that when I exclude a disk, the files that are contained on that disk are still available through the share. Does the exclusion only apply to writes, but not reads? So I'd like to know if the above is correct, and if there is anything else I should know?

What's the difference between the "Include disks" and "Exclude disks" in the Shares/Share Settings and the "Include disks" and "Exclude disks" in the Settings/Global Share Settings. When do I use one or the other? What do each of them do specifically?