[Support] binhex - DelugeVPN


Recommended Posts

Hey BinHex and averyone else,

 

I am completely new to the whole docker concept so i am trying to learn.

For the obvious reason i was pointed towards arch-delugevpn to have deluge running on a nas where i want all the other apps running not behind a vpn. 

To understand what to do i read through the following info:

 

https://hub.docker.com/r/binhex/arch-delugevpn

 

but reading through this i am left with a few questions.

for now i am running Docker-se 2.0 (19.03.8.r5) on ADM (3.5.2.RAG2) on a Asustor as6102 nas with portainer CE (2.0.0.r01)

i have pulled arch-delugevpn correctly but haven't run it yet (as i'm not sure if i correctly know how). As i dont' wanna mess things up on the NAS i just wanna double check if my train of thought is indeed correct. 

 

so reading through the above link i noticed there is often refered to use with PIA.

Do i assume correctly when i assume PIA stand for private internet access and is a VPN that does use a (similar to) openVPN protocol?

ifso.. i understand i should not use the PIA guidelines as i use surfshark VPN but should still follow the first general usage protocol the text starts with and just adapt that so it is correct for usage with surfsharks openVPN setting and place the unzipped files openvpn config and cert files in the /config/openvpn/ folder? and run the adepted general usage protocol?

 

additionally i found several discussions on adaptations of the copenvpn config file. but i believe this only relates to usage with the next gen pia vpn. is that correct? should i just use the files as supplied by surfshark or should i make some adaptations to is?

 

I hope i am not asking to much obvious questions here, as i said i am really new to this and a bit anxious to mess things up.

 

Thanks ahead for the support! Kind greatings

 

Matthieu.

 

ps: Binhex thanks very much for all you have done! much appreciated, and that beer will come your way and also nice to find a fellow BOTP-er ;)

 

 

 

 

 

 

 

Link to comment
32 minutes ago, spikey1973 said:

Do i assume correctly when i assume PIA stand for private internet access and is a VPN that does use a (similar to) openVPN protocol?

yes and yes

 

33 minutes ago, spikey1973 said:

it is correct for usage with surfsharks openVPN setting and place the unzipped files openvpn config and cert files in the /config/openvpn/ folder? and run the adepted general usage protocol?

yes, just set VPN_PROV to custom

 

33 minutes ago, spikey1973 said:

additionally i found several discussions on adaptations of the copenvpn config file. but i believe this only relates to usage with the next gen pia vpn. is that correct?

yes

 

34 minutes ago, spikey1973 said:

should i just use the files as supplied by surfshark or should i make some adaptations to is?

yes and no adaptions should need to be made

 

34 minutes ago, spikey1973 said:

also nice to find a fellow BOTP-er

nice profile pic 🙂

  • Thanks 1
Link to comment

oke i thought i was ready but now i am running against the issue of actually finding the /config/openvpn/ folder.

 

i assumed it should be located in the root of the ADM (linux based os of my NAS)

there i did indeed find a .config folder of course, but there is no openvpn folder in there.

i tried stopping at all (every container in portainer-ce), but then all that hapend is that my router would reboot.

afterwards there is still no openvpn folder in .config/ so i started to think i should look for it somewhere else, higher up in the file tree.

So i found in the Docker/Deluge folder a /Config, but also without openvpn folder.

 

Al i can think of now is that i should still look for a different location so i tried 'locate openvpn'

or i didn't force the creation of the folder in the right way yet.

 

any thoughts on the above?

 

kind greatings Matthieu

 

 

 

 

Link to comment
1 hour ago, spikey1973 said:

oke i thought i was ready but now i am running against the issue of actually finding the /config/openvpn/ folder.

 

i assumed it should be located in the root of the ADM (linux based os of my NAS)

there i did indeed find a .config folder of course, but there is no openvpn folder in there.

i tried stopping at all (every container in portainer-ce), but then all that hapend is that my router would reboot.

afterwards there is still no openvpn folder in .config/ so i started to think i should look for it somewhere else, higher up in the file tree.

So i found in the Docker/Deluge folder a /Config, but also without openvpn folder.

 

Al i can think of now is that i should still look for a different location so i tried 'locate openvpn'

or i didn't force the creation of the folder in the right way yet.

 

any thoughts on the above?

 

kind greatings Matthieu

 

 

 

 

What do you have programmed into Host Path 1 variable in your container settings (should be where /config is located). 

Host Path1.JPG

Edited by chesh
Link to comment

@chesh:

 

thanks for your reply, i tried looking for that info in Portainer.io but did find no reference to anything named host path (1 or other)

am i looking at the wrong spot? (again)

 

sorry for all this trouble, i feel the closer i seem to get the less i know and understand.

Edited by spikey1973
Link to comment
15 minutes ago, spikey1973 said:

@chesh:

 

thanks for your reply, i tried looking for that info in Portainer.io but did find no reference to anything named host path (1 or other)

am i looking at the wrong spot? (again)

 

sorry for all this trouble, i feel the closer i seem to get the less i know and understand.

Not familiar w/ Portainer, but looking at screenshots, I would think it is in the Container section under the DelugeVPN settings, but I may be way off.

 

Link to comment

any other / better dashboard i can use / you prefer? do keep in mind i am limited to a small amount of apps that is supported by ADM OS.

 

Within Portainer, there is a container section, bu i only have Deluge and PortainerCE in there.

DelugeVPN i have ONLY pulled in, so it is under images, but there, there is still a notification "unused". and i think i can not use it till i have this solved, right?

 

