[Support] binhex - DelugeVPN


Recommended Posts

Dear Binhex,

 

I am kind of lost finding a solution, and I am most grateful if you find time to help me. I want to run b-nzbget and b-radar thru b-delugevpn. Delugevpn is running and I can connect to WebUI. Nzbget is running, no log error. But I can not connect to WebUI, "server:6789". 

 

Binhex-radar is running and I can connect to WebUI. Testing indexer and download clients = ok, but downloads and media library do not work. 

 

Setup pictures are attached. Happy for any help.

 

Cheers,

 

Frode

b-delugevpn setup 1.png

b-delugevpn setup 2.png

b-nzbget setup.png

b-radar setup.png

Link to comment

Is there a way to specify which PIA server to use? My firewall blocks many countries, and I've had connections issues with port forwarding inside this docker as a result. Would like to choose a server in the whitelist...

 

Link to comment
2 hours ago, ainuke said:

Is there a way to specify which PIA server to use? My firewall blocks many countries, and I've had connections issues with port forwarding inside this docker as a result. Would like to choose a server in the whitelist...

 

You specify the server by which ovpn file you place in the openvpn folder.

 

340620140_ScreenShot2021-03-25at6_31_39PM.png.d502306a48767ec6516a9ab5eb926989.png

 

In this example I'm connected to the Czech Republic server.

Link to comment
1 hour ago, wgstarks said:

You specify the server by which ovpn file you place in the openvpn folder.

 

340620140_ScreenShot2021-03-25at6_31_39PM.png.d502306a48767ec6516a9ab5eb926989.png

 

In this example I'm connected to the Czech Republic server.

OK, thanks. I'm running the Wireguard version. Is there a like setting for that?

 

Link to comment
1 hour ago, ainuke said:

OK, thanks. I'm running the Wireguard version. Is there a like setting for that?

 

Hmmmm, OK. In the "Wireguard" folder in AppData, the conf file shows "ca-toronto.privacy.network:1337" for the endpoint, which is the server I'd have picked anyway...

Is that static, or does it change when restarted? I don't recall ever setting that, but maybe I did. 😕

Link to comment
Hmmmm, OK. In the "Wireguard" folder in AppData, the conf file shows "ca-toronto.privacy.network:1337" for the endpoint, which is the server I'd have picked anyway...
Is that static, or does it change when restarted? I don't recall ever setting that, but maybe I did. 

It’s static. Can’t remember what the default one is, but you can change it to whichever supported endpoint you wish and it should persist from that point.


Sent from my iPhone using Tapatalk
  • Like 1
Link to comment

 

NOTE:  I posted this in the binhex-qbittorrent thread as well.  This one gets more traffic but if I get to an answer in either I'll post the update in both for others who may run across the issue in the future.

 

I finally had the chance to set this and the binhex-qbittorent containers for evaluation as they're the last major containers I wanted I'd not gotten around to yet.  Most everything looks good, but whenever I launch either container I get this in the logs:

 

