@ Walter:

 

thank you for your help!!

 

these are screenshots of portainers.io i made when ssh to my nas from my laptop on the same LAN.

looking back at the screenshots i can not find how you concluded it is on my cache drive though (understanding this would probably be very helpfull not?)

 

did you find it back in the "containers" or the " images" screenshot?

 

kind regards.

Edited November 13, 20205 yr by spikey1973
addition

3 minutes ago, spikey1973 said:

@ Walter:

 

thank you for your help!!

 

these are screenshots of portainers.io i made when ssh to my nas from my laptop on the same LAN.

looking back at the screenshots i can not find how you concluded it is on my cache drive though (understanding this would probably be very helpfull not?)

 

kind regards.

The screenshot shows that you have set /config to host path /mnt/cache/appdata/delugeVPN. This would mean that the docker has created a folder named delugeVPN at location cache/appdata/. The path to your OpenVPN folder would be /mnt/cache/appdata/delugeVPN/openvpn/ on an UnRAID system. Not sure how portainer accesses your drives.

@ Walter

 

ah that screenshot, no that is a screenshot posted as an example by Chesh on page 291, as that is where it is located on his system.

that is what i am tring to find on my system.

 

i did post 2 screen shots though.. a little bit further on, also on page 291 but i will post them here again. but i doubt this gives any information except a possible tab inside portainer the info should be.

 

sorry for the confusion, i should've been more clear.

 

Matthieu

 

 

 

 

 

Hey guys, I'm seriously loving this software, but after rebooting my machine this morning, I began to have issues. Right now I'm unable to access the web GUI and both Sonarr and Radarr aren't connecting either. Here is a portion of my log:

2020-11-13 15:33:25,644 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-11-13 15:33:25,986 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-11-13 15:33:30,436 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-11-13 15:33:35,235 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (32560, 32560)
Configuration value successfully updated.

2020-11-13 15:33:40,132 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2020-11-13 15:33:40,132 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2020-11-13 15:33:40,133 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

I'm hoping someone has encountered this before and I've just simply overlooked something.

50 minutes ago, spikey1973 said:

 

i did post 2 screen shots though..

That is the LSIO deluge container. Since I’m guessing you aren’t running it on an UnRAID server (and this is an UnRAID forum) you should seek support in the LSIO discord. This thread is for a different container.

54 minutes ago, Scroopy Noopers said:

I'm hoping someone has encountered this before and I've just simply overlooked something.

That doesn’t show any problem. You should attach the supervisord.log to your next post.

11 minutes ago, wgstarks said:

That doesn’t show any problem. You should attach the supervisord.log to your next post.

My mistake. Here it is.

supervisord.log

On 11/13/2020 at 12:32 PM, ThaPear said:

Hi I've been trying to get this set up on my Synology NAS with NordVPN.
However, it's not starting the Deluge interface but is also not giving me any clear errors.
It works just fine when I set VPN_ENABLED to 'no'.
I have given it a /config and /data folder, and placed both the TCP and UDP configuration files from NordVPN's OpenVPN page in /config/openvpn.
I followed the tutorial by spaceinvaders but can not find a .crt or .pem file anywhere on the NordVPN website.
I have placed my log below in hopes you'll be able to see what I've done wrong.

 

<LOG>

I have found the issue. I had not added the --cap-add=NET_ADMIN.

The Synology Docker app does not allow me to add it, but I was able to set "Execute container using high privilege" and that fixed my issues.

oke not using unraid i still have a few delugevpn specific questions if i may?

 

1) -v /apps/docker/deluge/data:/data \
this line refers to the place where the downloads end up, basically i can choose this location myself?

2) -v /apps/docker/deluge/config:/config \
this line refers to the place where:
 

a: the openvpn config files are placed? or
b: the deluge config files are created?

if it is a i need to place two files there? .ovpn and a .crt right?

 

 

47 minutes ago, spikey1973 said:

oke not using unraid i still have a few delugevpn specific questions if i may?

 

1) -v /apps/docker/deluge/data:/data \
this line refers to the place where the downloads end up, basically i can choose this location myself?

2) -v /apps/docker/deluge/config:/config \
this line refers to the place where:
 

a: the openvpn config files are placed? or
b: the deluge config files are created?

if it is a i need to place two files there? .ovpn and a .crt right?

 

 

1) yes

2) both

@ walter

 

oke thank you, very helpfull.

7 minutes ago, spikey1973 said:

@ walter

 

oke thank you, very helpfull.

You’ll need to start the docker once so that it can create the folder in /config. Then you can place the crt and OpenVPN (if that’s what you’re using) into the config/binhex-delugevpn/openvpn folder and restart the docker.

I installed binhex-delugevpn 5 months ago to help remedy my uTorrent difficulties. Deluge has been great, but I'm not sure the port forwarding was setup correctly.

grc.com is how I test my local machine for open ports, and it shows as OPEN! when testing the port I have set for uTorrent. The port for deluge daemon is open, when tested using grc.

 

