binhex

firstly this is an unraid issue it is not image related, check that you are not using a specific tagged version, this can sometimes confuse the unraid webui into thinking there is an update, to do this left click krusader, select edit, the toggle 'advanced view' and check the repository, it should be 'binhex/arch-krusader', if this is ok then please post the issue at https://forums.unraid.net/forum/58-docker-engine/

i am assuming you are a protonvpn user, i would also assume from that error that protonvpn has been shutting down or changing some of their servers, go download a fresh config file from them and it should fix it.

do this:- Left click the prowlarr container and select 'Edit', make any change to a value, then switch it back to what it was and click on 'Apply', then copy and paste the 'Command execution' shown to a file, ensuring to remove any reference to username and password, then attach the file here.

are you sharing networkkng with another container, for example vpn container? if you are and you are using one of my images then you will need to define the port in/out (depeds on setup).

For completeness here is what the Jackett configuration looks like for Flaresolverr, just go to Jackett WebUI scroll down to 'Jackett Configuration' and configure the URL for Flaresolverr, e.g.:-

do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

There is no webui for this image, it is purely command line and there is nothing to configure on the flaresolverr end, you simply point prowlarr/jackett at flaresolverr and you are done. i am using this myself, an example setup defined in prowlarr:- once defined here you then add 'tags' to each index site which then links it to flaresolverr.

correct, it's not part of the image, its generated when you configure plex. before getting into that it might be worth working out if you have database corruption or not, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md and if so move onto Q5.

yes its safe to delete, just shutdown the container first to ensure no active transcodes are in progress, then delete and then start container again.

reserved

Overview: Support for Docker image arch-flaresolverr in the binhex repo. Application: Flaresolverr - https://github.com/FlareSolverr/FlareSolverr Docker Hub: https://hub.docker.com/r/binhex/arch-flaresolverr/ GitHub: https://github.com/binhex/arch-flaresolverr 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

Sorry, yep i know you were saying the opposite, not sure how that got misquoted 🙂

your database is corrupt and needs to be fixed up.

That depends, if you trust every device on your LAN (normal) AND you do not port forward all the ports then the risk is close to zero as nobody from the outside world (untrustworthy) can connect. that being said, if you want to change the port range then simply delete the existing port range (cannot change an existing port or range of ports) and then create a new port range to your liking.

its automated, there is a slight delay of an hour or so, so expect an update soon.

There is no support for automatic port assignment from that VPN provider Sent from my 22021211RG using Tapatalk

There is a big difference, proxy will forward HTTPS traffic only, whereas binding network ensures ALL traffic is sent down the VPN tunnel To be clear, for sonarr proxy is fine as it is HTTPS traffic only Sent from my 22021211RG using Tapatalk

read the description for the above keys here:- https://github.com/binhex/documentation/blob/master/docker/guides/vpn.md

not gone through this as i have a discrete nvidia card, but this looks like it should guide you through it:-

sounds like permissions issues to me, try stopping the container then delete the file /config/perms.txt, then start the container, be patient this will be resetting permissions for all files and folders within your /config folder, it may a few minutes then see if you have access.

Assuming you have a discrete graphics card and its nvidia follow Q3:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md

these are not the droids you're looking for :-), check who i am replying to.

totally expected, see Q32:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thanks for this, i am connecting differently as i have a pfsense box running wireguard and i connect in over that, so perhaps im missing some configuration, in any case im happy that you can connect fine with a custom bridge, and hopefully the above might help somebody else out 🙂

i did some investigation into this and it looks like something has changed, either unraid related, docker related or wireguard related, in any case this is the curent state of things:- vpn - custom bridge vs 'bridge' -------------------------------- with custom bridge with specific ip wireguard can access the webui from lan cannot access the webui from remote over vpn cannot access the webui from port forward openvpn cannot access webui from lan cannot access the webui from remote over vpn cannot access the webui from port forward with 'bridge wireguard can acccess the webui from the lan can access the webui from remote over vpn cannot access the webui from port forward openvpn can access the webui from lan can access the webui from remote over vpn can access the webui from port forward so as you can see from the above, best connectivity is from 'bridge' mode using openvpn, second is 'bridge' mode using wireguard, however accessing the web ui over a simple port forward when using wireguard does not work, even in bridge mode. so you currently have it set to wireguard with a custom bridge, which will get you access to the web ui, but will not permit access to the web ui when remoting in over vpn (at least not in my testing it didnt!).