I've tried running both transmission and deluge on my raspberry pi. Both times fresh install.
I can get it up and running fine, but then after about 1-2 minutes the web server stops responding and I can't access it unless i restart. I know it's not the whole pi crashing as I can still access pyLoad which is also running along with OpenVPN.
I first thought it was the problem of the applications. But now both are having the same problems I feel it is definitely not the application and rather the OS/hardware.
Has anyone had similar and found a fix?
UPDATE
I ran netstat -ano|grep 9091
and got:
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN off (0.00/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52774 ESTABLISHED keepalive (6879.20/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52794 ESTABLISHED keepalive (6879.20/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52776 ESTABLISHED keepalive (6879.20/0/0)
tcp 1123 0 192.168.0.11:9091 192.168.0.80:52888 ESTABLISHED keepalive (6940.61/0/0)
tcp 707 0 192.168.0.11:9091 192.168.0.80:52789 ESTABLISHED keepalive (6879.17/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52790 ESTABLISHED keepalive (6879.17/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:53184 ESTABLISHED keepalive (7104.42/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52775 ESTABLISHED keepalive (6879.14/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:53193 ESTABLISHED keepalive (7124.90/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52784 ESTABLISHED keepalive (6879.14/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52791 ESTABLISHED keepalive (6879.14/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52783 ESTABLISHED keepalive (6879.12/0/0)
tcp 0 0 192.168.0.11:9091 192.168.0.80:52785 ESTABLISHED keepalive (6879.12/0/0)
UPDATE 2 Right I think I've found the issue. It is to do with the openvpn. Once connected for some reason the port is open for a few minutes to LAN traffic before being closed. This however doesn't seem to be the case for pyload which is also running (port 8000)
I think what I need to do is ensure that all outbound traffic (to the WAN) is going over vpn (i.e. tun) but all LAN traffic is not routed through the vpn. To be honest I'm not sure how to do this. I've done a bit of research and came across these iptable rules (Linky), however I'm not sure if they're working and I still can't access port 9091.
iptables --append OUTPUT --destination 10.10.0.102 --protocol tcp --dport 1723 --jump ACCEPT
iptables --append OUTPUT --destination 10.10.0.102 --protocol gre --jump ACCEPT
My understanding of this is this forces all of the WAN traffic over my tun connection and allows port 1723 for the vpn tracker. However, I might be wrong in this. Can anyone help?
tcp.port eq ___ or udp.port eq ___
as the filter, where ___ is the port number, you'll limit the output to stuff coming to or from the server. If you do that, start it, and watch until it fails, there might be a clue. – goldilocks♦ Dec 4 '14 at 0:03icmp or tcp.port eq 9091
), unless you've customized an iptables set up otherwise... – goldilocks♦ Dec 4 '14 at 2:32