Warning: `/config/wireguard/wg0.conf' is world accessible

 

I've seen some people include that in their log captures here, but I've not found the resolution.  I thought that deleting perms.txt and restarting the containers would address, but the behavior is the same. Whether I delete perms.txt or leave it as be, it changes the 600 permissions I'd set on the file manually back to 755.  Can someone help me resolve this?

Link to comment

Currently using DelugeVPN with a few containers networked through it.

 

I have noticed that when I'm outside my network and using the wireguard vpn plugin to access my server, DelugeVPN and all containers routed through it are inaccessible via their respective webUIs. Not sure if I missed something in the FAQ or on here.

 

Any ideas?

Link to comment
1 hour ago, drpeppershaker said:

Currently using DelugeVPN with a few containers networked through it.

 

I have noticed that when I'm outside my network and using the wireguard vpn plugin to access my server, DelugeVPN and all containers routed through it are inaccessible via their respective webUIs. Not sure if I missed something in the FAQ or on here.

 

Any ideas?

I have the same issue, except with PIA as a stand-alone VPN Docker. Haven’t tracked it down as it isn’t a big issue for me, but I’ve wondered if it’s an artifact of the tunneling. Although I didn’t have this issue when I was running VPN and NZBGet + ‘arrs on a standalone pi. 

Edited by ainuke
Clarity
Link to comment
On 3/26/2021 at 7:22 AM, BurntOC said:

 

NOTE:  I posted this in the binhex-qbittorrent thread as well.  This one gets more traffic but if I get to an answer in either I'll post the update in both for others who may run across the issue in the future.

 

I finally had the chance to set this and the binhex-qbittorent containers for evaluation as they're the last major containers I wanted I'd not gotten around to yet.  Most everything looks good, but whenever I launch either container I get this in the logs:

 


Warning: `/config/wireguard/wg0.conf' is world accessible

 

I've seen some people include that in their log captures here, but I've not found the resolution.  I thought that deleting perms.txt and restarting the containers would address, but the behavior is the same. Whether I delete perms.txt or leave it as be, it changes the 600 permissions I'd set on the file manually back to 755.  Can someone help me resolve this?

 

Is this not a security concern? Nothing to be concerned about?

Link to comment

I was at one point able to install plugins by dropping them in /config/plugins for the docker, but as of a month or so ago the plugins (including previously installed ones) do not show up in the preferences > plugin list

 

what's going on and how can I install them? They're listed as enabled in core.conf

 

specifically i'm trying to (re)install SimpleExtractor, here https://github.com/d8ahazard/deluge-extractor

 

UMASK 002

 

sh-5.1# ls -l
total 2108
-rw-rw-r-- 1 nobody users  220498 Mar 12 08:03 LabelPlus-0.3.2.4-py3.8.egg
-rw-rw-rw- 1 nobody users 1934881 Oct  2 22:29 SimpleExtractor-1.4-py3.8.egg

 

 

Solved: Removing the python version from the file name let them show up

Edited by sage2050
Link to comment
On 3/17/2021 at 8:58 AM, mcjfauser said:

Hi, as of recently none of my torrents will download. They all show a status of permission denied, timed out, or host not found. I use BINHEX - PRIVOXYVPN. 

 

I have not changed any settings in any containers recently.

 

image.thumb.png.d57829431660fa9ca86a184744e8d413.png

 

Anyone have any ideas? 

Link to comment
29 minutes ago, mcjfauser said:

Anyone have any ideas? 

You shouldn't need a proxy address if you have the vpn enabled.

In my system, proxy setting is set to none

 

The reason it no longer works is due to tightening of networking rules in the docker for better security, I would look at the stickied FAQ post if you want to retain the proxy.

Edited by tjb_altf4
Link to comment

WebAPI Plugin for Organizrv2

Ok, so let's figure this out if we could. I've looked over the forums and the general consensus is that the WebGUI add plugin doesn't and won't work. Meh, whatever. But to manually add it:

  • Download WebAPI-0.4.0-py3.7.egg (or one of the variants)
  • Place in (assuming SpaceInvader One's setup guide) appdata/binhex-delugevpn/plugins/
  • Restart the Connection Manager/Daemon
  • ....
  • Profit.

However, these instructions don't seem to work for at least myself, but also a bunch of folks in this thread.

 

Vital info:

  • Deluge 2.0.4.dev38
  • binhex/arch-delugevpn (no version specified, updated today)
  • Python 3.9.2 (default, Feb 20 2021, 18:40:11) 
  • unRAID 6.9.1

 

I've tried eggs:

None of these seem to work by loading or by dropping them into the directory and restarting the docker. Manually expanding the egg files and adding the folders to the plugins/ dir also doesn't seem to do anything.

 

Most places also remind us to update binhex-delugevpn/core.conf to include the Plugin:
Note "WebAPI" added to enabled_plugins

 

   "download_location_paths_list": [],
    "enabled_plugins": [
        "LabelPlus",
        "AutoAdd",
        "Scheduler",
        "WebAPI"
    ],
    "enc_in_policy": 1,
    "enc_level": 1,
    "enc_out_policy": 1,
    "enc_prefer_rc4": true,
    "geoip_db_location": "/usr/share/GeoIP/GeoIP.dat",
    "ignore_limits_on_local_network": false,
    "info_sent": 0.0,

 

Some posts have mentioned restarting the Daemon to initialize the plugin, however, 1) wouldn't it no longer be activated after a docker restart?, and 2) Don't know about anyone else, but if I select the Daemon in Connection Manager and hit "Stop Daemon" I get an error message window that just says "An error Occurred" so... womp womp.

 

