David Woods

Looks good so far! THANKS!

DIdn't help Still getting the following error The following packages have unmet dependencies: deluge : Depends: python3-libtorrent (>= 1.1.1) but 1.0.11-1~xenial~ppa1.1 is to be installed E: Unable to correct problems, you have held broken packages.

Is v2 of the gui available for ubuntu? I can't seem to install it.

Will do. Thanks very much!

Yes I do, and No they aren't using a proxy, but the notice email clearly said that the protocol was bittorrent and deluge is the only bittorrent client I have running.

So I pilled my supervisord.log and was reading it over for this morning and it looked... odd. It looked like the full startup script didn't run. So I went back to my scripts and realized that I didn't fully shut down the container. Instead, I just paused and unpaused it, and it was when I unpaused it that the leak happened. I'll send you a private message with my logs from last night and this morning so you can have a look.

Unfortunately true. Apparently, Canada's notice and notice system is so streamlined that they can send out emails within minutes/hours. I was suspicious too but I validated the email was indeed from my ISP, the IP they had was mine and the time lined up exactly with the end of my backup.

Ok that's what I thought. Well I'm here to say it's not working. This morning I shutdown my containers to perform a backup. When I switched the containers back on it appears that for a very brief time deluge was up and accessing the internet without the VPN. I know it's not supposed to but it appears it did. Any idea how that could have happened?

Hello, I recently had an IP leak incident. I'm just trying to figure out how it happened so it doesn't happen again. Did you implement a leak prevention mechanism that shuts off torrents if the VPN goes down? If so is there a way I can test it? Thanks