Ffmpeg logs and maybe head to the jellyfin forums, there are a lot of helpful people there.
Ffmpeg logs and maybe head to the jellyfin forums, there are a lot of helpful people there.
vps + boreing proxy
Need your own domain that supports wildcard subdomains. Pretty easy to set up though and works well.
Use jellyseerr. Build using yarn/nodejs.
Follow the windows build instructions on jellyseer github. https://github.com/Fallenbagel/jellyseerr#windows
Couple of things would be great to see.
A reverse proxy setup for remote connections.
A custom format explanation/setup for radarr, and maybe going with sonarr v4 to also get custom formats. Perhaps using recyclarr to import custom formats from trashguides. Currently the setup only goes over adding a download client and media renaming. Would be nice to explain to people how to grab the quality of movie or show that they want.
A usenet download client/setup like sabnzb.
A qbittorrent setup for people who use private trackers and need to seed. And a setup that includes hardlinks so radarr/sonarr can move and rename without messing up seeding.
I know you can add your own container, but a setup for request app like jellyseerr or overseer would be great as well.
Have you looked into using buildarr, to deploy the arr stack? It can be fed a default setup so people wouldn’t have to touch a thing, it would be ready out the gates? Especially if recyclarr was incorporated to import custom formats.
Someone on this thread mentioned my project, which is very rough around the edges, but was definitely inspired by yams. I’m currently working on a massive revision, but I’ve got some life things going on that have stalled progress, but it will incorporate all the things I listed above plus a little more ideas i got brewing. Working on a powershell gui at the moment to switch away from .bat scripts. Thanks u/Rogergonzalez21 for the shoutout.
I think its because you’ve used the same download location for both radarr and qbit. Looking at the trash guide here,docker guide, if you look at the compose example you’ll notice that the download client, sabnzb in the example, has a separate download folder than radarrs. Fixing this should mean that you can also remove the remote path mapping, which in its current state has the same location for remote and local path, which conflicts with the practice described in this guide. But I think you shouldn’t need remote path mapping if you follow the docker guides folder layout.