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
For the record, I prefer NFS
And now I think we may have the answer....
OK so that command is for LXCs, and not for VMs. If youre doing a full VM, we'd mount NFS directly inside the VM.
Did you make an LXC or a VM for 102?
If its an lxc, we can work out the command and figure out what's going on.
If its a VM, we'll get it mounted with NFS utils, but how is going to depend on what distribution you've got running on there (different package names and package managers)
Ah, that distinction makes sense...I should've thought of that
So for the record, my Jellyfin-lxc is 101 (SMB mount, problematic) and my catch-all Docker VM is 102 (haven't really connected anything, and I don't care how it's done as long as performance is fine)
Ok we can remove it as an SMB mount, but fair warning a few bits of CLI to do this thoroughly.
systemctl list-units "*.mount"That said - I like to be sure, so lets do a few more things.
umount -R /mnt/pve/thatshare- Totally fine if this throws an errorcat /proc/mounts- a whooole bunch of stuff will pop up. Do you see your network share listed there? If so, lets go ahead and delete that line.nano /proc/mounts, find the line if its still there, and remove it.ctrl+xthenyto save.Ok, you should be all clear. Lets go ahead and reboot one more time just to clear out anything if you had to make any further changes. If not, lets re-add.
Go ahead and add in the NAS using NFS in the storage section like you did previously. You can mount to that same directory you were using before. Once its there, go back into the Shell, and lets do this again:
ls -la /mnt/pve/thenameofyourmount/Is your data showing up? If so, great! If not, lets find out whats going on.
Now lets add back to your container mount. You'll need to add that mount point back in again with:
pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media(however you had it mounted before in that second step).Now start the container, and go to the console for the container.
ls -la /whereveryoumountedit- if it looks good, your JF container is all set and now working with NFS! Go back to the options section, and enable "Start at Boot" if you'd like it to.Onto the VM, what distribution is installed there? Debian, fedora, etc?
Well, now the jelly lxc is failing to boot "run_buffer: 571 Script exited with status 2 Lxc_init: 845 failed to run lxc.hook.pre-start for container "101""
But the mount seems stable now. And the VM is Debian 12
That usually means something has changed with the storage, I'd bet there is a lingering reference in the .conf to the old mount.
The easiest? Just delete the container, start clean. Thats what nice about containers by the way! The harder would be mounting the filesystem of the container, and taking a look at some logs. Which route do you want to go?
For the VM, its really easy. Go to the VM, and open up the console. If you're logging in as root, commands as is, if you're logging in as a user, we'll need to add a sudo in there (and maybe install some packages / add the user to the sudoers group)
apt update && apt upgradeapt install nfs-commonmkdir /mnt/NameYourMountsudo mount -t nfs 192.168.1.100:/share/dir /mnt/NameYourMountls -la /mnt/NameYourMount. If you have an issue here, pause and come back and we'll see whats going on.nano /etc/fstab192.168.1.100:/share/dir /mnt/NameYourMount nfs defaults,x-systemd.automount,x-systemd.requires=network-online.target 0 0ctrl+xthenyls -la /mnt/NameYourMountto confirm you're all setI solved the LXC boot error; there was a typo in the mount (my keyboard sometimes double presses letters, makes command lines rough).
So just to recap where I am: main NAS data share is looking good, jelly's LXC seems fine (minus transcoding, "fatal player error"), my "docker" VM seems good as well. Truly, you're saving the day here, and I can't thank you enough.
What I can't make sense of is that I made 2 NAS shares: "A" (main, which has been fixed) and "B" (currently used docker configs). "B" is correctly connected to the docker VM now, but "B" is refusing to connect to the Proxmox host which I think I need to move Jellyfin user data and config. Before I go down the process of trying to force the NFS or SMB connection, is there any easier way?
Great!
Transcoding we should be able to sort out pretty easily. How did you make the lxc? Was it manual, did you use one of the proxmox community scripts, etc?
For transferring all your JF goodies over, there are a few ways you can do it.
If both are on the NAS, I believe you said you have a synology. You can go to the browser and go to http://nasip:5000/ and just copy around what you want if its stored on the NAS as a mount and not inside the container. If its inside the container only its going to be a bit trickier, like mounting the host as a volume on the container, copying to that mount, then moving around. But even Jellyfin says its complex - https://jellyfin.org/docs/general/administration/migrate/ - so be aware that could be rough.
The other option is to bring your docker container over to the new VM, but then you've got a new complication in needing to pass through your GPU entirely rather than giving the lxc access to the hosts resource, which is much simpler IMO.
I used the community script's lxc for jelly. With that said, the docker compose I've been using is great, and I wouldn't mind just transferring that over 1:1 either...whichever has the best transcoding and streaming performance. Either way, I'm unfortunately going to need a bit more hand-holding
LXC is going to be better, IMO. And we can definitely get hardware acceleration going.
So first, let's do this from the console of the lxc:
Is there something like card0 and renderD128 listed?
LXC is fine with me, the "new Jellyfin" instance is mostly working anyway. It just has a few issues:
And yes, I see card0 and renderD128 entries. 'vainfo' shows VA-API version: 1.20 and Driver version: Intel iHD driver...24.1.0
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
It definitely is, especially if you get a cluster going. FWIW, my media is all on a synology NAS (well technically two, but one is a backup) that I got used through work, so your setup isn't the wrong approach (imo) by any stretch.
What it comes down to in the connection is how you look at it - with a VM, its a full fledged system, all by its lonesome, that just happens to live inside another computer. A container though is an extension of that host, so think of it less like a VM and more like resource sharing, and you'll start to see where the different approaches have different advantages.
For example, I have transcode nodes running on my proxmox cluster. If I had JF as a VM, I'd need another GPU to do that - but since its a container for both JF and my transcode node, they get to share that resource happily. Whats the right answer is always going to depend on individual needs though.
And glad I could be of some help!