binhex

i see you are using a non standard port for the web ui, check this is setup correctly q4:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Can you please post your docker run command

Thanks for this i really appreciate the detail, i shall try and come up with a set of instructions for common vpn providers to make any transition/first time use easier, TBH PIA and ProtonVPN cover most users.

Don't set VPN provider to custom, set it to protonvpn

OK two more test for you: Set networking to default - if the networking is not set to 'bridge' then please set it back to this then test and report back Try with new config - can you edit your existing container and change the host path for /config to something else, then click apply, test and report back FYI - As you may be able to guess i cannot replicate this issue, krusader starts within 2-3 seconds for me, as i assume it does for most people.

I haven't checked all VPN providers, but i know PIA def is not supported at present. Ahh yes, that is something that needs to be set, that must of slipped through the net, i have now included this change in the script, it wont take effect until i rebuild the image, so for now please set it manually. no other ways that im aware of, localhost is pretty safe though TBH, you would have to have a intruder logged into the console of the docker for them to take advantage of this, you cannot bypass authentication from outside the container with this option set alone.

probably your preferences files is corrupt, try stopping the container then delete this file and start the container again.

ok so this is interesting, so it might be that the time to start is due to remote mount points or shares being retried until a timeout is hit. if you remove all remote attached directories does the startup time improve?.

Which version are you running?, if it's not the latest 7.1.4 then i would advise as a first step to get you up to the latest stable version, then try it again.

see Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md

There is no webui for flaresolverr, its a CLI tool.

ok and you have set the network for qbittorrent to use the gluetun containers network, right? for example my gluetun container is called gluetun-qbittorrent, so therefore i have set --extra-parameters for qbittorrent to:

interesting, i cannot replicate the issue, i have just tried with the latest image and a fresh config, i assume you are specifying the healthcheck via new HEALTHCHECK_COMMAND env var, right?. Can you please post your docker run command (edit container, change something, change it back and click apply then paste the contents of the subsequent window here) and attach the /config/supervisord.log file.

For now the other VPN related images are maintained, i shall give the community plenty of notice IF (and it is a big if) i decide to deprecate the VPN images.

Please see Q30 and Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

how do you mean?, i would treat use of gluetun and use of privoxyvpn as two separate things, do not try and combine the two, you can use both if you so wish but dont try and pass privoxyvpn to gluetun network, instead use gluetun's http proxy server if you need a proxy server, or turn off gluetun proxy server and run privoxyvpn.

you can but i dont think its going to tell me much, i got a sneaky feeling this is unraid related, im on v6, i assume you are on v7, right?.

I have created a gluetun template as the existing one was out of date (missing env vars) and if im moving forward with gluetun support then i wanted full control, if you wish to give it a whirl then look on CA for binhex-official-gluetun This is the basics to get a PIA tunnel setup for gluetun (yes there are butt-ton of options for gluetun, don't let it scare you! 😁) Set VPN_SERVICE_PROVIDER toPIA Set VPN_TYPE: toopenvpn Set OPENVPN_USER: to <your PIA username> Set OPENVPN_PASSWORD: to <your PIA password> Set SERVER_HOSTNAMES: to <port forward enabled endpoints> e.g. ca-toronto.privacy.network,nl-amsterdam.privacy.network Set VPN_PORT_FORWARDING: to on Set FIREWALL_OUTBOUND_SUBNETS: to <CIDR for your network> (same as LAN_NETWORK for my existing VPN containers) notes:- No need to download the OpenVPN config file, its baked into gluetun (nice for the end user, a PITA for the dev). This is how i have all 3 setup, any problems with gluetun for now they can go here (yes i may create a separate thread for the binhex official templates).

I was considering this as a replacement, as its a neater more flexible solution, but there is one sticking point that might cause friction (or maybe not, awaiting response from community) and that is that gluetun does not currently support PIA wireguard connections (see note), this is due to the complexity from PIA requiring the generation of a dynamic wireguard config file, this requires access to PIA before the tunnel can be established, the main gluetun dev is understandably nervous about this as it leaves a small window where gluetun will not be secure. Having said the above i have been testing with gluetun and it works really well once setup, i now have 3 gluetun containers running, one generic for all non incoming port apps, and then one for qbittorrent and one for nicotine+ (both require incoming ports), all using PIA OpenVPN. Note: Yes you can temporarily get gluetun to connect to PIA via wireguard but it will fail after a period of time, as the wireguard confguration will expire.

Please see Q30 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Please note this container now has built in gluetun support, please see Q9:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Please note this container now has built in gluetun support, please see Q9:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Please note this container has built in gluetun support, please see Q9:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Overview: Support for Docker image arch-qbittorrent in the binhex repo. Application: qBittorrent - https://github.com/qbittorrent/qBittorrent Docker Hub: https://hub.docker.com/r/binhex/arch-qbittorrent GitHub: https://github.com/binhex/arch-qbittorrent Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

It's possible to edit the python code but the change will be overwritten every time a new image is published, so yeah that's going to get frustrating for you real quick, i would back away from anything like that.