Meanwhile, back at Google...

 

My old buddies at OpenMediaVault (it was good at the time, but I'm soooooo glad I made the switch omg) are also struggling with adding plugins to deluge. I found a few posts that outline getting AutoRemovePlus-0.6.2-py3.7.egg to work, so I followed those (more or less the same as above, adding the egg to the plugins dir) to make sure it wasn't just the WebAPI egg itself. Sadly, no joy.  I know it's a few years old now but SpaceInvader One's plugin vid also doesn't help with this.

 

dev.deluge-torrent.org appears to have gone offline while I was typing this, so that's not ideal. But if anyone has an idea of how to enable plugins I'd appreciate some pointers.

If nothing else, perhaps I could request @binhex include the WebAPI plugin in the build? Given the number of requests it seems like it might be a well received addition ¯\_(ツ)_/¯ 

 

---------------------------------------- WORKING! ----------------------------------------

 

Right, welp, got it working though good, old fashioned, luck. There's a github support thread here: https://github.com/idlesign/deluge-webapi/issues/27 that got me going on the right path.

 

Basically, you need to download the plugin linked here: https://github.com/idlesign/deluge-webapi/files/4458994/WebAPI-0.4.0-py3.8.zip

 

And then rename the file to "WebAPI-0.3.9-py3.9.egg" then copy it into your config/appdata/binhex-delugevpn/plugins/ directory. Also expand it as if it were a zip file, the folder should be named "WebAPI-0.3.9-py3.9" by the expanding software. I don't know if it's the egg, the folder, or both that deluge wants to see, but I also don't care cause it's working.

 

You do need to add "WebAPI" to the binhex-delugevpn/core.conf as seen above. Make sure to mind your commas! Now reboot the docker and, hopefully, you'll see WebAPI available in Settings > Plugins and can activate it. Once activated it will have a settings item in the left list, click on that and check Enable CORS. Now go back over to Organizrv2 and in the Deluge Home settings enter the [ip]:[port] of your deluge instance using the password that you use for the webUI (as best as I can tell this doesn't work if you don't have a pw set).

 

Hope this helps folks in the future :D

Edited by DrPeril
FIXED!
  • Thanks 1
Link to comment

HELP!

 

I was trying to get binhex-couchpotato to connect through binhex-delugevpn once again.  I made edits as described in Q24, but couldn't find the 'VPN_INPUT_PORTS' env var.  I believed that I had to delete the delugevpn container and re-install it, and tha this would pick up my old settings again.

However, now when I go to the unRAID 'Docker' page I simply see a never-ending hourglass and there is no delugevpn showing.

 

Oh, and binhex-couchpotato always says 'rebuilding' under the version column.

 

What do I need to do to get delugevpn back (with all my settings)?

 

Edit:

I managed to get into couchpotato settings and blank the 'Extra Parameters'.  This seems to have fixed the hourglass problem.

I now seem to be in a position to re-install delugevpn with my original settings ....  I will carry on and see where I get to .......

 

Further Edit:

Ah, but I still don't have VPN_INPUT_PORTS ....  still stuck ....

 

... and no, I don't have a container version specified in the repository.

Edited by PeterB
Add INPUT_PORTS still missing ...
Link to comment

I've had some problems with the DelugeVPN container over the last couple of days.

 

I've deleted the container, and remove all the folders from the appdata folder on my cache drive, but now i'm not able to reinstall the container.

I get this error everytime:

 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='*********' -e 'VPN_PASS'='*********' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'LAN_NETWORK'='10.19.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 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -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/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn'

52ef2014dc334a437adaec89ae0cb562c81962cc0fa16325c69a9c24bfc0b68f
docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn (a0a045454e1034a49b03d548adfbf21ac8d75286ba4e3a6a6af9fc0767af2926): Bind for 0.0.0.0:58946 failed: port is already allocated.

The command failed.

 

I havn't changed anything on my server or my network, but all of a sudden the DelugeVPN Container stopped working - and I've not been able to get it up and running again, I've then tried the Container called: "delugevpn flexget" and it works fine, but I've used the Binhex container for over a year, without any problems - so fare..

 

Can anyone help me out here, i would really like to get back to the Binhex container, especially because the one I currently use. is marked as BETA in the Community Apps section...

 

Looking forward to hear from somebody / anybody, that might have a solution for my issue.... Thanks....

Edited by m-zone.me
Link to comment
10 hours ago, m-zone.me said:

0.0.0.0:58946 failed: port is already allocated.

This is the issue, so you have a container that is already using port 58946, you need to fix this conflict, either by stopping the other container or by changing the host port on this container to something else.

Link to comment

This may be a dumb question but using the wireguard option is there any way to get DelugeVPN to cycle through different endpoints? I've noticed that some trackers may not work with a selected endpoint (maybe ip ban?) but if I reconnect with another I pick back up. Would there be a way for a refresh or cycle of the endpoints?

 

Reading the faq, the openVPN config may support this but only if the connection has trouble making the handshake?

Link to comment

I see a few folks have commented on ProtonVPN.  I was able to get it hooked up by simply dropping in the openVPN file from the ProtonVPN site.  It's pretty slow - at least compared to my former torrenting solution (using an old PC with Windows and qbittorrent while running the VPN client in the background.)  Both use ProtonVPN as the main VPN source, but the WIndows PC with App was about 10 times faster when tested on the Ubuntu torrent.  I keep reading that port forwarding may be part of the issue.  Has anyone else who follows this setup Deluge ProtonVPN and had better results, or have any general tips I may be missing?

Link to comment

I updated my DelugeVPN docker container awhile back and Sonarr/Radarr will no longer connect when the VPN is turned on within the DelugeVPN container settings. I can connect to the DelugeVPN docker webui just fine with the VPN feature enabled, but Sonarr/Radarr cannot reach it unless the VPN feature is turned off. Please help. I don't want to be unprotected!



Does anyone know how to fix this?
 

Link to comment

I am also having issues with my deluge

 

I just check it and it looks like it hasn't been running for the pass few days.

I am using this version: binhex/arch-delugevpn:latest

my VPN still works

webGUI = This site can't be reached

 

can anyone see why this has started to happen or do I need to look at the first sticker post about IP Leakage

 

Update: .  I just look at the IP Table Q&A and I am loss 

I route my Sonarr, Radarr, Jackett through delugeVPN so I am guesting that I need to look at Q27

and as I am using delugevpn I will need to add the following to the other contactors ?

VPN_OUTPUT_PORTS = 58946

 

I am also having issue with access the GUI to conform that my VPN is working so I am looking at Q25 and this is where I am confused,  can someone please help me on working this all out.

 

docker settings.

image.thumb.png.a13771f7c8a5a3b4bd37c06f1f4a786b.png

image.thumb.png.b72bf81731590a09a9368513c323e366.png

image.png.3d620bb286c56e50961f41e4c1036da0.png

 

 

I just check my log and I see the following:

 

Quote

ErrorWarningSystemArrayLogin


Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2021-04-05 12:11:55.700673 [info] System information Linux 859703cf2409 5.10.21-Unraid #1 SMP Sun Mar 7 13:39:02 PST 2021 x86_64 GNU/Linux
2021-04-05 12:11:55.793621 [info] OS_ARCH defined as 'x86-64'
2021-04-05 12:11:55.849878 [info] PUID defined as '99'
2021-04-05 12:11:56.128027 [info] PGID defined as '100'
2021-04-05 12:11:56.475175 [info] UMASK defined as '000'
2021-04-05 12:11:56.501982 [info] Permissions already set for volume mappings
2021-04-05 12:11:56.642497 [info] Deleting files in /tmp (non recursive)...
2021-04-05 12:11:56.705187 [info] VPN_ENABLED defined as 'yes'
2021-04-05 12:11:56.731401 [info] VPN_CLIENT defined as 'openvpn'
2021-04-05 12:11:56.755344 [info] VPN_PROV defined as 'pia'
2021-04-05 12:11:58.179578 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/France.ovpn
2021-04-05 12:11:58.297423 [info] VPN remote server(s) defined as 'france.privacy.network,'
2021-04-05 12:11:58.319084 [info] VPN remote port(s) defined as '1198,'
2021-04-05 12:11:58.341266 [info] VPN remote protcol(s) defined as 'udp,'
2021-04-05 12:11:58.366489 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-04-05 12:11:58.390604 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-04-05 12:11:58.417269 [info] LAN_NETWORK defined as '192.168.1.0/24'
2021-04-05 12:11:58.443578 [info] NAME_SERVERS defined as '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'
2021-04-05 12:11:58.469414 [info] VPN_USER defined as '************'
2021-04-05 12:11:58.494452 [info] VPN_PASS defined as '*********************'
2021-04-05 12:11:58.521431 [info] STRICT_PORT_FORWARD defined as 'yes'
2021-04-05 12:11:58.546511 [info] ENABLE_PRIVOXY defined as 'yes'
2021-04-05 12:11:58.580302 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2021-04-05 12:11:58.605468 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2021-04-05 12:11:58.634693 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2021-04-05 12:11:58.660404 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2021-04-05 12:11:58.687270 [info] Starting Supervisor...
2021-04-05 12:12:02,140 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2021-04-05 12:12:02,141 INFO Set uid to user 0 succeeded
2021-04-05 12:12:02,167 INFO supervisord started with pid 6
2021-04-05 12:12:03,169 INFO spawned: 'shutdown-script' with pid 186
2021-04-05 12:12:03,170 INFO spawned: 'start-script' with pid 187
2021-04-05 12:12:03,171 INFO spawned: 'watchdog-script' with pid 188
2021-04-05 12:12:03,172 INFO reaped unknown pid 7 (exit status 0)
2021-04-05 12:12:03,208 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2021-04-05 12:12:03,209 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-05 12:12:03,209 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-05 12:12:03,209 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-05 12:12:03,275 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2021-04-05 12:12:03,278 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2021-04-05 12:12:03,283 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2021-04-05 12:12:03,288 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2021-04-05 12:12:03,292 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2021-04-05 12:12:03,297 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2021-04-05 12:12:03,302 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2021-04-05 12:12:03,306 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2021-04-05 12:12:04,263 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2021-04-05 12:12:04,265 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.10.21-Unraid

2021-04-05 12:12:04,265 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2021-04-05 12:12:04,267 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2021-04-05 12:12:04,267 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'

2021-04-05 12:12:04,267 DEBG 'start-script' stdout output:
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2021-04-05 12:12:04,802 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2021-04-05 12:12:04,881 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2021-04-05 12:12:04,888 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2021-04-05 12:12:04,890 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2021-04-05 12:12:04,892 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4
192.168.1.0/24 via 172.17.0.1 dev eth0

2021-04-05 12:12:04,892 DEBG 'start-script' stdout output:
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.4
local 172.17.0.4 dev eth0 table local proto kernel scope host src 172.17.0.4
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.4
--------------------

2021-04-05 12:12:05,408 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2021-04-05 12:12:05,410 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 84.17.60.211/32 -i eth0 -j ACCEPT
-A INPUT -s 84.17.60.212/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 84.17.60.211/32 -o eth0 -j ACCEPT
-A OUTPUT -d 84.17.60.212/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2021-04-05 12:12:05,412 DEBG 'start-script' stdout output:
--------------------

2021-04-05 12:12:05,413 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2021-04-05 12:12:05,830 DEBG 'start-script' stdout output:
2021-04-05 12:12:05 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.

2021-04-05 12:12:05,830 DEBG 'start-script' stdout output:
2021-04-05 12:12:05 WARNING: file 'credentials.conf' is group or others accessible
2021-04-05 12:12:05 OpenVPN 2.5.1 [git:makepkg/f186691b32e68362+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 24 2021
2021-04-05 12:12:05 library versions: OpenSSL 1.1.1j 16 Feb 2021, LZO 2.10

2021-04-05 12:12:05,830 DEBG 'start-script' stdout output:
2021-04-05 12:12:05 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2021-04-05 12:12:05,831 DEBG 'start-script' stdout output:
2021-04-05 12:12:05 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----


2021-04-05 12:12:05,831 DEBG 'start-script' stdout output:
2021-04-05 12:12:05 TCP/UDP: Preserving recently used remote address: [AF_INET]84.17.60.212:1198
2021-04-05 12:12:05 UDP link local: (not bound)
2021-04-05 12:12:05 UDP link remote: [AF_INET]84.17.60.212:1198

 

 

 

 

 

 

 

 

 

Edited by chris_netsmart
updated log file
Link to comment
11 hours ago, chris_netsmart said:

2021-04-05 12:12:04,263 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2021-04-05 12:12:04,265 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.10.21-Unraid

2021-04-05 12:12:04,265 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2021-04-05 12:12:04,267 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2021-04-05 12:12:04,267 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
 

 

It says in your logs why you are unable to access it through the web browser. You should reference Q2 in the below documentation to make it persist through reboot. Just be sure you have your "LAN_NETWORK" variable correctly identified in the container. Also, you should change your PIA password, it's in the logs.

 

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to comment
On 4/1/2021 at 2:53 AM, PeterB said:

HELP!

 

I was trying to get binhex-couchpotato to connect through binhex-delugevpn once again.  I made edits as described in Q24, but couldn't find the 'VPN_INPUT_PORTS' env var.  I believed that I had to delete the delugevpn container and re-install it, and tha this would pick up my old settings again.

However, now when I go to the unRAID 'Docker' page I simply see a never-ending hourglass and there is no delugevpn showing.

 

Oh, and binhex-couchpotato always says 'rebuilding' under the version column.

 

What do I need to do to get delugevpn back (with all my settings)?

 

Edit:

I managed to get into couchpotato settings and blank the 'Extra Parameters'.  This seems to have fixed the hourglass problem.

I now seem to be in a position to re-install delugevpn with my original settings ....  I will carry on and see where I get to .......

 

Further Edit:

Ah, but I still don't have VPN_INPUT_PORTS ....  still stuck ....

 

... and no, I don't have a container version specified in the repository.

You can download the app again from the APPS tab and just point the config path to your last Deluge appdata folder. It will overwrite your old template as long as it is named the same. You should have the VPN_INPUT_PORTS and VPN_OUTPUT_PORTS variables in the template again. You can also just add the variables to your template, as long as the you have the VPN_INPUT_PORTS and VPN_OUTPUT_PORTS as the "Key" and your ports as the "Value".

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.