@blokhead @david279 please pull 'latest' tagged image just built and try again, please let me know the outcome.

15 minutes ago, binhex said:

@blokhead @david279 please pull 'latest' tagged image just built and try again, please let me know the outcome.

That worked after a force pull.

23 minutes ago, binhex said:

@blokhead @david279 please pull 'latest' tagged image just built and try again, please let me know the outcome.

I pulled the latest and now deluge is reporting downloads correctly to the Arrs, but my NZBget still won't start a download, it loads in the list - status downloading, but there is no traffic.  Verified it pulled the new IP that i got from PIA when updating Deluge.

It might be an issue with the update for nzbget that I also installed this morning.

 

36 minutes ago, blokhead said:

I pulled the latest and now deluge is reporting downloads correctly to the Arrs, but my NZBget still won't start a download, it loads in the list - status downloading, but there is no traffic.  Verified it pulled the new IP that i got from PIA when updating Deluge.

It might be an issue with the update for nzbget that I also installed this morning.

 

Just sent something from radarr to deluge, and it is showing as active in Sonarr, and Lidarr...

 

I'm never updating again lol

 

3 hours ago, binhex said:

according to your logs docker is using the default docker network of:-
 

[info] Docker network defined as    172.17.0.0/16

so that looks fine, just check this container is running using the docker 'bridge', that is how this image was designed.

 

It is running using the 'bridge'.

1 minute ago, Noego said:

 

It is running using the 'bridge'.

There was an issue upstream with the base os, please try pulling down latest (built around 30 mins ago), this MAY fix your issue.

It's working fine for me now. I pulled the latest image using the unRAID GUI.

 

Thanks for fixing this so quickly. I appreciate all the work you put into the multiple docker containers that I use! 

On 9/21/2023 at 12:30 PM, binhex said:

There was an issue upstream with the base os, please try pulling down latest (built around 30 mins ago), this MAY fix your issue.

 

It didn't solve the issue.

 

I tried to pull the QBitTorrentVPN and I get the same issue. So I guess it is not the docker, but more likely some setup elsewhere. 

 

EDIT:

I have no idea why, but I updated to the newest Mac OS and got an error message about access to a folder (locale time folder). 
I reinstalled the docker, and everything works fine now. 

Edited October 2, 20232 yr by Noego
Suddenly works

6 hours ago, binhex said:

what is the ip address of the machine running the web browser?

The browsers are all on a different VLAN

 

Your latest Update today has fixed this.

 

Thank you

 

 

 

Edited September 21, 20232 yr by Keyman

Latest update fixed my issues, too.  I could access the webUI from home on the internal LAN, but had no access through WireGuard remotely.  All good now.  Thanks!

Having an issue resolving DNS in a docker container. Been looking through these forms plus github and nothing is working. Unsure if I missed something in the setup. I have tried multiple .ovpn and ensured I can connected to the same locations on another device using the PIA client.
using default bridge network in docker and tired many name_servers addresses which includes the default

 

Log and docker compose below. Any help would be appreciated 
 

Quote

Having issues resolving name 'france.privacy.network', sleeping before retry...

version: '3.9'
services:
    delugevpn:
        image: binhex/arch-delugevpn:latest
        container_name: delugevpn
        cap_add:
            - NET_ADMIN
        volumes:
            - ${downloadFolder}:/data
            - ${delugevpnConfig}:/config
            - /etc/localtime:/etc/localtime:ro
        environment:
            - VPN_ENABLED=yes
            - VPN_USER=<username>
            - VPN_PASS=<password>
            - VPN_PROV=pia
            - VPN_CLIENT=openvpn
            - STRICT_PORT_FORWARD=no
            - ENABLE_PRIVOXY=no
            - LAN_NETWORK=192.168.1.0/24
            - NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
            - DELUGE_DAEMON_LOG_LEVEL=info
            - DELUGE_WEB_LOG_LEVEL=info
            - DELUGE_ENABLE_WEBUI_PASSWORD=no
            - DEBUG=true
            - UMASK=000
            - PUID=0
            - PGID=0
        ports:
            - '8112:8112'
            - '8118:8118'
            - '58846:58846'
            - '58946:58946'

 

1 hour ago, OneWeekNotice said:

Log and docker compose below

no log attached, please do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

11 hours ago, binhex said:

no log attached, please do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Logs attached. Thanks for the help

supervisord.log

I'm having a little trouble with labels that are passed from Medusa to deluge..

 

It gets the right label, and moves the torrent upon completion to the correct directory, but doesn't remove the torrent from the list until I go to the deluge webgui, and right click the label and select label options. Then just clicking ok makes it remove the torrents, (The files that it are pointing to are already gone, it's just not removing the torrent from the list.)

 

Delugesiphon for chrome works fine for the same label.

 

 

Any clues?

 

Edited September 26, 20232 yr by dabone
spelling

22 hours ago, OneWeekNotice said:

Having an issue resolving DNS in a docker container. Been looking through these forms plus github and nothing is working. Unsure if I missed something in the setup. I have tried multiple .ovpn and ensured I can connected to the same locations on another device using the PIA client.
using default bridge network in docker and tired many name_servers addresses which includes the default

 

Log and docker compose below. Any help would be appreciated 
 

