Running Zeronet using Subgraph

Hi.

I'm trying to run Zeronet on a laptop using [Subgraph OS](https://subgraph.com/), the self-proclaimed _adversary resistant computing platform_. It's an operational system based on Debian and, much like its privacy oriented counterpart Tails OS, it uses what it refers to as a "metaproxy" in order to route all traffic through tor.

I've installed Zeronet following the installation instructions provided for Debian, also, I've downloaded the required dependencies from their official repository. The installation process runs without errors, though ultimately Zeronet fails to launch:
```
user@subgraph:~$ python ZeroNet-master/zeronet.py
- Starting ZeroNet...
[15:07:04] - OpenSSL loaded, version: 0100020CF
[15:07:04] - Version: 0.5.7 r2190, Python 2.7.13 (default, Jan 19 2017, 14:48:08)
[GCC 6.3.0 20170118], Gevent: 1.1.2
[15:07:04] - Creating FileServer....
[15:07:04] TorManager Connecting to Tor Controller 127.0.0.1:9051
^CShutting down...
[15:14:14] - Unhandled exception
None
KeyboardInterrupt
```

I've sought and found attempts to troubleshoot this problem here at [Github](https://github.com/HelloZeroNet/ZeroNet/issues/610) and [Reddit](https://github.com/HelloZeroNet/ZeroNet/issues/610). Though they were experienced by users of Tails. Still, I tried the solution proposed unanimouslyby both treads.

> I have installed Tails in a VM and this one worked for me:
>
> zeronet.py --proxy 127.0.0.1:9050 --tor disable --ui_ip 10.0.2.16 (your ip can be different from this use /sbin/ifconfig to see yours)
>
> Then access using http://10.0.2.16:43110

These are my network interfaces as described by ifconfig:
```
enp2s0: flags=4099 mtu 1500
ether c4:34:8f:ab:db:34 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1 (Local Loopback)
RX packets 99129 bytes 33654317 (32.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 99129 bytes 33654317 (32.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

oz-clear: flags=67 mtu 1500
inet 10.0.1.1 netmask 255.255.255.0 broadcast 0.0.0.0
ether aa:da:88:8d:6e:93 txqueuelen 1000 (Ethernet)
RX packets 25808 bytes 2604749 (2.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35411 bytes 52660576 (50.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vozTJcEyg: flags=67 mtu 1500
ether aa:da:88:8d:6e:93 txqueuelen 0 (Ethernet)
RX packets 18702 bytes 2125764 (2.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 26381 bytes 43486281 (41.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp3s0: flags=4163 mtu 1500
inet 192.168.0.18 netmask 255.255.255.0 broadcast 192.168.0.255
ether 3c:97:0f:79:86:a0 txqueuelen 1000 (Ethernet)
RX packets 73846 bytes 84383411 (80.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 52848 bytes 12957734 (12.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
```
Hence I tried the following command:
```
user@subgraph:~$ python ZeroNet-master/zeronet.py --proxy 127.0.0.1:9050 --tor disable --ui_ip 10.0.1.1
- Starting ZeroNet...
[15:37:47] - OpenSSL loaded, version: 0100020CF
[15:37:47] - Patching sockets to socks proxy: 127.0.0.1:9050
[15:37:47] - Version: 0.5.7 r2190, Python 2.7.13 (default, Jan 19 2017, 14:48:08)
[GCC 6.3.0 20170118], Gevent: 1.1.2
[15:37:47] - Creating FileServer....
[15:37:47] - Creating UiServer....
[15:37:47] - Removing old SSL certs...
[15:37:47] - Starting servers....
[15:37:47] Ui.UiServer --------------------------------------
[15:37:47] Ui.UiServer Web interface: http://10.0.1.1:43110/
[15:37:47] Ui.UiServer --------------------------------------
[15:37:48] FileServer Checking port 15441 using P2P...
[15:37:48] FileServer Checking port 15441 using portchecker.co...
[15:37:52] FileServer [BAD :(] Port closed: Port 15441 is closed.
[15:37:52] FileServer Trying to open port using UpnpPunch...
[15:38:08] FileServer UpnpPunch run error: UpnpError: Failed to communicate with igd using port 15441 on local machine after 3 tries. in FileServer.py line 75 > UpnpPunch.py line 325 > UpnpPunch.py line 316
^CShutting down...
[15:38:37] - Unhandled exception
None
KeyboardInterrupt
```
Still, using both the Tor Browser and the clearnet enabled Chromium, the web interface failed to load. Also, I've checked my router configuration to make sure that it is fowarding port 15441, though I'm not sure if it that's a relevant factor if not for publishing content at the Zeronet.

