• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: January 2nd, 2025

help-circle





  • Yea, Jellyfin is far from perfect, and it’s what I use.

    It’s a bit more work than it should be, like it loves to identify stuff as Asian if it doesn’t have a perfect match, sometimes with folders properly structured with year and IMDB ID.

    I’m constantly having to fix metadata or even remove a specific movie, rescan, return the movie folder, rescan, and then it sees it right.

    I’ve had to blow away my entire Jellyfin database multiple times this year because it just loses it’s mind and won’t properly identify something.

    It’s what I use, that doesn’t mean it’s perfect, but it is an incredible value, and it doesn’t phone home or any other nonsense.



  • Connecting remotely to your home devices is dependent on your home internet connection’s upload speed, which is usually a fraction of the download speed.

    Then add the overhead of the VPN (Tailscale) and how direct of a connection it’s able to make.

    Then the connection of the device you’re testing from - it may have some bandwidth limitations.

    I just did a quick test - copy a specific file from a local server to my phone - just enabling Tailscale made that copy take twice as long, so it’s definitely adding significant bandwidth constraints (could be an Android limitation).






  • To add - by doing pulls the backup server uses different credentials to run than the credentials used to perform pulls.

    Backup server has it’s own credentials database, machines being backed up have their own database. Backup service in backup server uses appropriate credentials from machine being backed up to access the data there (shares, etc). So credentials from compromised machine are unrelated to credentials for backup server.

    And if backups are done properly (full on a schedule, daily incrementals, or something similar) you should be able to revert to a known-good state with minimal data loss.