Please see screenshots. 

 

 

 

 

 

Screenshot from 2020-11-05 21-46-00.png

Screenshot from 2020-11-05 21-46-05.png

Link to comment
9 minutes ago, cromwell said:

Is anyone else having trouble with PIA? The container doesn't seem to stay on when connected to PIA. I set ```Container Variable: VPN_ENABLED``` to ```no``` and the container worked just fine...

 

Tried connecting to different servers, but no luck. PIA support is non-existent 

I had 0 problems since moving to Wireguard until a couple of hours ago when I had to restart the container... but it connected just fine and had no problems since. Was getting the "unable to download JSON" or something (I really should keep a note of these before restarting, sorry!)

 

EDIT: Sorry, I should add, I use the rTorrent container now, instead of DelugeVPN, but I figured it was an issue with PIA

Edited by xxDeadbolt
Link to comment
25 minutes ago, cromwell said:

Is anyone else having trouble with PIA? The container doesn't seem to stay on when connected to PIA. I set ```Container Variable: VPN_ENABLED``` to ```no``` and the container worked just fine...

 

Tried connecting to different servers, but no luck. PIA support is non-existent 

See Q19 and Q22 in the FAQ: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to comment

hi PIA user here,

according to Q19, i need to get latest docker image but i dont want the latest and greatest delugevpn, if im understanding correctly.  i want the older version of delugevpn that i run that makes the trackers i am on the most happy.  when clients are too new they get blocked on trackers. 

 

in any case, i keep trying to do the thing i see in Q20 with the multi end points cycling through but every time i start up delugevpn it wipes all but one of the endpoints out leaving it to just a single end point .ovpn file again.

 

ive tried all the next gen stuff and renaming from privacy back to privateinternetaccess and back again and nothing works besides me trial and erroring, one by one, the older ovpn files until one finally connects.  im confused how so many other people are up and running without a hitch on the new servers...

 

 

Link to comment
14 minutes ago, DontWorryScro said:

hi PIA user here,

according to Q19, i need to get latest docker image but i dont want the latest and greatest delugevpn, if im understanding correctly.  i want the older version of delugevpn that i run that makes the trackers i am on the most happy.  when clients are too new they get blocked on trackers. 

 

in any case, i keep trying to do the thing i see in Q20 with the multi end points cycling through but every time i start up delugevpn it wipes all but one of the endpoints out leaving it to just a single end point .ovpn file again.

 

ive tried all the next gen stuff and renaming from privacy back to privateinternetaccess and back again and nothing works besides me trial and erroring, one by one, the older ovpn files until one finally connects.  im confused how so many other people are up and running without a hitch on the new servers...

 

 

You're going to have to use a different docker container then.  The old 1.3x version of the Deluge container doesn't support next-gen servers and the old PIA servers were shutdown on 10/31.  So, you go current w/ Deluge, or you'll have to switch to be able to connect to PIA and use a client that your trackers support.

Link to comment
19 minutes ago, DontWorryScro said:

hi PIA user here,

according to Q19, i need to get latest docker image but i dont want the latest and greatest delugevpn, if im understanding correctly.  i want the older version of delugevpn that i run that makes the trackers i am on the most happy.  when clients are too new they get blocked on trackers. 

 

in any case, i keep trying to do the thing i see in Q20 with the multi end points cycling through but every time i start up delugevpn it wipes all but one of the endpoints out leaving it to just a single end point .ovpn file again.

 

ive tried all the next gen stuff and renaming from privacy back to privateinternetaccess and back again and nothing works besides me trial and erroring, one by one, the older ovpn files until one finally connects.  im confused how so many other people are up and running without a hitch on the new servers...

 

 

I switched to binhex-qbittorrentvpn docker. Doesn't have all the features of Deluge but it'll work for me until the deluge devs get some of the bugs worked out of v2.

Link to comment
1 hour ago, wgstarks said:

I switched to binhex-qbittorrentvpn docker. Doesn't have all the features of Deluge but it'll work for me until the deluge devs get some of the bugs worked out of v2.

There are already later builds of Deluge, but not in the ArchLinux repositories.  I'm running v2.1.1 on my desktop.

Link to comment
10 hours ago, binhex said:

yes, dont touch the port, 1337 is pia's choosen port for wireguard, port 1198 is used for openvpn.

I think this was the prompt I was looking for!  My router has four WAN ports, but only one connection is un-metered.  I'd been trying to work out how to configure a route so that delugeVPN traffic only went to the un-metered port.  I've just set a route for all traffic to a 1337 destination port to go via WAN2 and that seems to be working.

Link to comment
5 minutes ago, wgstarks said:

Just out of curiosity, does it still have issues with trackers failing?

I'm only running it as a thin client, so I wouldn't be aware.

However, I'm not sure what issue you're referring to - I'm not aware of that problem on DelugeVPN.  How would I identify it?

Link to comment
1 hour ago, chesh said:

You're going to have to use a different docker container then.  The old 1.3x version of the Deluge container doesn't support next-gen servers and the old PIA servers were shutdown on 10/31.  So, you go current w/ Deluge, or you'll have to switch to be able to connect to PIA and use a client that your trackers support.

I'm using v.2.0.3.  I just dont want it updating to :latest where it's bleeding edge new before trackers have a chance to whitelist the latest iteration.  So I suppose I don't mean old old.

And though I did read that they shut the legacy servers down on 10/31 I just connected to the old DE-Berlin about an hour ago so maybe they haven't technically pulled the plug yet.

Edited by DontWorryScro
additional info
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.