activ Posted January 29, 2017 Author Share Posted January 29, 2017 So a manual start works? I've just pushed a new version again with some extra log information that will at least tell us which of the two start lines is used. Quote Link to comment
nexusmaniac Posted January 29, 2017 Share Posted January 29, 2017 So a manual start works? I've just pushed a new version again with some extra log information that will at least tell us which of the two start lines is used. Manual start did work, yeah I've just updated to the latest version (after looking through your latest commits) You've fixed it I think line 34 in "apps/nobody/transmission.sh" solved it, I can restart the container and have Transmission back up and running in seconds Thanks Activ! Quote Link to comment
jedimstr Posted January 29, 2017 Share Posted January 29, 2017 Damn you guys are fast... busy copying and pasting, and then refreshed the thread....nevermind. So yeah, confirming that the latest update fixed it for me as well. Quote Link to comment
activ Posted January 29, 2017 Author Share Posted January 29, 2017 I was hoping that might fix it Hopefully the improvements in the new scripts will make it worth the effort. Sorry it didn't work before and thanks a lot to both of you for helping me troubleshoot. Quote Link to comment
nexusmaniac Posted January 29, 2017 Share Posted January 29, 2017 I was hoping that might fix it Hopefully the improvements in the new scripts will make it worth the effort. Sorry it didn't work before and thanks a lot to both of you for helping me troubleshoot. It did indeed! I haven't actually had a chance to look at the other changes you've made haha - All I saw was updating from binhex, what kinda stuff's changed? Thanks for being an incredibly responsive dev!! Quote Link to comment
activ Posted January 29, 2017 Author Share Posted January 29, 2017 The script updates are for checking that transmission is still running and the vpn is still up. If the transmission process dies it gets restarted and of the vpn goes down it should get reconnected. Quote Link to comment
nexusmaniac Posted January 29, 2017 Share Posted January 29, 2017 The script updates are for checking that transmission is still running and the vpn is still up. If the transmission process dies it gets restarted and of the vpn goes down it should get reconnected. Brill! Good update Quote Link to comment
jedimstr Posted January 29, 2017 Share Posted January 29, 2017 Ditto... great update and thanks for being so responsive! https://www.wpclipart.com/signs_symbol/gesture_mood/thumb/thumbs_up_through_wall_T.png[/img] Quote Link to comment
a_n_d_y Posted January 29, 2017 Share Posted January 29, 2017 I upgraded to the latest and greatest and having problems. The docker container says its running, but I can't access the web UI with PIA VPN enabled. Works fine with it disabled tho. What do you think? ErrorWarningSystemArrayLogin usermod: no changes [info] Env var PUID defined as 99 [info] Env var PGID defined as 100 [info] Permissions already set for /config [info] Starting Supervisor... 2017-01-29 12:25:08,584 CRIT Set uid to user 0 2017-01-29 12:25:08,584 INFO Included extra file "/etc/supervisor/conf.d/transmission.conf" during parsing 2017-01-29 12:25:08,586 INFO supervisord started with pid 16 2017-01-29 12:25:09,588 INFO spawned: 'checkproc-script' with pid 19 2017-01-29 12:25:09,589 INFO spawned: 'start-script' with pid 20 2017-01-29 12:25:09,589 INFO spawned: 'transmission-script' with pid 21 2017-01-29 12:25:09,590 INFO spawned: 'privoxy-script' with pid 22 2017-01-29 12:25:09,594 DEBG 'transmission-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-01-29 12:25:09,594 INFO success: checkproc-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 INFO success: transmission-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-01-29 12:25:09,594 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-01-29 12:25:09,596 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2017-01-29 12:25:09,597 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47465293154064 for <Subprocess at 47465293107640 with name privoxy-script in state RUNNING> (stderr)> 2017-01-29 12:25:09,597 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47465292105776 for <Subprocess at 47465293107640 with name privoxy-script in state RUNNING> (stdout)> 2017-01-29 12:25:09,597 INFO exited: privoxy-script (exit status 0; expected) 2017-01-29 12:25:09,597 DEBG received SIGCLD indicating a child quit 2017-01-29 12:25:09,602 DEBG 'start-script' stdout output: [info] VPN default certs defined, copying to /config/openvpn/... 2017-01-29 12:25:09,603 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2017-01-29 12:25:09,604 DEBG 'start-script' stdout output: [warn] VPN provider remote port incorrect, overriding to 1198 2017-01-29 12:25:09,626 DEBG 'start-script' stderr output: mknod: /dev/net/: File exists 2017-01-29 12:25:09,628 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-01-29 12:25:09,630 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2017-01-29 12:25:09,630 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-01-29 12:25:09,631 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 192.168.1.0/24 via 172.17.0.1 dev eth0 2017-01-29 12:25:09,631 DEBG 'start-script' stdout output: -------------------- 2017-01-29 12:25:09,632 DEBG 'start-script' stdout output: [info] iptable_mangle module not supported, attempting to load... 2017-01-29 12:25:09,633 DEBG 'start-script' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.4.30-unRAID 2017-01-29 12:25:09,633 DEBG 'start-script' stdout output: [warn] iptable_mangle module not supported, you will not be able to connect to Deluge webui or Privoxy outside of your LAN 2017-01-29 12:25:09,644 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-01-29 12:25:09,644 DEBG 'start-script' 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 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9091 -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 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9091 -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 2017-01-29 12:25:09,644 DEBG 'start-script' stdout output: -------------------- 2017-01-29 12:25:09,644 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2017-01-29 12:25:09,652 DEBG 'start-script' stdout output: [info] OpenVPN started Quote Link to comment
activ Posted January 29, 2017 Author Share Posted January 29, 2017 Not sure when you last updated, but I have pushed an update this afternoon that fixed a similar problem. Also: Did you add the extra variables? Please read the posts before and provide similar information if you are still having problem after updating to the current version. Quote Link to comment
a_n_d_y Posted January 29, 2017 Share Posted January 29, 2017 I have the latest and greatest as of 30 minutes ago. My bad, I should've dug back further in the support pages. Didn't realize additional variables needed to be manually added. I guess I thought they'd show up with the update. Anyways, working fine! Thank you! Quote Link to comment
DazedAndConfused Posted January 29, 2017 Share Posted January 29, 2017 I don't believe that is a valid PHP_TZ you set. You will have to google to find the correct names. But, since you are in EST, just set it to America/New_York The new variables worked for me right away. I didn't set the /etc/localtime because I couldn't get it to see that file on unraid, so I just skipped it. Quote Link to comment
commanderbloom Posted February 1, 2017 Share Posted February 1, 2017 I just updated my docker to latest (I believe commits from 3 days ago) and now it will not load properly if I have the VPN on. At first I wasn't seeing any errors, so I turned debug on and then found the following: 2017-01-31 23:48:54,159 DEBG 'start-script' stdout output: [debug] Show name resolution for VPN endpoint nl.privateinternetaccess.com 2017-01-31 23:48:54,240 DEBG 'start-script' stderr output: Error: 2017-01-31 23:48:54,241 DEBG 'start-script' stderr output: error sending query: No (valid) nameservers defined in the resolver 2017-01-31 23:48:54,250 DEBG 'start-script' stdout output: [info] Adding 192.168.123.0/24 as route via docker eth0 2017-01-31 23:48:54,255 DEBG 'start-script' stdout output: [info] ip route defined as follows... What could be causing this? I'm using PIA by the way. Thanks. Quote Link to comment
a_n_d_y Posted February 1, 2017 Share Posted February 1, 2017 I had similar problems, but adding the additional variables required resolved it: https://lime-technology.com/forum/index.php?topic=48899.msg534306#msg534306 Quote Link to comment
commanderbloom Posted February 1, 2017 Share Posted February 1, 2017 I had similar problems, but adding the additional variables required resolved it: https://lime-technology.com/forum/index.php?topic=48899.msg534306#msg534306 Worked like a charm, thanks a ton! Quote Link to comment
nox Posted February 2, 2017 Share Posted February 2, 2017 Need some help. After searching this topic I managed to add the google nameserver, but I still cant connect to my container. What am I missing? usermod: no changes [info] Env var PUID defined as 99 [info] Env var PGID defined as 100 [info] Permissions already set for /config [info] Starting Supervisor... 2017-02-01 16:24:05,767 CRIT Set uid to user 0 2017-02-01 16:24:05,767 INFO Included extra file "/etc/supervisor/conf.d/transmission.conf" during parsing 2017-02-01 16:24:05,771 INFO supervisord started with pid 15 2017-02-01 16:24:06,772 INFO spawned: 'checkproc-script' with pid 18 2017-02-01 16:24:06,774 INFO spawned: 'start-script' with pid 19 2017-02-01 16:24:06,784 INFO spawned: 'transmission-script' with pid 23 2017-02-01 16:24:06,786 INFO spawned: 'privoxy-script' with pid 25 2017-02-01 16:24:06,790 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-02-01 16:24:06,790 INFO success: checkproc-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-01 16:24:06,790 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-01 16:24:06,791 INFO success: transmission-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-01 16:24:06,791 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-01 16:24:06,814 DEBG 'start-script' stdout output: [debug] Environment variables defined as follows 2017-02-01 16:24:06,815 DEBG 'start-script' stdout output: BASH=/bin/bash BASHOPTS=cmdhist:complete_fullquote:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_LINENO=([0]="0") BASH_SOURCE=([0]="/root/start.sh") BASH_VERSINFO=([0]="4" [1]="4" [2]="5" [3]="1" [4]="release" [5]="x86_64-unknown-linux-gnu") BASH_VERSION='4.4.5(1)-release' DEBUG=true DIRSTACK=() ENABLE_PRIVOXY=no EUID=0 ) HOME=/home/nobody HOSTNAME=2a66961648a6 HOSTTYPE=x86_64 HOST_OS=unRAID IFS=$' \t\n' LANG=en_GB.UTF-8 LAN_NETWORK=192.168.1.0/24 MACHTYPE=x86_64-unknown-linux-gnu NAME_SERVERS=8.8.8.8 OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PGID=100 PIPESTATUS=([0]="0") PPID=15 PS4='+ ' PUID=99 PWD=/ SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=2 SUPERVISOR_ENABLED=1 SUPERVISOR_GROUP_NAME=start-script SUPERVISOR_PROCESS_NAME=start-script TERM=xterm TZ=America/Los_Angeles UID=0 VPN_CONFIG=/config/openvpn/ipvanish-US-Chicago-chi-a16.ovpn VPN_ENABLED=yes VPN_PASS=xxxxxxxxxxxxxxxxxxxxxxxx VPN_PORT=1194 VPN_PROTOCOL=udp VPN_PROV=custom VPN_REMOTE=ipvanish-US-Chicago-chi-a16.ovpn VPN_USER=xxxxxxxxxxxxxxxxxxxxxxxx WHITELIST='*.*.*.*' _='[debug] Environment variables defined as follows' exit_code_chmod=0 exit_code_chown=0 [debug] Directory listing of files in /config/openvpn as follows 2017-02-01 16:24:06,822 DEBG 'transmission-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-02-01 16:24:06,857 DEBG 'start-script' stdout output: total 12 drwxrwxrwx 1 nobody users 64 Feb 1 16:23 . drwxrwxr-x 1 nobody users 288 Jan 30 19:48 .. -rwxrwxrwx 1 nobody users 1684 Jan 11 04:15 ca.ipvanish.com.crt -rwxrwxrwx 1 nobody users 21 Feb 1 16:23 credentials.conf -rwxrwxrwx 1 nobody users 467 Feb 1 16:23 ipvanish-US-Chicago-chi-a16.ovpn 2017-02-01 16:24:06,858 DEBG 'start-script' stdout output: [debug] Contents of ovpn file /config/openvpn/ipvanish-US-Chicago-chi-a16.ovpn as follows... 2017-02-01 16:24:06,860 DEBG 'start-script' stdout output: client # Disabled, as we pass this value via env var ;dev tun # Disabled, as we pass this value via env var ;remote chi-a16.ipvanish.com 443 udp resolv-retry infinite nobind persist-key persist-remote-ip ca ca.ipvanish.com.crt verify-x509-name chi-a16.ipvanish.com name auth-user-pass credentials.conf comp-lzo verb 3 auth SHA256 cipher AES-256-CBC keysize 256 tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA:TLS-DHE-DSS-WITH-AES-256-CBC-SHA:TLS-RSA-WITH-AES-256-CBC-SHA 2017-02-01 16:24:06,863 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/ipvanish-US-Chicago-chi-a16.ovpn 2017-02-01 16:24:06,866 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2017-02-01 16:24:06,868 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47628122742584 for <Subprocess at 47628122841672 with name privoxy-script in state RUNNING> (stderr)> 2017-02-01 16:24:06,868 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47628122742440 for <Subprocess at 47628122841672 with name privoxy-script in state RUNNING> (stdout)> 2017-02-01 16:24:06,868 INFO exited: privoxy-script (exit status 0; expected) 2017-02-01 16:24:06,870 DEBG received SIGCLD indicating a child quit 2017-02-01 16:24:06,958 DEBG 'start-script' stderr output: mknod: 2017-02-01 16:24:06,959 DEBG 'start-script' stderr output: / 2017-02-01 16:24:06,959 DEBG 'start-script' stderr output: : File exists 2017-02-01 16:24:06,960 DEBG 'start-script' stderr output: 2017-02-01 16:24:06,994 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-02-01 16:24:07,009 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf [debug] Show name servers defined for container 2017-02-01 16:24:07,010 DEBG 'start-script' stdout output: nameserver 8.8.8.8 2017-02-01 16:24:07,011 DEBG 'start-script' stdout output: [debug] Show name resolution for VPN endpoint ipvanish-US-Chicago-chi-a16.ovpn 2017-02-01 16:24:07,050 DEBG 'start-script' stdout output: ;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 209 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;; ipvanish-US-Chicago-chi-a16.ovpn. IN A ;; ANSWER SECTION: ;; AUTHORITY SECTION: . 86398 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017020101 1800 900 604800 86400 ;; ADDITIONAL SECTION: ;; Query time: 35 msec ;; SERVER: 8.8.8.8 ;; WHEN: Wed Feb 1 16:24:07 2017 ;; MSG SIZE rcvd: 125 2017-02-01 16:24:07,059 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2017-02-01 16:24:07,061 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-02-01 16:24:07,064 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 2017-02-01 16:24:07,065 DEBG 'start-script' stdout output: 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 192.168.1.0/24 via 172.17.0.1 dev eth0 2017-02-01 16:24:07,066 DEBG 'start-script' stdout output: -------------------- 2017-02-01 16:24:07,071 DEBG 'start-script' stdout output: [debug] Modules currently loaded for kernel 2017-02-01 16:24:07,075 DEBG 'start-script' stdout output: Module Size Used by vhost_net 8037 0 tun 16556 2 vhost_net vhost 13029 1 vhost_net macvtap 9551 1 vhost_net macvlan 11993 1 macvtap kvm_intel 142275 0 kvm 268324 1 kvm_intel md_mod 36275 3 xt_CHECKSUM 1271 1 iptable_mangle 1592 1 ipt_REJECT 1457 2 nf_reject_ipv4 2419 1 ipt_REJECT ebtable_filter 1839 0 ebtables 14232 1 ebtable_filter xt_nat 1849 7 veth 4665 0 ipt_MASQUERADE 1213 11 nf_nat_masquerade_ipv4 1865 1 ipt_MASQUERADE iptable_nat 1831 1 nf_conntrack_ipv4 5810 3 nf_nat_ipv4 4327 1 iptable_nat iptable_filter 1528 1 ip_tables 9422 3 iptable_filter,iptable_mangle,iptable_nat nf_nat 9852 3 nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4 bonding 90588 0 x86_pkg_temp_thermal 4669 0 coretemp 5276 0 e1000e 142034 0 i2c_i801 10759 0 i2c_core 18064 1 i2c_i801 ptp 8988 1 e1000e ahci 26003 5 libahci 19067 1 ahci pps_core 5864 1 ptp 2017-02-01 16:24:07,077 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2017-02-01 16:24:07,141 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-02-01 16:24:07,145 DEBG 'start-script' 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 9091 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9091 -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 9091 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9091 -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 2017-02-01 16:24:07,146 DEBG 'start-script' stdout output: -------------------- 2017-02-01 16:24:07,147 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2017-02-01 16:24:07,176 DEBG 'start-script' stdout output: [info] OpenVPN started Quote Link to comment
activ Posted February 2, 2017 Author Share Posted February 2, 2017 The new variables are: STRONG_CERTS NAME_SERVERS PHP_TZ VPN_DEVICE_TYPE I'm pretty sure you are missing a crucial one. Quote Link to comment
binhex Posted February 2, 2017 Share Posted February 2, 2017 The new variables are: STRONG_CERTS NAME_SERVERS PHP_TZ VPN_DEVICE_TYPE I'm pretty sure you are missing a crucial one. hi activ, i think you have a coding issue somewhere, you shouldnt have to do this, there is code in there to set all of the above to defaults if not specified, the worrying thing is it looks like for some reason or another this code is not working for this particular docker, as can be seen by commanderbloom's issue where it didnt switch to default name servers. ahh ive found the issue!, your missing the insertion of the heredoc into the init.sh and thus missing out all the fallback code :-) mine:- https://github.com/binhex/arch-delugevpn/blob/master/setup/root/install.sh - note lines starting 202 yours - https://github.com/activ/arch-transmissionvpn/blob/master/setup/root/install.sh - note its missing :-) thus why any failure to define any of the new env vars bombs the user out. Quote Link to comment
nox Posted February 2, 2017 Share Posted February 2, 2017 I managed to get those in last night. Still no luck. Do I have them in wrong? Log attached. Had too many characters to post. Quote Link to comment
activ Posted February 2, 2017 Author Share Posted February 2, 2017 I would expect to see the new variables in the list of variables in your log, but thay are not there. Think you need to check again. @Binhex: If I get some time this weekend I'll check into it. Thanks. Quote Link to comment
Aran Posted February 3, 2017 Share Posted February 3, 2017 Ok, i updated unraid to 6.2.4 and none of my dockers worked any more. I installed transmissionvpn yesterday but i can't get it to work. I'm still in a learning-process. The new variables are added and i got this: /plugins/dynamix.docker.manager/scripts/docker create --name="activ-transmissionvpn" --net="bridge" --privileged="true" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="*****" -e "VPN_PASS"="*****" -e "VPN_REMOTE"="ippower.zapto.org" -e "VPN_PORT"="1194" -e "VPN_PROTOCOL"="tcp" -e "VPN_PROV"="custom" -e "ENABLE_PRIVOXY"="no" -e "LAN_NETWORK"="192.168.8.0/24" -e "WHITELIST"="192.168.*.*" -e "DEBUG"="false" -e "PUID"="99" -e "PGID"="100" -e "STRONG_CERTS"="no" -e "NAME_SERVERS"="8.8.8.8,8.8.4.4" -e "PHP_TZ"="Europe/Paris" -e "VPN_DEVICE_TYPE"="tun" -p 9091:9091/tcp -p 8118:8118/tcp -v "/mnt/user/Films/":"/data":rw -v "/mnt/cache/appdata/activ-transmissionvpn":"/config":rw activ/arch-transmissionvpn usermod: no changes [info] Env var PUID defined as 99 [info] Env var PGID defined as 100 [info] Permissions already set for /config [info] Starting Supervisor... 2017-02-03 12:22:57,782 CRIT Set uid to user 0 2017-02-03 12:22:57,782 INFO Included extra file "/etc/supervisor/conf.d/transmission.conf" during parsing 2017-02-03 12:22:57,783 INFO supervisord started with pid 20 2017-02-03 12:22:58,787 INFO spawned: 'checkproc-script' with pid 23 2017-02-03 12:22:58,789 INFO spawned: 'start-script' with pid 24 2017-02-03 12:22:58,791 INFO spawned: 'transmission-script' with pid 25 2017-02-03 12:22:58,791 INFO spawned: 'privoxy-script' with pid 26 2017-02-03 12:22:58,794 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-02-03 12:22:58,794 INFO success: checkproc-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-03 12:22:58,794 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-03 12:22:58,794 INFO success: transmission-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-03 12:22:58,794 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-02-03 12:22:58,796 DEBG 'transmission-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-02-03 12:22:58,797 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2017-02-03 12:22:58,797 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47382796251216 for <Subprocess at 47382795261856 with name privoxy-script in state RUNNING> (stderr)> 2017-02-03 12:22:58,797 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47382795772200 for <Subprocess at 47382795261856 with name privoxy-script in state RUNNING> (stdout)> 2017-02-03 12:22:58,797 INFO exited: privoxy-script (exit status 0; expected) 2017-02-03 12:22:58,797 DEBG received SIGCLD indicating a child quit 2017-02-03 12:22:58,799 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/pfSense-TCP-1194-tvpn.ovpn 2017-02-03 12:22:58,820 DEBG 'start-script' stderr output: mknod: /dev/net/: File exists 2017-02-03 12:22:58,822 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-02-03 12:22:58,824 DEBG 'start-script' stdout output: [info] Adding 192.168.8.0/24 as route via docker eth0 2017-02-03 12:22:58,824 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-02-03 12:22:58,824 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 192.168.8.0/24 via 172.17.0.1 dev eth0 2017-02-03 12:22:58,825 DEBG 'start-script' stdout output: -------------------- 2017-02-03 12:22:58,826 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2017-02-03 12:22:58,839 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-02-03 12:22:58,839 DEBG 'start-script' 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 tcp -m tcp --sport 1194 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9091 -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 tcp -m tcp --dport 1194 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9091 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9091 -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 2017-02-03 12:22:58,839 DEBG 'start-script' stdout output: -------------------- 2017-02-03 12:22:58,839 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2017-02-03 12:22:58,843 DEBG 'start-script' stdout output: [info] OpenVPN started root@powernas:~# docker exec -it activ-transmissionvpn ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.2 netmask 255.255.0.0 broadcast 0.0.0.0 ether 02:42:ac:11:00:02 txqueuelen 0 (Ethernet) RX packets 11 bytes 666 (666.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11 bytes 570 (570.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1 (Local Loopback) RX packets 640 bytes 49280 (48.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 640 bytes 49280 (48.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I guess it never connects to the vpn and transmission is not starting. Quote Link to comment
activ Posted February 4, 2017 Author Share Posted February 4, 2017 @aran: You are right, the vpn doesn't connect. Transmission won't start because the vpn isn't connected. Maybe a debug log will give you some more info. Quote Link to comment
Aran Posted February 4, 2017 Share Posted February 4, 2017 Yep, i had to update my keys. Problem solved. Sorry for the wall of text. Quote Link to comment
activ Posted February 5, 2017 Author Share Posted February 5, 2017 A new version is now online that include Binhex's variable checking code, this should fix some issues with forgotten variables. Of course it's still best to just set the variables needed. Quote Link to comment
jmagnusson Posted March 27, 2017 Share Posted March 27, 2017 Has anyone else noticed that there's no log output from Transmission itself in the container's logs? These are the last three lines of the log output from the container. After that it's completely silent. 2017-03-27 21:42:11,743 DEBG 'transmission-script' stdout output: Script started, file is /home/nobody/typescript 2017-03-27 21:42:11,760 DEBG 'transmission-script' stdout output: Script done, file is /home/nobody/typescript 2017-03-27 21:42:11,760 DEBG 'transmission-script' stdout output: [info] transmission started Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.