#jackett — Public Fediverse posts

#Jackett gives me this problem where if I leave it alone at some point for no reason I can discern the service stops. This is naturally frustrating if I ever want to manually push something through #Radarr or check up on #Sonarr.

I checked updates and I was "very" behind. So i updated. ehh pretty nice. Then it happened again. Logs only go back to boot. Need a way to see logs when it crashed but :shrug: I'll work on it maybe I might reinstall or something.

Después de algunos intentos fallidos,el fin de semana pasado pude instalar y configurar el plugin jackett en qbittorrent, que amplia a otros buscadores. Aún no tengo claro el alcance, o cuánto agrega a lo que busco a veces, pero ya veremos.

https://github.com/qbittorrent/search-plugins/wiki/How-to-configure-Jackett-plugin

#qbitorrent #jackett #torrent #p2p

I love the way jackett updates itself. The program runs on different OS smoothly, is an sh based program, only does one thing and does it excellent.

The Update process is run only after a long while, after the spawn of jackett. Since I always monitor its logs i saw the following (as screencapped) today when it announced a new version.

Every move it makes is logged in explicit detail. You see how a lib is first copied checked after arrival then replacing the old version. The same goes for all files in the jackett tree which you run in ~/bin/jackett

#programming #opensource #POSIX #Linux #BSD #searchClient #jackett

My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉

Previously, it supports #Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.

Now, to reduce reliance on Plex and lean towards a completely #FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.

I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my #Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.

🔗 https://github.com/irfanhakim-as/charts/pull/136

Jackett и альтернативные решения (интерфейсы и api) для поиска торрентов

В этой небольшой статье расскажу о том, что такое Jackett , на сколько это полезное и простое решение в вопросе поиска нужных раздач, а также, какие существуют альтернативы как для пользовательского интерфейса, так и для API ( Application Programming Interface ).

https://habr.com/ru/articles/841924/

#api #torrent #torrentsearch #tracker #jackett #qbittorrent

@YggTorrent Le nouveau formulaire de connexion casse l'intégration avec #jackett :(

Jackett + Synology Download Station

Есть желание добавить в Synology Download Station возможность искать по 613 торрент трекерам? Хочется видеть, какие именно торренты будут загружены? Хочется чтобы оно работало и в мобильном приложении? Тогда прошу под кат!

https://habr.com/ru/articles/804239/

#Synology #Download_Station #jackett #кино #torrent #plex #медиацентр

Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.

With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:

🚀 #Plex: The media streaming frontend.
🚀 #Jackett: The intermediary between these services.
🚀 #FlareSolverr (opt): Jackett's helper for circumstances that require it.
🚀 #qBittorrent (opt): #Torrent client.
🚀 #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
🚀 #Radarr: Media management tool for movies.
🚀 #Sonarr: Media management tool for TV shows/#anime.

This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.

It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.

🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/flex

Finally overcame this
The slowdowns and weird behaviours were solved instantly simply by using PVCs with access mode: RWO rather than RWX - dk why this is the case, but it is so that's nice!

Everything works now, including: #Plex, #Jackett, #Radarr, #Sonarr, #qBittorrent, and #Overseerr. With this setup, all is needed to add a show to the media streaming frontend (will prolly explore the possibility of using #Jellyfin in place of Plex in the future) is to open up Overseerr and request for a movie/TV show - it will then contact Radarr/Sonarr to download said media using qBittorrent, after which the show will be picked up automatically by Plex.

The only "issue" left is that I notice the downloads either download slowly (hundreds of KiB/s on average), or sometimes even stall or be stuck at "downloading metadata" - even when it seems that the seeding ratio is pretty good. Dk if this is a "#Torrent" issue, or internet in a containerised environment issue (since internet speeds are fine on the host, and my own machine).

Don't really care abt said issue yet tho for now, just excited to be done with this #Helm chart as a "0.1.0" release, then improve on it further such as allowing the use of existing PVCs, external servers for each service (i.e. external qBittorrent server), etc.

RE: https://sakurajima.social/notes/9pk70gb36b

i think i might have to separate them into several helm charts in the end lol, maybe cramming 6 containers into a single pod - which results in heavy resource usage on a single node in your cluster (rather than spread them across multi nodes), might not be the best idea.

i'll just finish the whole "master" chart, then create new charts, for each. atm, the master includes: #jackett, #overseerr, #plex, #qbittorrent, #sonarr, and #radarr.

Tengo tan bien montado ahora mismo el “tinglado” con #Plex, #Sonarr, #Radarr, #Prowlarr, #Jackett, etc que hasta tengo ganas de que salgan series y películas de las plataformas donde no tengo cuenta solo para poner en marcha el sistema y ver como cada engranaje hace su función.

An update on this - I spent about four hours yesterday trying to configure #dockercompose scripts for my services. Once I realised that you could set up multiple networked containers in one compose yml it was like a lightbulb went off. This thing is crazy powerful and useful.

I am struggling to figure out some SSL errors with #Jackett currently - I tried updating OpenSSL but didn't seem to fix it. Based on the GitHub it looks like an ongoing issue so I'm just going to hope it gets fixed soon.

The next step is moving this setup over to my host machine and configuring my port forwards correctly, then I'll switch things over to a pure docker-based setup. I'm actually really excited about learning more - maybe the next step is starting to learn a bit of #python.

Honestly you don't need much, my #jellyfin server is running on an old dual core #Intel #pentium

I am currently deploying #nextcloud, #jellyfin, #sonarr, #readarr, #sabnzbd, #radarr, #lidarr, #prowlarr, #heimdall, #jackett, #qbittorrent, #ombi, #tdarr (I am using a spare laptop as a node, this is just the server), and a few others that are dependencies such as #swag, and #mariadb, all of these are run as docker containers most of which are from #linuxserver.io

@laserlotus

@scd I've been running the stack so long I can't even think of where to point to for a good guide. You'll want to get a functional Docker setup to begin with since that's what all of those acquisition stacks run on. Start with #Jackett and a good torrent client (I like binhex/arch-delugevpn with a good VPN like AirVPN), then add #Sonarr and #Radarr on top. I'd say tackle each of those parts individually which will make it easier to find guides. Those four containers provide a solid foundation to later add onto. #Plex

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

#jackett - то самое открытие, которое сразу же превращается в "Must have".

Открыл для себя замечательный поисковик торрентов. Имеет преднастройки 500+ трекеров по всему миру. Поддерживается некоторыми плеерами под @tvbox (например NUM). Можно установить где-нибудь на своей VPS-ке. Для установки в Calculate Linux используете пакет www-apps/jackett-bin. Далее /etc/init.d/jackett start. Сервис будет доступен по адресу http://localhost:9117 #jackett #calculatelinux #tvbox

Calloboration with the @IBRACORP_IO
# channel on #Sonarr, #Jackett, #QBittorrent, for amazing #OpenSource, #Free, #SelfHosted media management... https://youtu.be/Cth-bsLAa_M

Any #Linux gurus on here that can help me with a #Jackett upgrade? #Ubuntu 16.04 server.