booker9587

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by booker9587

  1. I did, also restarted docker afterwards.
  2. I seem to be having an issue accessing the gui from my lan network. I dont see it being added to the iptables, but maybe I shouldn't? My LAN is: 10.0.0.0/24 and I have added that to the config. Here is the log for that portion. 2016-08-22 19:24:52,060 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 10.0.0.0/24 via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 2016-08-22 19:24:52,060 DEBG 'start-script' stdout output: -------------------- 2016-08-22 19:24:52,065 DEBG 'start-script' stdout output: [info] iptable_mangle module not supported, attempting to load... 2016-08-22 19:24:52,067 DEBG 'start-script' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.4.18-unRAID 2016-08-22 19:24:52,067 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 2016-08-22 19:24:52,089 DEBG 'start-script' stdout output: [info] Adding additional incoming port 8081 for eth0 2016-08-22 19:24:52,116 DEBG 'start-script' stdout output: [info] Adding additional outgoing port 8081 for eth0 2016-08-22 19:24:52,126 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2016-08-22 19:24:52,128 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 8888 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8090 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8090 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8081 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8081 -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 8888 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8090 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8090 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8081 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8081 -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-08-22 19:24:52,128 DEBG 'start-script' stdout output: -------------------- [info] nameservers 2016-08-22 19:24:52,129 DEBG 'start-script' stdout output: nameserver 8.8.8.8 nameserver 8.8.4.4 2016-08-22 19:24:52,130 DEBG 'start-script' stdout output: -------------------- If I turn off the vpn, I can get in without any issues but once I enable I cannot get in. Just for reference, i am on the same switch as my unraid server.. my PC is 10.0.0.99/24, server is 10.0.0.6/24 am I missing something within my config? This is just installed via the community plugin a few hours ago, so should be latest build.