I tried running the same command modified like so `python ZeroNet-master/zeronet.py --proxy 10.0.1.1:9050 --tor disable`, and I've got a slightly different response from the terminal running the command after the `FileServer [BAD :(]` part:
```
[16:05:51] FileServer [BAD :(] Port closed: Error: GeneralProxyError: Socket error: [Errno 104] Connection reset by peer in FileServer.py line 137 > urllib2.py line 154 > urllib2.py line 429 > urllib2.py line 447 > urllib2.py line 407 > urllib2.py line 1241 > urllib2.py line 1195 > httplib.py line 1042 > httplib.py line 1082 > httplib.py line 1038 > httplib.py line 882 > httplib.py line 844 > httplib.py line 1255 > httplib.py line 821 > SocksProxy.py line 12 > socks.py line 685
[16:05:51] FileServer Trying to open port using UpnpPunch...
[16:06:06] FileServer UpnpPunch run error: UpnpError: Failed to communicate with igd using port 15441 on local machine after 3 tries. in FileServer.py line 75 > UpnpPunch.py line 325 > UpnpPunch.py line 316
^CShutting down...
[16:06:37] - Unhandled exception
None
KeyboardInterrupt
```
Also, while performing these tests, I've had another terminal side-by-side running the command `sudo journalctl -f`. This terminal did not respond to the requests performed by executing `zeronet.py` before. Though, now it did:
```
Sep 04 16:05:44 subgraph sudo[4422]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 04 16:05:50 subgraph fw-daemon[750]: NOTI 21f0 ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45170 -> 10.0.1.1:9050
Sep 04 16:05:50 subgraph fw-daemon[750]: NOTI 21f3 ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45172 -> 10.0.1.1:9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:50 subgraph fw-daemon[750]: NOTI 21f6 ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45174 -> 10.0.1.1:9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:50 subgraph fw-daemon[750]: NOTI 21f9 ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45176 -> 10.0.1.1:9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:50 subgraph fw-daemon[750]: NOTI 21fc ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45178 -> 10.0.1.1:9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:50 subgraph fw-daemon[750]: NOTI 21ff ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45180 -> 10.0.1.1:9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:50 subgraph fw-daemon[750]: NOTI 2202 ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45182 -> 10.0.1.1:9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:50 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:51 subgraph fw-daemon[750]: NOTI 220c ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45198 -> 10.0.1.1:9050
Sep 04 16:05:51 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:51 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:51 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:53 subgraph fw-daemon[750]: NOTI 2212 ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45202 -> 10.0.1.1:9050
Sep 04 16:05:53 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:53 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:53 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
Sep 04 16:05:53 subgraph fw-daemon[750]: NOTI 2216 ALLOW|10.0.1.1:9050 > /usr/bin/python2.7 TCP 10.0.1.1:45206 -> 10.0.1.1:9050
Sep 04 16:05:53 subgraph subgraph-metaproxy[901]: No specific policy for client destination port, using wildcard relay for port: 9050
Sep 04 16:05:53 subgraph subgraph-metaproxy[901]: Opening SOCKS5 relay.
Sep 04 16:05:53 subgraph subgraph-metaproxy[901]: Error dialing SOCKS5 proxy at 127.0.0.1:9050: proxy: SOCKS5 proxy at 127.0.0.1:9050 failed to connect: general failure
[...]
```
It then goes on and on trying different ports to make a TCP connection and failing to do so.

Well. That's it, that's all I know. Any guidance from here will be appreciated.

Thanks!