[[Support] binhex - DelugeVPN]

2 hours ago, binhex said:

yeah i too have been playing with the alternative way of generating a token and it does seem more stable, so i have made the change for both port assignment and also wireguard, as both require tokens and both are failing, one failing when connecting to 10.0.0.1 and the other failing when connecting to metadata server on certain endpoints, so it def still does look like a pia outage of some type here, but the alternative method of hitting https://privateinternetaccess.com/gtoken/generateToken, seems to be working ok so i have switched over to that, just generating a test image now...

 

edit - ok test went well, new prod image built, please pull down and try at your convenience.

Looks good so far! THANKS!

[[Support] binhex - DelugeVPN]

10 minutes ago, wgstarks said:

You might try this- https://deluge.readthedocs.io/en/latest/intro/01-install.html

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.

 

[[Support] binhex - DelugeVPN]

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

 

[[Support] binhex - DelugeVPN]

24 minutes ago, binhex said:

This could be the cause i have done no testing around pause/resume of a container, i have no idea what order the processes will resume in, and it is potentially possible that the deluge process may resume before iptables rules are re-written. The problem is i dont really see an easy way to do any checks for this to prevent it from occurring, so it maybe either really difficult or just plain impossible, i will have to have a think about it.

 

i can do some digging into this and try and replicate the issue, but obviously for now this would be my top culprit and therefore i would not recommend pausing and resuming of this particular container, instead perform a docker stop and start to ensure proper startup order is performed.

Will do. Thanks very much!

[[Support] binhex - DelugeVPN]

4 minutes ago, binhex said:

Do you use sonarr/radarr etc? If so have you configured these to use a proxy?

Sent from my EML-L29 using Tapatalk
 

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.

[[Support] binhex - DelugeVPN]

 

 

 

2

2 hours ago, binhex said:

that should not be possible, there is a blocking script in place that prevents deluge from running until a valid ip is shown against the tunnel adapter, unless this happens deluge cannot start.

 

if you have the supervisord.log file for the period then please attach it here. or pm me it.

 

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.

[[Support] binhex - DelugeVPN]

1 hour ago, strike said:

I'm sorry, I'm not trying to be an ass, but sounds like BS to me. How do you know it's not working? Since you asked how you could check for IP leakage I'm guessing you don't have the knowledge to do so yourself? So what changed between your first and second post? Did you read up on how to use wireshark or something and actually test it? And I find it very unlikely that between your docker backup this morning and the supposed leakage you got some letter from your ISP delivered to you by express mail (or a drone maybe). Because how else would you know it was an IP leak when you don't know how to test it? If my assumption is wrong I apologize, but your story sounds like total BS to me. If not,  you surely have some proof of your theory?  

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.

[[Support] binhex - DelugeVPN]

8 minutes ago, binhex said:

Documentation link in op, see VPN faq its answered in there.

Sent from my EML-L29 using Tapatalk
 

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?

[[Support] binhex - DelugeVPN]

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