Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Ok lets start with that rendering - seeing those is good! You should only need to add some group access, so run this:
The output should just say "jellyfin" right now. Thats the user thats running the Jellyfin service. So lets go ahead and....
You should now see the jellyfin user as a member of jellyfin, video, and render. This gives access for the jellyfin user to make use of the gpu/hardware acceleration.
Now restart that jellyfin and try again!
Ok, consider it done! My concern is this section of the admin settings:
I followed Intel's decode/encode specs for my CPU, but there's no feedback on my selection. I'm still getting "Playback failed due to a fatal player error."
What do you have above that?
There should be a hardware acceleration dropdown, and then a device below that. Since you have /dev/dri/renderD128, that should be in the "device" field, and the Hardware Acceleration dropdown should be QSV or VAAPI (if one doesn't work, do the other)
QSV and '/dev/dri/renderD128'. I'll switch to VAAPI and see... Edit: no luck, same error
Just checked one of mine, VAAPI is where I'm set, with acceleration working. 7th or 8th gen or so on that box, so VAAPI should do the trick for you.
So should I be disabling some hardware decoding options then?
Might be a better question for someone who knows more JF ffmpeg configs, but I think the HEVC up top should be checked and the bottom range extended hevc should be unchecked. I think you should have AV1 support too.
Worst case, start with h264 and move down the list
Great point actually, time for c/jellyfin I think. Would you mind helping me with the transferal of config and user data? Is "NFS mount NAS docker data to host" > "pass NFS to jelly LXC" > "copy data from NAS folder to LXC folder" the right idea?
Also may be good for c/jellyfin, but what I'd see if you could do is leverage a backup tool. Export and download, then import, all from the web. I know there is a built in backup function, and I recall a few plugins as well that handled backups.
Seems to me that might be the most straightforward method - but again, probably better with a more jellyfin focused comm for that. I have moved that LXC around between a bunch of machines at this point, so snapshots and backups via proxmox backup server are all I need.
Yeah, it seems like the transplanting of LXCs, VMs, and docker is fairly pain-free...where I really shot myself in the foot is starting on an underpowered NAS and network transfers are clearly not my friend.
I'm not familiar with the backup stuff, but I remember hearing about it being added recently. I'll look into it, thanks for the recommendation.
You taught me a lot of stuff in just a couple days. The overwhelming/anxious part of dealing with Proxmox for me is still the pass-through of data from outside devices. VMs aren't bad at all, but everything else seems like a roll of the dice to see if the machine will allow the connection or not