🇨🇦
Plex, Emby, and Jellyfin are all legal, and each have ways to serve liveTV alongside your own locally stored content, and DVR that liveTV if you want. You’d just have to purchase a liveTV subscription from your local provider (or go the Pirate route ofc).
Emby has what they call ‘Emby Connect’ which is entirely optional and is basically a glorified DNS service.
It doesn’t proxy connections, it just passes on the hostname to the client. The server is still required to setup port forwarding or other routing like tailscale or a proxy on a vps.
Emby Connect will let you sign into your local server using your emby.media credentials, but unlike Plex it’s completely optional and only works once explicitly linked to the local user of an Emby server.
I only bring it up because you explicitly said you have no idea why it doesn’t work.
Take things at a comfortable pace; there’s no sense overwhelming yourself. Then you just forget what you’ve done and end up lost in your own maze.
I started with Plex myself, almost 10 years ago. Moved to Emby, where I learned about buying a domain, setting up ssl through a reverse proxy, and just continued to explore from there. Today I run ~26 containers/projects across three systems and I’m always keeping my eye out for interesting new things.
Best of luck with your journey m8.
Sounds like you’re behind cgNAT, which essentially means there’s another router owned by your ISP that’s between yours and the open internet, which also requires port forwarding, but your ISP will never do that for you.
It complicates things, but the solution(s) are tools like tailscale, cloudflare Tunnels, or to rent a VPS just to host a proxy/vpn.
Plex solves this by using their own public servers as a proxy for you, but this is part of how they have control over your users/server/data, such as blocking remote streaming… That makes more than a few people uncomfortable.
Plex centralizes authentication at plex.tv
When a user wants to connect to a ‘private’ plex server, they must first sign into their plex.tv account, which then provides the auth token needed to login to the users server (even if both the client and server are on the same lan)
With this system, Plex can monitor and control every single connection to every plex server; limiting access to whatever they want. Even your own local content.
Plex has an automatic proxy service hosted by their public servers. If you haven’t or can’t configure port forwarding correctly, plex will route the connection through their own servers.
The problem is, that also means Plex co has total control over your server and the data sent between it and clients if they so choose. Anything from quietly logging the data sent back and fourth, to controlling who can connect and what they can do while they are.
Jellyfin has to be correctly exposed to the internet via port forwarding or tools like tailscale/a vpn; but it’s entirely your server under your control. You have ultimate control over how your server can be accessed, but that also means you’re responsible for actually setting that up.
Major version changes for any software from the OS right down to a simple notepad app should update as sequentially as possible (11>12>13>etc). Skipping over versions is just asking for trouble, as it’s rarely tested throughly.
It might work, but why risk it.
An example: if 12 makes a big database change but you skip over that version, 13 may not recognize the databases left by 11 because 12 had the code to recognize and reformat the old database while that code was seen as unnecessary and removed from 13.
Stuff like this is also why you can’t always revert to an older version while keeping the data/databases from the newer software.
Typical piracy requires you to search sources/indexers yourself, decide on the best search result for what you’re trying to download, pass that to your download client, then manually name and sort the downloaded files into media folders once the download completes.
The arr’s automate this entre process for several media types (movies, tv, music, etc), combining search results from dozens of indexers to make its decision on what to download.
Now, I open a webpage, search for a movie/show (results from imdb) and select an item I want to watch. ~15min later, that item has been found, downloaded, and sorted into my media folders where Emby/Jellyfin can display it to myself or friends.
Add on to this with Ombi, a requests platform that allows my friends+family to request media and have the arrs automatically grab it. Since setting that up a little over a year ago, it’s filled almost 400 requests (not including media I’ve grabbed/requested myself) without me having to manually manage requests ever.
Ontop of grabbing media on request, the arr’s also monitor the sources you’ve configured, watching for new uploads, and grabbing content that’s missing from your library but monitored for, such as: newly aired episodes, media that couldn’t be found earlier, or upgrades in quality for existing media (if configured/allowed to upgrade existing media).
Every time a new episode airs for a show I’ve added, it automatically grabs it for me. (currently 486 series monitored here)
That’s a neat little tool that seems to work pretty well. Turns out the files I thought I’d need it for already have embedded OCR data, so I didn’t end up needing it. Definitely one I’ll keep in mind for the future though.
That works magnificently. I added -l so it spits out a list of files instead of listing each matching line in each file, then set it up with an alias. Now I can ssh in from my phone and search the whole collection for any string with a single command.
Thanks again!
Started a new job as a tool tech in a rental center; maintaining, repairing, and simply showing people how to operate, a ton of different tools, some of which I’ve never even seen before.
First thing I did is setup a file share on my server that I’ve populated with 70+ manuals and growing by the day…
Read through them all myself to understand the nuances of each machine and be able to explain the details to customers; plus I can print them a fresh copy on demand just for good measure.
Interesting; that would be much simpler. I’ll give that a shot in the morning, thanks!
Yeah, your home server is still able to reach plex.tv so there’s no problem there.
It’s people actually hosting there that got screwed over.
Plex blocked Hetzner IPs, so servers hosted there can’t reach plex.tv to auth users or validate plex pass.
DNS-01 is in the pipeline at least, so hopefully we’ll see that bring wildcard certs along with it.
It’s nice to see this being integrated into nginx. I’ve been using ACME.sh for around a decade instead. It just triggers through a script on a crontab schedule grabbing a new cert via DNS-01 if necessary, then refreshing nginx to recognize the new file.
almost nothing else…? Cmon OP, you’ve gotta elaborate there. What ended up taking a swim with the turd stick?
Just the domains? They’ll be back under new names in a couple days max.
Note; that project is no longer being maintained.
https://github.com/filebrowser/filebrowser/discussions/4906
There is a fork working it’s way out of beta though.
You have to explicitly enable directory indexing; but then it will automatically generate simple http pages listing directory contents.
https://nginx.org/en/docs/http/ngx_http_autoindex_module.html
I have the same issue with Immich on android. It pretty much never uploads files until I manually open the app; then the app refuses to acknowledge it has uploaded those new files until it’s closed and re-opened :( (power saving is set to un-restricted in android, and background data usage is allowed. I’ve been through troubleshooting very thoroughly, it just doesn’t work)
FolderSync has been the only reliable (non-root) backup solution I’ve used. It’s set to monitor my image folders for changes and upload any new files as soon as they’re created; this works ~85% of the time. Then, It’s also set with a few schedules to check for changes every 3hrs, backing up everything on the phone the app can access; this catches anything the on-change/on-creation file detection misses, while also backing up more data than just my images. I have yet to see that fail after ~3 years.