I tried. I couldn't get it to work again, so wanted to look at other options alongside looking for help/solutions.
But just as it decided to stop working, despite my efforts; it's suddenly started working again.
Sigh...
I tried. I couldn't get it to work again, so wanted to look at other options alongside looking for help/solutions.
But just as it decided to stop working, despite my efforts; it's suddenly started working again.
Sigh...
Vaultwarden is just a self-hosted server for Bitwardens clients. It's Bitwardens android client I've been having issues with.
That's an interesting option. It's the Bitwarden app I've been having issues with; though I'm not sure how much of that is Bitwardens fault vs Android itself.
I'll give that a look, thanks :)
That's exactly why I'm so upset about this. I don't want my passwords in my clipboard history.
Up until now, I've had some minor trouble; but usually deselecting the field you want filled and selecting it again brings up the missing autofill. That or switching apps and back.
Suddenly this morning it's completely 100% broken. I can't get ANYTHING to autofill no matter how much I try.
I stand corrected; as of today bitwarden autofill doesn't work AT ALL.
Absolutely nothing will autofill anymore.
I'm so tired of seeing this overblown reaction to ancient non-news.
Yes, there are some minor vulnerabilities in Jellyfin; but they really really aren't concerning.
Unauthenticated, a random person could potentially (with some prior knowledge of this specific issue, and some significant effort randomly generating media UUIDS to tryout) retrieve/playback some media unauthorized. THATS IT. That's the ONLY real concern. And it's one you could mitigate with a fail2ban filter if you were that worried about it.
The other 'issues' here, are the potential for your already authenticated users to attack each others settings. Who do you share your server with that you're concerned about them attacking each other???
Put this to bed and stop fussing over it. It's genuinely not worth your time or attention. Exposing Jellyfin to the net is fine.
Dev comment on the situation: (4 days ago) https://github.com/jellyfin/jellyfin/issues/5415#issuecomment-2825240290
The three of them are all pretty similar, achieving the same goal; whatever works for you.
I've never had an issue with Ombi, so I've stuck with it. I actually use Emby instead of Jellyfin, so Overseerr isn't an option, and I've just not had a reason to try out Jellyseer over what's already setup and working.
Prowlarr is definitely a good recommendation. I used Jackett for the longest time; but being able to modify indexers in one place, then have it propagate to the rest of the stack is so much nicer. It lists a ton of indexers to look into too, if you need more.
The arrs are pretty light weight; the memory use can add up when you run several of them with really large libraries alongside other projects, but otherwise I hardly notice them running in the background. You don't need any sort of special hardware; this stuff will run on an old laptop you shove in the corner and ignore.
The part that really takes processing power is transcoding media between formats when streaming it to clients, but that's Emby/Jellyfins job.
Torrents have two options:
Ideally you use Hardlinking - This creates a 'copy' of the file that's just a link to the original data, instead of actually duplicating it. This only works when both 'copies' are kept on the same drive/filesystem; but gives you two versions so you can leave one available to seed and have one renamed and sorted away.
Failing that, it can fallback to plain duplicating the files. One copy kept to seed, and one copy sorted away.
Personally, I've switched to usenet for 99% of downloads, so seeding isn't really a thing. It's there as a fallback though.
My setup is a conglomeration of a quite a few different pieces; but they are not all required. I'd encourage you to explore, start small and expand into new pieces/areas when you feel comfortable. I started this ~8 years ago with basically 0 knowledge of hosting web services; and just built up the knowledge through exploration over time.
If all you're looking to do is watch movies, and you're happy to play the downloaded media directly on your pc (or move the files around manually, just like manual torrenting); the only piece you need is Radarr.
Once setup; You tell it what movies you want to watch, it searches for those using the indexers you've given it (YourBittorrent, TPB, and BadassTorrents for example), choses the best results out of them all based on things like upload date, seeds, quality descriptors in the title, etc. Then passes that to your torrent/usenet client. Finally it will rename and sort the files into nicely organized media folders for you, once the download client has marked it as complete.
What type of auto fill do you use/works for you?
Looking into this more I've realized there are three options, but only one has ever worked for me. (talking strictly about the Bitwarden android app)
The standard 'autofill services', which is supposed to provide a popup on screen near the item to be auto filled has never worked for me. Sometimes it will flash onscreen for a fraction of a second, but always disappears before you could possibly touch or even read it.
'inline autofill' is what I have been using. It replaces the word suggestions on the keyboard with autofill options. It's what stopped working today, then seems to have come back; both unexplainably...
Finally there's the 'use accessibility' option, but the only bitwarden accessibility options I can find in android are these:
Each with 'select action' > 'bitwarden'. No other configuration, no options to choose what to do with Bitwarden, just 'bitwarden'.
When enabled the selected action enables/disables bitwarden as an autofill service to be used in the standard Android autofill services as above. I can't find anything at all in accessibility that actually triggers autofill to fill things.
I've always had all three of these autofill options enabled, but inline is the only thing that's ever actually functioned. Even still, that has been flakey, with it often not appearing in the keyboard until I move the cursor between fields several times or switch apps and come back. Today is the first time it's outright refused to show up no matter what troubleshooting I tried.
It's fixed itself and started working again, but I habe no idea why. I didn't change anything between now and when I made this post.