Jump to content
binhex

[Support] binhex - DelugeVPN

5786 posts in this topic Last Reply

Recommended Posts

On 2/7/2020 at 11:46 AM, Level1 said:

Hey guys, I'm new to the forums but am absolutely loving the OS so far. I recommend it to every techie I know constantly. As easy as it is to use though, sometimes I run into issues I can't google my way out of which brings me here. I am trying to use the Binhex DelugeVPN with privoxy docker container that Spaceinvader One has the tutorial for. In his tutorial, though, he only sets it up with the PIA provider who is already included in the package. I am trying to use the docker with another service, specifically PureVPN. I have put in my credentials and imported the appropriate crt, key, and ovpn file pointing to the proper credential file. However, I can never actually access the WebUI because the VPN never fully connects. I have tried multiple servers and replaced the URLs in the ovpn file with the ipv4 to circumvent any DNS issues. Nothing works. The log gives me the following error:

 

2020-02-07 02:51:27,870 DEBG 'start-script' stdout output:
Fri Feb 7 02:51:27 2020 OpenSSL: error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md too weak
Fri Feb 7 02:51:27 2020 Cannot load inline certificate file
Fri Feb 7 02:51:27 2020 Exiting due to fatal error

 

I am out of potential solutions. Any suggestions?

I had the same after trying lots of different PureVPN settings ... I ended up forcing the docker to update (docker - advanced - force update), I then replaced all the OpenVPN files ... it kept all the settings and started working again.

Share this post


Link to post
26 minutes ago, tompapajr said:

Good point -- If i specify a location, yes it seems to go to the specified location.  Ideally, I'd like the unpacked data to reside in the torrent's folder.

Really sounds like an issue with the plugin itself rather than the docker container. Might want to post this in the Extractor v2 support thread.

Share this post


Link to post
8 minutes ago, Andy Test said:

I ended up forcing the docker to update (docker - advanced - force update),

fyi that wont of done anything.

 

8 minutes ago, Andy Test said:

I then replaced all the OpenVPN files

this will of been the fix, looks like purevpn have improved their ovpn config and certs so that it now passes openvpn strict checks.

Share this post


Link to post

The python version of the last deluge is:

sh-5.0# python --version
Python 3.8.1
sh-5.0# 

 

So Far all the plugin I have found doesn't support this new version?

I need a RSS plugin does anyone have one working?

As always your support and knowledge sharing is highly appreciated Thanks!

Share this post


Link to post
3 hours ago, casperse said:

The python version of the last deluge is:

sh-5.0# python --version
Python 3.8.1
sh-5.0# 

 

So Far all the plugin I have found doesn't support this new version?

I need a RSS plugin does anyone have one working?

As always your support and knowledge sharing is highly appreciated Thanks!

Questions like this should really be posted in the Deluge forums. Your much more likely to get some sort of answer there since they have threads dedicated to these plugins.

Share this post


Link to post
3 hours ago, casperse said:

The python version of the last deluge is:

sh-5.0# python --version
Python 3.8.1
sh-5.0# 

 

So Far all the plugin I have found doesn't support this new version?

I need a RSS plugin does anyone have one working?

As always your support and knowledge sharing is highly appreciated Thanks!

To help others you can rename the plugin to match the 3.8 python and it will then show up in the deluge UI

BUT IT WILL NOT WORK... so I guess we have to wait for a new version to come out here:

https://bitbucket.org/bendikro/deluge-yarss-plugin/downloads/

 

I can see that others are using the other docker just to get the RSS feed :-)

 

 

Share this post


Link to post

Does anyone else suffer from ballooning memory usage on this container? Eventually it bricks my server.

 

I'm running: binhex/arch-delugevpn:2.0.3-2-01

deluge_graph.JPG

Share this post


Link to post

Is there any "security" difference between the Binhex Deluge and the Binhex rTorrent?