I've followed a few different tutorials for setting up Port Forward rules in pfsense. None have worked for Deluge obviously. The rule for uTorrent is working just fine and the options for deluge are the same. WAN, TCP, Other, etc.

 

Redirect target IP is the IP of the server where deluge is running.

 

Can someone ask the correct questions to help me get this figured out?

Edited November 15, 20205 yr by jeff.lebowski

I'm having an issue when changing my container from using ovpn to wireguard.

 

The container starts normal at first then after a few minutes (I think it's 3 or 4) downloads stop working (but the UI remains functional). A minute or so later, the UI stops responding. And then another minute or so after that, all of docker stops responding. And then another minute after _that_, unraid stops responding requiring a hard reset.

 

I know that sounds crazy.

On 11/5/2020 at 6:14 AM, Burizado said:

Awesome!  That's what I assumed, but just wanted to clarify. 😉

Thanks again for all your hard work on this!

I'm trying to modify my new Wireguard endpoint. I'm in the wg0.conf file, and see what I need to change, but not sure of what exactly I should be changing and what my options are? If I wanted a Toronto server, do I change amsterdam to toronto, or do I need an entirely new server address? If so, where do I find a list of available wireguard servers for this?

 

EDIT: I found out how. I just looked at my old list of OpenVPN servers such as ca-toronto and uk-london and changed nl-amsterdam to ca-vancouver for example in my /appdata/binhex-delugevpn/wireguard/wg0.conf file. Huge increase in speed!

Edited November 15, 20205 yr by [email protected]

I am having issues with accessing the GUI.

 

I deleted the old container and used Community Applications to install fresh.  I've attached the log, which seems to show all is well, but I just cannot access the GUI.

supervisord.log

Edited November 15, 20205 yr by JustinChase
edited log

10 minutes ago, JustinChase said:

I am having issues with accessing the GUI.

 

I deleted the old container and used Community Applications to install fresh.  I've attached the log, which seems to show all is well, but I just cannot access the GUI

No answers for your problem but you should change your user name/password since they are included in the log.

8 minutes ago, wgstarks said:

No answers for your problem but you should change your user name/password since they are included in the log.

I'm not sure what happened, i was sure I edited them out.  i replaced log with edited credentials, and am changing now.

Hi All

 

I absolutely love this docker and the all in one approach making it secure!

Installed this some time ago, and for some reason during the installation I was told to set the branch to: binhex/arch-delugevpn:2.0.3_23_g5f1eada3e-1-03

I have just removed this and updated it to the normal one: binhex/arch-delugevpn

 

And I need a little help on how to get up and running again :-)

 

(I USE PIA!)

Some new arguments in the docker settings:

Container Variable: VPN_OPTIONS?  (I have looked but havent found what this should be filled out with?)

 

Also in the log file I can see the following errors

 

I have downloaded the new set of files from PIA: openvpn-nextgen.zip:

 

And extracted the:

ca.rsa.2048.crt

DE Frankfurt.ovpn

crl.rsa.2048.pem

credentials.conf (Mine)

 

Also set the Container Variable: STRICT_PORT_FORWARD: no

What am I missing?

 

As always thanks for a great forum and so many great people helping each other

 

 

 

 

 

I updated the files again and removed the set the Container Variable: ENABLE_PRIVOXY: no

I got a complain about not setting the "Container Variable: VPN_OPTIONS?"

But the UI started up again! :-)

10 hours ago, JustinChase said:

I am having issues with accessing the GUI.

 

I deleted the old container and used Community Applications to install fresh.  I've attached the log, which seems to show all is well, but I just cannot access the GUI.

supervisord.log 28.86 kB · 1 download

did you set lan_network correctly?, its currently defined as:-

2020-11-15 18:03:38.132920 [info] LAN_NETWORK defined as '192.168.1.0/24'

if you are unsure how to define it then check Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

11 minutes ago, casperse said:

I got a complain about not setting the "Container Variable: VPN_OPTIONS?"

thats fine, its used to allow connections from multiple containers, its not mandatory. 

On 11/15/2020 at 8:23 AM, jeff.lebowski said:

I've followed a few different tutorials for setting up Port Forward rules in pfsense.

dont do that, its unnecessary and a potential security hole, see Q15:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

I upgraded to next gen openvpn and was able to access the WebGUI remotely when I VPN using wireguard into my Unraid server. When I switched delugevpn to use wireguard, I could no longer access the WebGUI remotely (locally, it works fine). Switch back to openvpn, and I can access remotely.

 

I think the post a few pages back (regarding Wireguard to VPN into Unraid) may be relevant to my issue as I don't see anything glaring in my deluge logs. However, I'm not sure what setting would be incorrect in my wireguard VPN setup for Unraid as I can use wireguard to access all other containers on my server remotely except DelugeVPN.

 

Thanks!

 

 

supervisord.log

6 hours ago, binhex said:

did you set lan_network correctly?, its currently defined as:-

2020-11-15 18:03:38.132920 [info] LAN_NETWORK defined as '192.168.1.0/24'

 

Nope, I sure didn't.  I've fixed, and all is well again.  Thanks again for the prompt support, and for all you contribute!