binhex

As mentioned above, if your vpn provider is NOT PIA or ProtonVPN then STRICT_PORT_FORWARD is completely ignored, this is for openvpn and wireguard, this has always been the case.

Just to be crystal clear here, Flaresolverr is currently in a broken state, until the Flaresolverr dev's (not me) merge in the PR's mentioned here this is dead in the water.

if your vpn provider is not pia or protonvpn (i assume not due to the statement 'my VPN provider and they advise none of their servers support port forwarding') then STRICT_PORT_FORWARD does nothing.

no it's not. Thats because this app does not understand the idea of docker volumes, which this is, ignore it.

Have a read of Q2 here first to get a basic understanding of bind mounts:- https://github.com/binhex/documentation/blob/master/docker/faq/general.md Once you have read that then move onto Q4 to get the paths correct:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Binding to the virtual adapter is a qbittorrent feature, deluge does not have this but you can bind to the ip address, which i do for you automatically. See above for question 1, and yes to the second part, see Q1 here.

Unless this issue is directly related to the way in which I am building this image (unlikely) then your best bet is to post this on the deluge bug board here. Please keep in mind I am not a member of the deluge developer team, I am simply packaging up what is produced by the application developer(s). FYI I have replicated the issue you are seeing, def looks like a bug in deluge to me, no sign of python traceback in the log. You?

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

Hi guys, i managed to get an hour to myself to have a stab at this, so i was using the compiled version of flaresolverr but i cannot patch it, so i switched to pulling from source and installing the python packages and then finally applying the patched file, however there is another showstopper bug which means i cannot use this either until another PR is merged, here are the gory details:- The issue:- https://github.com/FlareSolverr/FlareSolverr/issues/1119 possible fix (PR):- https://github.com/FlareSolverr/FlareSolverr/pull/1163 And as you can see the PR above makes alterations to the flaresolverr_service.py file, so whether this includes the PR you guys want incorporating or not i cannot say, most probably not, all in all its in a very broken state and will require the flaresolverr dev's (not me) to carefully merge in the PR's one at a time, until that's done it's a waiting game.

This is expected, Plex runs in Host network mode not Bridge

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

I will see if i get some time in the next couple of days to take a look at this, super busy right now.

It is not permitted to include the MS Marketplace in code-server, see the FAQ here, having said that if you live in a country with no copyright laws or want to take the risk and go ahead then you can enable MS Marketplace by doing the following:- 1. left click the container and select edit 2. click on ' Add another Path, Port, Variable, Label or Device' 3. select config type 'variable' 4. set the 'key' to be 'ENABLE_MS_EXTENSIONS_GALLERY' 5. click 'add' 6. click 'apply'.

That patch won't work for the this version of the image as i am currently including the pre-compiled binary, if it's still broken by Monday then i will consider switching to running the scripts directly and including the patched file, wonder why the dev's are reticent to include it if it fixes the issue?.

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

same issue? ignore that, you don't ever want UPnP turned on.

Recording how far i got with language filtering, so the below code doesn't work as expected, it looks like for whatever reason the regex set of separators is not being used, leading to bad partial matching on languages in the movie title, but I'm recording it here in case anybody is interested and wants to try and complete it:- - if_else: condition: "result.contentType in [contentType.movie]" if_action: find_match: - if_else: condition: or: # TODO regex currently seems to incrrectly do partial matches need to fix - "torrent.baseName.matches(r'^\\(?!.*[\\.\\-_\\s]\\(eng|english\\)[\\.\\-_\\s]\\).*[\\.\\-_\\s]\\(fre|french|ger|germany|ita|italy\\)[\\.\\-_\\s].*$')" - "torrent.files.filter(f, f.extension in extensions.video_movie && f.size > 200*mb).map(f, f.basePath).join(' ').matches(r'^\\(?!.*[\\.\\-_\\s]\\(eng|english\\)[\\.\\-_\\s]\\).*[\\.\\-_\\s]\\(fre|french|ger|germany|ita|italy\\)[\\.\\-_\\s].*$')" if_action: add_tag: foreign-movie Of note CEL requires a lot of escaping, thus the ugliness in an already rather lengthy regex!.

My quick stab at this, so the following regex will match on fr, fre, french, ge, ger, germany (feel free to extend languages) but will NOT match if en, eng, or english are (also) present. ^(?!.*\b(en|eng|english)\b).*?\b(fr|fre|french|ge|ger|germany)\b.*$ To be clear this could either match on torrent name or filename within the torrent.

The trouble with that is that you would be deleting a lot of english movies/tv that do not contain 'En, Eng, or English, case-insensitive' which is the vast majority of releases, if you want to do this your best bet is to negatively match on stuff you want to delete for example match on 'fr, FRE, French' for example if you do not want movies/tv shows with french audio, you could be a little clever and put in a ^((?!en).)*$ or similar as part of the regex to ensure it does not pick up movies that contain (in this example) french AND english audio. HOWEVER disk space is cheap at the end of the day and it's not really the job of the index server to filter, i have put in filtering for non ascii titles as i cannot even tell what the movie/tv sow is, but really this is a job for the scripts/apps searching the index site, i.e. sonarr/radarr etc, but that is just my personal opinion.

an issue already exists for this:- https://github.com/qbittorrent/qBittorrent/issues/21421 Note:- As mentioned by @wgstarks I am NOT a dev for qbittorrent, I am simply packaging up what is available, any bugs/features etc with the application (in this case qBittorrent) need to be posted on the official github repository linked above.

fixed up, new image has been built, please pull down.

from the developer:- So right now, nope there is no way to pick up english as flagged by bitmagnet, best you could do is a bit of clever regex, but as mentioned its going to be tricky.

Yes I forced the rename as you cannot have both config and classifier

Permissions look fine, classifier yml is a configuration file so it does not need to be directly executed

well its slightly more targeted than that, from the comment in the file:- # remove any magnet in content type movies or tv series that matches the extensions video_movie and is 200 MB or larger and contains a torrent filename with 2 or more consecutive non ascii characters In my experience of running this (using tagging to view the match) i have not seen any false positive matches, all chinese/japanese/koren/etc movie files get tagged for movies and tv series. But of course this is what I want, what you may want to filter is completely down to you, and it maybe that you don't care about the wasted db space and simply want to grab as many magnets as possible, some people have a pokemon attitude to magnets 'gotta catch em all!' 🙂 I have been trying to get filtering working correctly and giving me the results i want for quite some time now ( 6+ hours) but now its there i'm happy, feel free to ask away if you want to achieve a specific filter type, i may not know the answer though straight away, CEL is still very new to me.