version: '3.9'
services:
    delugevpn:
        image: binhex/arch-delugevpn:latest
        container_name: delugevpn
        cap_add:
            - NET_ADMIN
        volumes:
            - ${downloadFolder}:/data
            - ${delugevpnConfig}:/config
            - /etc/localtime:/etc/localtime:ro
        environment:
            - VPN_ENABLED=yes
            - VPN_USER=<username>
            - VPN_PASS=<password>
            - VPN_PROV=pia
            - VPN_CLIENT=openvpn
            - STRICT_PORT_FORWARD=no
            - ENABLE_PRIVOXY=no
            - LAN_NETWORK=192.168.1.0/24
            - NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
            - DELUGE_DAEMON_LOG_LEVEL=info
            - DELUGE_WEB_LOG_LEVEL=info
            - DELUGE_ENABLE_WEBUI_PASSWORD=no
            - DEBUG=true
            - UMASK=000
            - PUID=0
            - PGID=0
        ports:
            - '8112:8112'
            - '8118:8118'
            - '58846:58846'
            - '58946:58946'

 

Found my issue. Was running Pihole on my network. Disabled and everything is working. Confirmed this solution with other threads comments in the past.

On 7/28/2023 at 6:46 AM, strike said:

Do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

 

Also what network type do you use? And are you using VLAN?

Soooo this is from way back, 

 

See attached, 

Also using a normal network nothing too fancy just a normal router with a DHCP

PC network range is 

 

192.168.1.63 and docker is 192.168.1.30 both on /24supervisord.log

 

 

8 hours ago, brent3000 said:

192.168.1.63 and docker is 192.168.1.30 both on /24

that is most probably your issue, set the container back to 'bridge' network type and it will work.

17 hours ago, binhex said:

that is most probably your issue, set the container back to 'bridge' network type and it will work.

Am I not able to have a different IP for the docker container? I have it on another IP on another system? 

 

Edited September 27, 20232 yr by brent3000

Hello, I'm trying to route other docker containers through DelugeVpn. I'm following the github guide Q24, Q25 and Q26. 

 

Question: Does anyone know what the equivalent setup would be for unraid 'Extra Parameters' in docker cli or a docker gui such as portainer? 

 

Specifically these below instructions. 

Quote

Left click icon and 'Edit' container and toggle advanced view (top right).

In 'Extra Parameters' enter --net=container:<vpn container name>.

Go to 'Network Type' and select 'none'.

Write down the ports defined and then remove all ports (no ports required as we will be accessing it via the vpn container).

Click on 'Apply'.

Any help would be appreciated

2 hours ago, OneWeekNotice said:

Any help would be appreciated

Not sure if you need that specific guide but I followed this video and it worked for me (its abit out of date on some of the button locations but helped me get it done using the GUI)

 

Edited September 27, 20232 yr by brent3000
added video

2 hours ago, OneWeekNotice said:

Question: Does anyone know what the equivalent setup would be for unraid 'Extra Parameters' in docker cli or a docker gui such as portainer? 

for docker cli it should be as simple as adding in those flags and parameters to the docker cli, extra parameters is simply a unraid mechanism of allowing people to specify options that have not been designed in the web ui, that's all.

19 hours ago, binhex said:

that is most probably your issue, set the container back to 'bridge' network type and it will work.

Ok so when i set it to 'Bridge' mode it works but when i try and set it to custom IP address it seems the error comes back, However i have the exact sane setup on another system (just that one has VLAN's this one dosnt) and it works a treat.

 

Screen from one which isnt working

 

This is from another box i have and its working fine

4 minutes ago, brent3000 said:

Ok so when i set it to 'Bridge' mode it works but when i try and set it to custom IP address it seems the error comes back, However i have the exact sane setup on another system (just that one has VLAN's this one dosnt) and it works a treat.

 

Screen from one which isnt working

 

This is from another box i have and its working fine

you can assign a fixed ip to the container BUT the custom bridge must be assigned a different network to your LAN, for example:

if your docker container has an ip of 192.168.2.1 subnet 192.168.2.0/24 and your LAN_NETWORK is defined as 192.168.1.0/24 then it will work, 

 

if your docker container has an ip of 192.168.1.1 subnet 192.168.1.0/24 and your LAN_NETWORK is defined as 192.168.1.0/24 then you will not be able to access the web ui (your current configuration).

 

Switching to the default 'bridge' works, as this resets the docker network to 172.17.0.0/16 thus preventing the LAN_NETWORK clash and allowing iptables rules to work as designed.

 

29 minutes ago, binhex said:

you can assign a fixed ip to the container BUT the custom bridge must be assigned a different network to your LAN, for example:

if your docker container has an ip of 192.168.2.1 subnet 192.168.2.0/24 and your LAN_NETWORK is defined as 192.168.1.0/24 then it will work, 

 

if your docker container has an ip of 192.168.1.1 subnet 192.168.1.0/24 and your LAN_NETWORK is defined as 192.168.1.0/24 then you will not be able to access the web ui (your current configuration).

 

Switching to the default 'bridge' works, as this resets the docker network to 172.17.0.0/16 thus preventing the LAN_NETWORK clash and allowing iptables rules to work as designed.

 

Well that explains it well on why one works and one dosnt, is that a recent change? I swear this was working before at one stage.

 

The issue I oddly then get is when i have a docker using the dlugevpn as its network for some reason in this format I cant access the other docker when its being router via the bridge version (yet what its setup like before, Deluge wont load but all the other docker containers work fine via the IP)

 

(--net=container:binhex-delugevpn)

 

Would some of the network changes impact that from working while in bridge mode?

 

Thats following the guide above i posted from Space Invader 

Just now, brent3000 said:

Well that explains it well on why one works and one dosnt, is that a recent change? I swear this was working before at one stage.

nope, its been that way since day1, it was indeed designed that way as macvlan, ipvlan and custom bridges and all that guff wasn't even an option (in unraid) when this image was created.

 

5 minutes ago, brent3000 said:

I cant access the other docker

i am not quite clear on this, do you mean access the web ui of the other docker container from your lan or do you mean cross communication between docker containers in the same network? e.g. sonarr talking to deluge whilst both using delugevpn network?.