[[Support] binhex - qBittorrentVPN]

For me it didn't, it got stuck at the same message with privileged =on unfortunately

[[Support] binhex - qBittorrentVPN]

1 minute ago, binhex said:

delugevpn does not require privileged elevation, it is set like that for unraid users only because there is no simple way to set '--cap-add=NET_ADMIN' which is what is actually required (other than extra args which is ugly). so i know you are saying this is 'high privilege' but i have to ask, is that the same as 'docker run <rest of command> --privileged=true <rest of command>', can you actually see what synology executes as a command line?.

 

if you cant access the ui when the vpn is disabled then the issue is not related to port forwarding, openvpn config or account credentials, its got to be permissions related, thats my guess, is there nobody else you can talk to on the synology forum that has this running?, it probably would be much quicker as they know what hoops (if any) need to he jumped through in order to get this running on a synology appliance.

Thanks for the help so far! I'll try to find something on the web in a few minutes and let you know!

[[Support] binhex - qBittorrentVPN]

17 minutes ago, binhex said:

hmm ok, i would double check with synology support/forum that that checkbox really does equate to the 'privileged' flag for docker, as if its anything less than that then you will see the exact symptoms you are describing.

 

one other thing to check, what happens if you set VPN_ENABLED to no, can you access the web ui then?.

As per synology's website it is execute with high privilege, ive used that for multiple instances as well, including your (binhex) delugevpn. But pia told me to use qbittorrent instead as it would be better for speeds.

 

Ive tried multiple changes among vpn_enabled to no but no different out ome unfortunately.

 

I thought it had something to do with VPN port forwarding but that would be weird as I should still be able to access the we ui even when VPN is off

[[Support] binhex - qBittorrentVPN]

Yes, basically the first check translates as "run the container with high permissions" and the second ticked checkmark is to automatically restart the container

[[Support] binhex - qBittorrentVPN]

I've read the thread but coudn't find a solution to my problem, maybe you can help me. I keep getting the message "[info] Waiting for qBittorrent process to start listening on port 911..." but the webpage is never accessible.