TombRaider

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

1 Neutral

About TombRaider

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed
  1. Each ipt torrent has three tracker addresses aka announce urls. This is all I could find. https://ssl.empirehost.me/*hash*/announce https://localhost.stackoverflow.tech/*hash*/announce https://routing.bgp.technology/*hash*/announce
  2. 0) I have been running your DelugeVPN container for years but am in the process of switching to qBt, so currently both containers are in use. Both behind a VPN. 1) I am not sure if I understand you correctly but there are no special rules for the ipt tracker. Globally, qBt is set to TCP only (I read that uTP could cause problems within VPN tunnels) and the listening port is the same that is forwarded on AirVPN. This port has been additionally entered into the config file as per your example config: port_range = 49400-49400 port_random = no 2) While performing this step, I realized t
  3. Strange. I can reproduce the leak though as you can see in the screenshot. This is the same torrent listed twice immediately after booting. It could be a problem with IPT in general as the deluge container returns "error: host not found (non-authoritative), try again later". The Deluge torrents aren't shown at all on IPT. Maybe the containers are interfering somehow? Btw, are we supposed to bind the network interface to tun0 under advanced settings or wouldn't make that any difference?
  4. This morning, I noticed what I think is an IP Leak. On IPT in the active torrents section, all torrents seeded with the qBT container are listed twice. One entry is attached to my real IP address while the other one is the AirVPN address. Can you tell from the log why this is?
  5. Hi there, this might be strange, but yesterday I installed the qbittorrent VPN and everything seemed fine. However, now I cannot access the deluge webUI anymore as the password "deluge" does not work. What can I do? Edit: It turned out there is no password set at all. Just hit enter and it worked.
  6. Hi guys, turns out I got a little rusty when it comes to these containers. I've copied a couple of commands from my working Deluge container just so you know. What's the 6881 port used for again? If it is the listening port for qbt, then should it be changed to the port that was forwarded on AirVPN? There is an entry in the qBittoreent.conf that reads Connection\PortRangeMin=6881, so I wonder wheteher it is needed if I have to add the port range manually anyway. Another issue is that the WebUI is showing /config/qBittorrent/downloads/ as the standard download
  7. Can anyone say why AUTH failed? edit: AirVPN seems to have some problems. Connection working again.
  8. Have you added the port when you tried accessing the WebGUI? http://localhost:8112
  9. Edit: Again, I solved the problem on my own. Hate it when that happens What I did was to replace the ovpn file with a newly created one. I don't why this works but maybe someone finds a hint in the log. Anyone else having problems with privoxy and torrents? I can't find any errors in the logs but privoxy doesn't seem to work at all. Websites do not load when accessed through it. On top of that, all connections to different trackers get canceled in Deluge (Operation canceled). The VPN is working though.
  10. Edit: SOLVED , but I'll leave it here in case someone runs into the same problem. You can use either command and just use your container ID. You may need to add sudo in front of it. @binhex There is a bug affecting me on the latest docker version that will be fixed in the next one. https://github.com/docker/for-linux/issues/211 https://github.com/moby/moby/issues/36145 There's a workaround for now but I don't know how to change the command to my needs. Below are two examples the docker dev has given but they look different and I'm a noob. docker-conta
  11. It is because the AirVPN client "Eddie" is just an OpenVPN wrapper and it refuses to open an second instance of OpenVPN as long as the one from the container is running. I don't know if it's impossible to run 2 processes of OpenVPN or if it's an unfortunate programming choice. Edit: Nevermind, upated the client to the latest beta and it works now with two instances of OpenVPN.
  12. Thank you. That would have helped me a lot if the problem hadn't already solved itself. The VPN is working again. I didn't do anything. I extended my VPN subscription a couple of days ago, so maybe there was an issue on their end, but it seems to be fixed now. Nice to see that the firewall works so well. I got two more questions if you don't mind. Do you have any plans to make a QBittorrent+VPN+Privoxy image? Is it correct and intended that the container starts an instance of OpenVPN on my host? This prevents me from using the VPN client software a
  13. Hi, after months of the container running perfectly I encountered a problem today. I cannot access sites through privoxy anymore and torrents aren't working either. The container is up and running and below is an excerpt from a container log. I can spot an AUTH error towards the end. Is the VPN not working and the IP-tables FW blocking any traffic? 2017-11-29 13:02:15,671 DEBG 'start-script' stdout output: [warn] OpenVPN process terminated, restarting OpenVPN... 2017-11-29T12:02:15.671445530Z 2017-11-29 13:02:15,679 DEBG 'start-script' stdout output: We
  14. You need to download the AirVPN_US-Atlanta....ovpn file again but this time untick the box that splits it into 5 files. This way the singele file contains all the data you need. The strange thing is that by default the file won't get seperated, so it looks like you have ticked this option under advanced settings in the config generator. When done copy this new file into the openvpn folder and delete all the other files.
  15. I've got another question With the container running I see two additional network interfaces, i.e. docker0 which is self-explaining and one veth59exxx which supposedly represents the VPN tunnel. My small network usage widget, which tracks all interfaces, shows a constant downloading stream of roughly 500Kib/s despite me not downloading anything. Is this the container talking to the host or should I be worried? Again, this is on a Linux host with no unRAID installed.