Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)L
Posts
6
Comments
81
Joined
3 yr. ago

  • So should I be disabling some hardware decoding options then?

  • QSV and '/dev/dri/renderD128'. I'll switch to VAAPI and see... Edit: no luck, same error

  • 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."

  • LXC is fine with me, the "new Jellyfin" instance is mostly working anyway. It just has a few issues:

    1. Config and user data from "old Jellyfin" isn't there and doesn't want to connect. I tried connecting my NAS's docker data to Prox host like the previous mount, but it doesn't like it.
    2. Aforementioned HWA errors (I'm guessing I checked an incorrect box)
    3. Most data from the NAS isn't showing up. I added all libraries and did a full rescan and reboot, but most of the media still isn't there. I'm hoping passing config data will fix that

    And yes, I see card0 and renderD128 entries. 'vainfo' shows VA-API version: 1.20 and Driver version: Intel iHD driver...24.1.0

  • 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

  • I 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?

  • Thanks! Its not easy, but I don't give up. Took me 3 years to get the *arrs running, but I eventually got it

  • 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

  • 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)

  • Yes! I do

  • Are there different rules for a VM with that command? I made a 2nd NAS share point as NFS (SMB has been failing, I'm desperate, and I don't know the practical differences between the protocols), and Proxmox accepted the NFS, but the share is saying "unknown." Regardless, I wanted to see if I could make it work anyway so I tried 'pct set 102 -mp1 /mnt/pve/NAS2/volume2/docker,mp=/docker'

    102 being a VM I set up for docker functions, specifically transferring docker data currently in use to avoid a lapse in service or user data.

    Am I doing this in a stupid way? It kinda feels like it

  • I restarted everything like you suggested, same 'showmount' result unfortunately...I double checked the SMB mount in the datacenter, and the settings look correct to me. The NAS's storage icon shows that it's connected, but it seems like that doesn't actually mean it's *firmly *connected

  • So I got Jellyfin running last night as an unprivileged LXC using a community script. It's accessible via web browser, and I could connect my NAS. Now I'm having NAS-server connection issues and "fatal player" issues on certain items. I appreciate the support, I'm going to need a lot of it haha

  • Well, this is the first step in me eventually dropping Windows (assuming all goes well). I'd like to wipe my main PC and do a dual-boot situation eventually, but migrating services to an actual server takes priority...got kiddos counting on their cartoons, can't let em down

  • "Hosts on 192.168.0.4:" As a novice, I get the feeling that means it's not working

  • That's good to know at least. I was getting anxious last night thinking that I signed up for something I'd never get running. So curl is working now...not sure why it wasn't earlier, but I've used it since and it is confirmed working. And networking (as in internet connectivity) is working, but now I'm struggling with the NAS mount: it was working perfectly at first, but now it's randomly shifting between "available" and "unknown".

  • Well, the plan was to use a couple VMs for niche things that I'd love to have and many services. But if I can't get Proxmox working as advertised, I'll throw most of that out of the window

  • Interesting, what browser do you use? Sounds like I may have to switch from Firefox if that's the case because this lack of quality of life is ridiculous

  • Probably hundreds of hours, but very little was in a functional desktop...most of it was trying to get an install to boot and update software (I'm not joking).