Also, you are trying to access from the same LAN you have configured?

That file is ridiculously long any specific part?, I didn't change the LAN part, I am trying to access it from the PC next to my server, same one I can access the other Unraid containers from

Deleted and tried starting over again, if I turn the vpn enabled to no, it works and pops up immedaitely

Finally figured it out deleted some of the privoxy stuff and tried a different port and it now works for some reason thanks

6 hours ago, erfly7 said:

Finally figured it out deleted some of the privoxy stuff and tried a different port and it now works for some reason thanks

You might post the changes you made to get it working. Someone (not me 😁) might be able to explain why they worked so that it may help others.

 

Glad it’s working for you.

Deleted the two privoxy lines, changed port to 8081 instead of 8100 and for some reason worked, I also started from scratch and generated a whole new wireguard file from airvpn.

Tried logging into my application today and I cannot connect.  I disabled the VPN and it let me in... but of course no VPN...

 

I am using PIA for VPN...  Any ideas what happened?  I changed nothing overnight.

8 minutes ago, twidget2011 said:

Tried logging into my application today and I cannot connect.  I disabled the VPN and it let me in... but of course no VPN...

 

I am using PIA for VPN...  Any ideas what happened?  I changed nothing overnight.

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

Did you want the files mentioned on that page?

 

 

Here is the Command executiondocker run
  -d
  --name='qbittorrentvpn'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='xxxxxxxxx'
  -e 'VPN_PASS'='xxxxxxxxxx
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'WEBUI_PORT'='8080'
  -e 'LAN_NETWORK'='192.168.1.0/24, 10.8.0.0/24'
  -e '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'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/share_media/':'/data':'rw'
  -v '/mnt/user/share_media/torrents/prowlarr':'/prowlarr':'rw'
  -v '/mnt/user/share_media/torrents/music/':'/musicdownloads':'rw'
  -v '/mnt/user/appdata/qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

8126552ec8dea889a9da06038f7fbc2cf7a91d94525764b1196d52f09287920b

The command finished successfully!

2 minutes ago, twidget2011 said:

Did you want the files mentioned on that page?

Yes. Those were instructions for what info to post. Be sure to redact user/password.

On 10/27/2024 at 5:08 PM, nerbonne said:

I assume you mean the 10.10.6.0/23 network?   Yes, my desktop PC is IP 10.10.6.7/23

 

Did you find a solution... I think I have the same issue...

25 minutes ago, wgstarks said:

Yes. Those were instructions for what info to post. Be sure to redact user/password.

 

 

command execution.txt.txt

debug enabled supervisord.log

Edited October 31, 20241 yr by twidget2011

Looks like a successful start followed by a few restarts. Have you tried using a different endpoint?

14 minutes ago, wgstarks said:

Looks like a successful start followed by a few restarts. Have you tried using a different endpoint?

What do you mean by endpoint? Do you mean like a different VPN Provider?

4 minutes ago, twidget2011 said:

What do you mean by endpoint? Do you mean like a different VPN Provider?

No. The endpoint in PIA.

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

Scoll down to Q21 section 5.

This is really just a guess but it may be an unstable PIA connection.

You’ll need to restart the docker after you make the changes.

Let me try that now...

47 minutes ago, wgstarks said:

Looks like a successful start followed by a few restarts. Have you tried using a different endpoint?

I changed it... same result....  If I disable VPN, I can connect... with VPN, I cannot connect to torrent client...

What IP are you trying to connect from?

I have tried two on my home network...

Is that 192.168.1.0/24?

6 minutes ago, wgstarks said:

Is that 192.168.1.0/24?

it was in that subnet...

I just tried again.. now it is up... I have no earthy idea why...  

Very annoying and strange...

The docker restart can sometimes take several minutes.

The arm64 docker image 5.0.1-1-01 is still using qBit 5.0.0

11 hours ago, twidget2011 said:

Did you find a solution... I think I have the same issue...

Nope.  I was hoping the maintainer ( @binhex ) would drop in. I appreciate @wgstarks replying to all the questions but hasn't been able to help and I worry that all the activity is hiding the fact that multiple people are having this problem.