(Only one I can think of is the Space invader IP Block list in Deluge that isn't available in the rTorrent)

But beside that its the same right

 

Share this post


Link to post
28 minutes ago, casperse said:

Is there any "security" difference between the Binhex Deluge and the Binhex rTorrent?

security wise they are both as secure as each other, using the same shared image.

Share this post


Link to post

I had an error where Deluge was using the container disk image for my downloads, thus setting off warnings. Not sure what triggered this change, but when I tried to revert the location to usual <screenshot>, I got a command failed error: Error response from daemon: endpoint with name binhex-delugevpn already exists in network bridge.. Anything I'm missing?

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='REDACTED' -e 'VPN_PASS'='REDACTED' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.86.0/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 
13da363b92fbdc7dcf0b37d926e09828d3f6dd11f05cbf1677321a618df3abcf
/usr/bin/docker: Error response from daemon: endpoint with name binhex-delugevpn already exists in network bridge.

The command failed.

 

2020-02-15_21-50-59.png

Share this post


Link to post
On 2/16/2020 at 5:56 AM, vvolfpack said:

I got a command failed error: Error response from daemon: endpoint with name binhex-delugevpn already exists in network bridge.. Anything I'm missing?

it means you are trying to create a container with the same name as one that already exists, issue the following command on your host and you will no doubt see you already have a container named 'binhex-delugevpn':-

docker ps -a

so delete the old one if you want to create a new container with the same name.

Share this post


Link to post
On 2/15/2020 at 11:32 PM, aLbOsOuLja said:

Is it safe to have docker running with high running privileges in the synology docker for DelugeVPN?

there are no known vulnerabilities that im aware of that use elevated privileges for this container on synology.

Share this post


Link to post
On 2/17/2020 at 3:22 AM, binhex said:

issue the following command on your host and you will no doubt see you already have a container named 'binhex-delugevpn':-

Running the command doesn't show 'binhex-delugevpn' as a container. However, I do see a folder for the container under appdata. Deleting this folder and reinstalling the docker also shows me the same 'command failed' error from before.

 

Attaching my diagnostics file in case it's an error in the docker image itself since delugevpn downloaded items to its diskimage causing it to reach 100% storage.

 

CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS                    PORTS                                                                  NAMES
dd408724d851        binhex/arch-jackett      "/usr/bin/tini -- /b…"   37 hours ago        Up 27 hours               0.0.0.0:9117->9117/tcp                                                 binhex-jackett
9be5e3a09bc8        binhex/arch-sickchill    "/usr/bin/tini -- /b…"   37 hours ago        Created                                                                                          binhex-sickchill
6b116441524c        linuxserver/openvpn-as   "/init"                  38 hours ago        Up 27 hours               0.0.0.0:943->943/tcp, 0.0.0.0:9443->9443/tcp, 0.0.0.0:1194->1194/udp   openvpn-as
dd876d1256e3        linuxserver/duckdns      "/init"                  3 days ago          Up 27 hours                                                                                      duckdns
3aedc50e459c        binhex/arch-plexpass     "/usr/bin/tini -- /b…"   3 days ago          Up 27 hours                                                                                      binhex-plexpass
9c7295b66cb6        binhex/arch-sonarr       "/usr/bin/tini -- /b…"   6 days ago          Exited (0) 3 days ago                                                                            binhex-sonarr
b1fdead365e7        binhex/arch-radarr       "/usr/bin/tini -- /b…"   6 days ago          Exited (0) 38 hours ago                                                                          binhex-radarr
348ae87c462b        binhex/arch-sabnzbd      "/usr/bin/tini -- /b…"   9 days ago          Up 27 hours               0.0.0.0:8080->8080/tcp, 0.0.0.0:8090->8090/tcp                         binhex-sabnzbd
d64832469e44        binhex/arch-krusader     "/usr/bin/tini -- /b…"   10 days ago         Up 27 hours               5900/tcp, 0.0.0.0:6080->6080/tcp                                       binhex-krusader

vvolfbox-diagnostics-20200217-1058.zip

 

Edit 1: After a reboot, the command passes successfully, but I'm unable to start the docker. After clicking "Start". It spins for a second and returns to "Stopped" state. Any help would be much appreciated!

 

 

EDIT 2:

Getting these syslogs from trying to start the application

Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered blocking state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:14 vvolfbox kernel: device veth72bc119 entered promiscuous mode
Feb 18 23:02:14 vvolfbox kernel: IPv6: ADDRCONF(NETDEV_UP): veth72bc119: link is not ready
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered blocking state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered forwarding state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:14 vvolfbox kernel: eth0: renamed from veth7da683a
Feb 18 23:02:14 vvolfbox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth72bc119: link becomes ready
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered blocking state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered forwarding state
Feb 18 23:02:15 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:15 vvolfbox kernel: veth7da683a: renamed from eth0
Feb 18 23:02:15 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:15 vvolfbox kernel: device veth72bc119 left promiscuous mode
Feb 18 23:02:15 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state

Any help would be much appreciated, @binhex!

Edited by vvolfpack
Updating with the latest information

Share this post


Link to post

Is there an issue with PIA? I havent been able to download anything for 2 days. Connection times out.

When I set it to not use VPN, I get super slow speeds and I am on Fiber.

Share this post


Link to post
18 minutes ago, barajas.uriel said:

Is there an issue with PIA? I havent been able to download anything for 2 days. Connection times out.

When I set it to not use VPN, I get super slow speeds and I am on Fiber.

PIA has many different endpoints, try a different one on the port forward enabled list.

Share this post


Link to post
14 hours ago, jonathanm said:

PIA has many different endpoints, try a different one on the port forward enabled list.

I have tried several, they start up, and then the connection times out. Public and private trackers.

Share this post


Link to post
On 2/18/2020 at 9:27 AM, barajas.uriel said:

I have tried several, they start up, and then the connection times out. Public and private trackers.

Did you find a solution? Mine stopped downloading yesterday.  I restarted the docker and now I can't even access the web UI.

Share this post


Link to post

Ok so if I disable VPN it seems to work.  I guess I will try another end point.

Share this post


Link to post

Update: My issue was network-related.  I had enabled a 2nd NIC on my server.  I disabled the 2nd NIC and rebooted the server -.

 

All is well now.  I think I will leave it alone before I create more problems.

 

I have been sailing with Deluge for some time now without issue.  I have VPN enabled in Deluge routing thru Toronto.

 

I rebooted my unraid server today. I am not able to open the Deluge WEBUI without first disabling the VPN. 

 

What is the issue?  This was working fine before I did the re-boot.  I just get the "site cannot be reached" error. Using port 8112.

 

Here is my log:

 

 

2020-02-19 20:39:33,304 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-02-19 20:39:33,305 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-02-19 20:39:33,425 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-02-19 20:39:33,431 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-02-19 20:39:33,436 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-02-19 20:39:33,442 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-02-19 20:39:33,448 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-02-19 20:39:33,454 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-02-19 20:39:33,459 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-02-19 20:39:33,465 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-02-19 20:39:33,471 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-02-19 20:41:33,599 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-02-19 20:43:33,724 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-02-19 20:45:38,847 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-02-19 20:47:43,970 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-02-19 20:49:49,092 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2020-02-19 20:51:54,221 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

 

Then I shut down the Docker and deleted the Config Files in OpenVPN.  Copied the original certificates

back and changed my end point from Toronto to France. Same results in the logfile.

 

Also looking at my Unraid Log I am seeing the following :


Feb 20 07:36:16 MediaTower kernel: docker0: port 4(veth9c959ce) entered blocking state
Feb 20 07:36:16 MediaTower kernel: docker0: port 4(veth9c959ce) entered forwarding state
Feb 20 07:36:16 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state
Feb 20 07:36:17 MediaTower kernel: eth0: renamed from vethde49b44
Feb 20 07:36:17 MediaTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9c959ce: link becomes ready
Feb 20 07:36:17 MediaTower kernel: docker0: port 4(veth9c959ce) entered blocking state
Feb 20 07:36:17 MediaTower kernel: docker0: port 4(veth9c959ce) entered forwarding state
Feb 20 07:38:37 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state
Feb 20 07:38:37 MediaTower kernel: vethde49b44: renamed from eth0
Feb 20 07:38:37 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state
Feb 20 07:38:37 MediaTower kernel: device veth9c959ce left promiscuous mode
Feb 20 07:38:37 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state
Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered blocking state
Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state
Feb 20 07:38:41 MediaTower kernel: device veth55c0157 entered promiscuous mode
Feb 20 07:38:41 MediaTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth55c0157: link is not ready
Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered blocking state
Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered forwarding state
Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state
Feb 20 07:38:43 MediaTower kernel: eth0: renamed from veth37cc761
Feb 20 07:38:43 MediaTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth55c0157: link becomes ready
Feb 20 07:38:43 MediaTower kernel: docker0: port 4(veth55c0157) entered blocking state
Feb 20 07:38:43 MediaTower kernel: docker0: port 4(veth55c0157) entered forwarding state
Feb 20 07:57:51 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state
Feb 20 07:57:51 MediaTower kernel: veth37cc761: renamed from eth0
Feb 20 07:57:52 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state
Feb 20 07:57:52 MediaTower kernel: device veth55c0157 left promiscuous mode
Feb 20 07:57:52 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state
Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered blocking state
Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered disabled state
Feb 20 07:59:46 MediaTower kernel: device vethc3f7b23 entered promiscuous mode
Feb 20 07:59:46 MediaTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethc3f7b23: link is not ready
Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered blocking state
Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered forwarding state
Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered disabled state
Feb 20 07:59:47 MediaTower kernel: eth0: renamed from veth3940a12
Feb 20 07:59:47 MediaTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc3f7b23: link becomes ready
Feb 20 07:59:47 MediaTower kernel: docker0: port 4(vethc3f7b23) entered blocking state
Feb 20 07:59:47 MediaTower kernel: docker0: port 4(vethc3f7b23) entered forwarding state

Edited by a12vman
Additional Information

Share this post


Link to post

Hi! New to Unraid but learning on the way and watching many Youtube guides. Ive just configured DelugeVPN and everything is working fine except for Privoxy. I just want to use Privoxy for my browsing but when i configure my network settings on my mac my internet connection goes down. I think im doing everything right but something is failing. In the log file for the Docker image it says 2020-02-20 20:21:16,883 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

Any ideas on what may be wrong here? 

Share this post


Link to post
4 minutes ago, oskarax said:

Hi! New to Unraid but learning on the way and watching many Youtube guides. Ive just configured DelugeVPN and everything is working fine except for Privoxy. I just want to use Privoxy for my browsing but when i configure my network settings on my mac my internet connection goes down. I think im doing everything right but something is failing. In the log file for the Docker image it says 2020-02-20 20:21:16,883 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

 

Any ideas on what may be wrong here? 

Exactly what settings are you using on your Mac?

Share this post


Link to post
3 minutes ago, wgstarks said:

Exactly what settings are you using on your Mac?

im using the webproxy HTTP and the secure webproxy HTTPS, filling in my host ip and portnumber 8118.

 

When ive done that i have no internet access at all. Just fails to connect.

Edited by oskarax
typo

Share this post


Link to post
4 minutes ago, wgstarks said:

Have you tried another browser?

Ive tried Safari, Chrome and Firefox. Exactly the same on all of them Just tries to connect but after a while fails...

Share this post


Link to post

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.