LazerDickMcCheese

joined 2 years ago

Just to repeat what you're already hearing: if I started over from the beginning, I'd skip a NAS entirely and just build a server with a ton of bays (which I just bought). Funny enough, I came here to recommend Fractal Design cases too

Ah, I thought operation didn't matter, my bad

[–] LazerDickMcCheese@sh.itjust.works 1 points 3 days ago (2 children)

Faraday cage?

[–] LazerDickMcCheese@sh.itjust.works 2 points 4 days ago (1 children)

Let the record show that irmadlad saved the day here. I learned a lot about what I needed and no longer have to concern myself with something beyond my comprehension

Thank you, that's really solid advice. It turns out my efforts may have been misguided anyway. I think I was under the impression that "internet exposure" and "Cloudflare tunnel" had similar setups

I thought my VPN didn't, but they continue to disappoint me. According to the internet, my VPN is using CGNAT

[–] LazerDickMcCheese@sh.itjust.works 2 points 4 days ago (3 children)

See, this just shows how much I need to learn...I thought what I was trying to set up *was *the same thing as a "Cloudflare tunnel." Honestly, don't care how it gets implemented, I just assumed this was the easy way because that's what all the youtubers were suggesting. My end goal here is "I'm on my phone 100 miles away from home, open Jellyfin/Nextcloud/whatever, use domain.actually.works" without needing to disable my Proton/Air/Mullvad connection.

But I've followed 4 or 5 "you won't believe how easy Nginx is" tutorials, and they're not working for me...

[–] LazerDickMcCheese@sh.itjust.works 1 points 4 days ago* (last edited 4 days ago)

Ok, this is an extensive answer (thank you), but also a lot to unpack. Before I go making a bridge network, I wanna make sure I'm following you. I'm pretty inexperienced with self-hosting in general outside of Docker, but I'm especially a novice with anything networking so pardon my ignorance here.

Yes, Jellyfin is accessible locally. Performance is the best I've ever seen it too. I uninstalled Tailscale on my Ubuntu server (it was causing networking issues, frankly I didn't understand how) and removed it from my tailnet dashboard, but Jellyfin is still remotely accessible via Tailscale (which is fine, I guess).

At this point, my users and I are trying to avoid Tailscale on mobile devices when possible. Two reasons: 1. prevents maintaining regular VPN usage (deal breaker for a couple people) 2. switching between home wifi and mobile drops connectivity, required turning networking off and on again (deal breaker for me, I got spoiled by Synology's reverse proxy and can't go back)

From what I can tell, there's no CGNAT trickery at play (actually the internet says otherwise). My DNS is a local Pihole+Unbound, in case that matters. The Ubuntu IP is static. Were you requesting the yaml of Jellyfin or Nginx?

And I believe I was hoping to set up a "Cloudflare tunnel." I think I was under the impression that this "tunnel" *is *a reverse proxy.

br-04577e8d1ec8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.27.0.1 netmask 255.255.0.0 broadcast 172.27.255.255 inet6 fe80::f43a:6cff:fe6e:6f74 prefixlen 64 scopeid 0x20 ether f6:3a:6c:6e:6f:74 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-059b78f628b4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255 inet6 fe80::18:abff:fee0:3eb3 prefixlen 64 scopeid 0x20 ether 02:18:ab:e0:3e:b3 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-0a5f3a65b300: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255 inet6 fe80::e00e:50ff:fe65:836 prefixlen 64 scopeid 0x20 ether e2:0e:50:65:08:36 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-1945efd955e7: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.26.0.1 netmask 255.255.0.0 broadcast 172.26.255.255 inet6 fe80::8c68:a5ff:fe3a:9873 prefixlen 64 scopeid 0x20 ether 8e:68:a5:3a:98:73 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-3d620c7c2cae: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.22.0.1 netmask 255.255.0.0 broadcast 172.22.255.255 inet6 fe80::c2b:66ff:fe94:2b49 prefixlen 64 scopeid 0x20 ether 0e:2b:66:94:2b:49 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-460d6535b2c5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.24.0.1 netmask 255.255.0.0 broadcast 172.24.255.255 inet6 fe80::642c:cfff:fe44:dbdc prefixlen 64 scopeid 0x20 ether 66:2c:cf:44:db:dc txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-475a728d1c35: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.23.0.1 netmask 255.255.0.0 broadcast 172.23.255.255 inet6 fe80::ccd2:f8ff:fe28:3421 prefixlen 64 scopeid 0x20 ether ce:d2:f8:28:34:21 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-4f0e4b158e77: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255 ether 6a:b9:50:03:81:49 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-523dfe276b24: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.29.0.1 netmask 255.255.0.0 broadcast 172.29.255.255 inet6 fe80::c489:10ff:fe7d:c60b prefixlen 64 scopeid 0x20 ether c6:89:10:7d:c6:0b txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-57763f5382b6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.28.0.1 netmask 255.255.0.0 broadcast 172.28.255.255 inet6 fe80::74a5:7ff:fe65:c6ef prefixlen 64 scopeid 0x20 ether 76:a5:07:65:c6:ef txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-598a0f745a98: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255 inet6 fe80::c66:3aff:feb9:911e prefixlen 64 scopeid 0x20 ether 0e:66:3a:b9:91:1e txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-ab783b77c95c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.31.0.1 netmask 255.255.0.0 broadcast 172.31.255.255 inet6 fe80::649f:6bff:fe13:2fe8 prefixlen 64 scopeid 0x20 ether 66:9f:6b:13:2f:e8 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-bef45e98255d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255 inet6 fe80::cc5f:6bff:fe87:b447 prefixlen 64 scopeid 0x20 ether ce:5f:6b:87:b4:47 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-f48ae7f54dbb: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.30.0.1 netmask 255.255.0.0 broadcast 172.30.255.255 inet6 fe80::d437:84ff:feb2:ca4a prefixlen 64 scopeid 0x20 ether d6:37:84:b2:ca:4a txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::cc6:caff:fe43:79a9 prefixlen 64 scopeid 0x20 ether 0e:c6:ca:43:79:a9 txqueuelen 0 (Ethernet) RX packets 1783 bytes 1910011 (1.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1922 bytes 351712 (351.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.44 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::9e6b:ff:fea5:51f prefixlen 64 scopeid 0x20 ether 9c:6b:00:a5:05:1f txqueuelen 1000 (Ethernet) RX packets 4387465737 bytes 6336735875164 (6.3 TB) RX errors 0 dropped 8 overruns 0 frame 0 TX packets 754588388 bytes 573935751223 (573.9 GB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 127840 bytes 10957792 (10.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 127840 bytes 10957792 (10.9 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth0775369: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::cc3c:2cff:fe9c:5db0 prefixlen 64 scopeid 0x20 ether ce:3c:2c:9c:5d:b0 txqueuelen 0 (Ethernet) RX packets 221480 bytes 212832018 (212.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 254661 bytes 202198400 (202.1 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth0c0ea06: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::38e3:cfff:fe9d:bb11 prefixlen 64 scopeid 0x20 ether 3a:e3:cf:9d:bb:11 txqueuelen 0 (Ethernet) RX packets 194122 bytes 19377179 (19.3 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 354068 bytes 582336025 (582.3 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth10feba1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::ecf5:74ff:fe18:8241 prefixlen 64 scopeid 0x20 ether ee:f5:74:18:82:41 txqueuelen 0 (Ethernet) RX packets 481334 bytes 63464919 (63.4 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 455170 bytes 820601446 (820.6 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth1d28ecf: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::bca2:b6ff:fec1:86f1 prefixlen 64 scopeid 0x20 ether be:a2:b6:c1:86:f1 txqueuelen 0 (Ethernet) RX packets 75387 bytes 11145936 (11.1 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 40041 bytes 255176942 (255.1 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth1e42990: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::2052:25ff:fe39:703 prefixlen 64 scopeid 0x20 ether 22:52:25:39:07:03 txqueuelen 0 (Ethernet) RX packets 6333109 bytes 68605366213 (68.6 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7502722 bytes 1336724524 (1.3 GB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth42cfbe1: fl

Yes, I recently got it working. So LAN connectivity is fine and strangely I can remote access it via Tailscale even though the machine isn't on a tailnet

[–] LazerDickMcCheese@sh.itjust.works 2 points 5 days ago (2 children)

The whole reason I bought the domain is because I was told to stop using Tailscale for this purpose. I'm so confused...

[–] LazerDickMcCheese@sh.itjust.works 1 points 1 week ago (1 children)

it's full duplex

 

I followed YouTube videos and all my domain points to is "server not found." My domain is through Cloudflare. My server's ports have been opened at the router.

Proxy Host Settings: Domain name: newly.registered.domain Scheme: http (I've tried https too) Forward hostname/IP: local.server.ip.v4 Forward port: jelly_port Access list: Publicly accessible SSL: *.newly.registered.domain

I'd love to share my certificate info, but I don't see a way to do that...but I set up the DNS thingy with a Cloudflare API token. I remember typing in my server's public IP here too. Took many tries, but it finally accepted the settings as valid.

So what am I missing to get a reverse proxy? I thought it was supposed to work after all of that.

I've been trying to get this going for so long that it just feels like I'm beating my head against the wall until it randomly works, ya know?

 

This is my first real dive into hosting a server beyond a few Docker containers in my NAS. I've been learning a lot over the past 5 days, first thing I learned is that Proxmox isn't for me:

https://sh.itjust.works/post/49441546 https://sh.itjust.works/post/49272492 https://sh.itjust.works/post/49264890

So now I'm running headless Ubuntu and having a much better time! I migrated all of my Docker stuff to my new server, keeping my media on the NAS. I originally set up an NFS share (NAS->Server) so my Jellyfin container could snag the data. This worked at first, quickly crumbled without warning, and HWA may or may not be working.

Enter the Jellyfin issue: transcoded playback (and direct, doesn't matter) either give "fatal player error" or **extremely **slow, stuttery playback (basically unusable). Many Discord exchanges later, I added an SMB share (same source folder, same destination folder) to troubleshoot to no avail, and Jellyfin-specific problems have been ruled out.

After about 12hrs of 'sudo nano /etc/fstab' and 'dd if=/path/to/nfs_mount/testfile of=/dev/null bs=1M count=4096 status=progress', I've found some weird results from transferring the same 65GB file between different drives:

NAS's HDD (designated media drive) to NAS's SSD = 160MB/s NAS's SSD to Ubuntu's SSD = 160MB/s NAS's HDD to Ubuntu's SSD = .5MB/s

Both machines are cat7a ethernet straight to the router. I built the cables myself, tested them many times (including yesterday), and my reader says all cables involved are perfectly fine. I've rebooted them probably a fifty times by now.

NAS (Synology DS923+): -32GB RAM -Seagate EXOS X24 -Samsung SSD 990 EVO

Ubuntu: -Intel i5-13500 -Crucial DDR5-4800 2x32GB -WD SN850X NVMe

If you were tasked with troubleshooting a slow mount bind between these two machines, what would you do to improve the transfer speeds? Please note that I cannot SSH into the NAS, I just opened a ticket with Synology about it.

Here's the current /etc/fstab after extensive Q&A from different online communities

NFS mount: 192.168.0.4:/volume1/data /mnt/hermes nfs4 rw,nosuid,relatime,vers=4.1,rsize=13>

SMB mount: //192.168.0.4/data /mnt/hermes cifs username=_____,password=_______,vers=3.>

 

cross-posted from: https://sh.itjust.works/post/49393596

I've been running Jellyfin on a Synology DS923+ for a couple years with 'linuxserver/jellyfin:latest' with no issue until that big update recently. Suddenly it's borked...extremely slow speeds, failing to play files half the time, stuttering even when it does play. It was time for a hardware update regardless; it was a miracle that the NAS was able to run as many services on it as it was anyway.

So I built a Proxmox machine with the intent of adding hardware acceleration and transcoding (ideally I'd like to stream to a couple old CRTs): -ASRock B760M PRO RS -Intel i5-13500 -2x32GB Crucial DDR5-4800 -1TB WD SN850X NVMe

Using the Proxmox community Jellyfin script (https://community-scripts.github.io/ProxmoxVE/scripts?id=jellyfin&category=Media+%26+Streaming) I set up an LXC and the iGPU is supposedly being utilized properly. I added an NFS mount from the NAS's media folder to the Proxmox host, then bound the mount point to the LXC. So at this point, it is accessible to clients via web browser, but I'm having a few issues:

  1. (Probably a Prox issue but...) Jellyfin isn't seeing all the media. I added all the libraries and did a full scan, but *maybe *10% of the media is actually available. Hopefully this is a moot point because--

  2. My old docker config isn't available. I made an NFS mount from the NAS's docker folder to the Proxmox host and tried to route it to the LXC as well, but the Proxmox-NAS refuses to work so I'd need a workaround.

  3. I have no idea if my transcoding settings are right. Intel's specs for my CPU and Jellyfin's recommendations seems to conflict slightly, but between both sets of info there's still some settings that lack guidance. Basically, can someone with a computer engineering degree double check my settings? I tried a screenshot, but Lemmy didn't appreciate it

Hardware acceleration: Intel Quicksync (QSV) QSV Device: /dev/dri/renderD128

X H264

X HEVC

MPEG2

VC1

VP8

X VP9

X AV1

HEVC 10bit

VP9 10bit

HEVC RExt 8/10bit

HEVC RExt 12bit

X Prefer OS native DXVA or VA-API hardware decoders

X Enable hardware encoding

Enable Intel Low-Power H.264 hardware encoder

Enable Intel Low-Power HEVC hardware encoder

X Allow encoding in HEVC format

Allow encoding in AV1 format

Edit: forgot to include logs: "ffmpeg version 7.1.2-Jellyfin Copyright (c) 2000-2025 the FFmpeg developers built with gcc 13 (Ubuntu 13.3.0-6ubuntu2~24.04) configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto=auto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libharfbuzz --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc libavutil 59. 39.100 / 59. 39.100 libavcodec 61. 19.101 / 61. 19.101 libavformat 61. 7.100 / 61. 7.100 libavdevice 61. 3.100 / 61. 3.100 libavfilter 10. 4.100 / 10. 4.100 libswscale 8. 3.100 / 8. 3.100 libswresample 5. 3.100 / 5. 3.100 libpostproc 58. 3.100 / 58. 3.100 [AVHWDeviceContext @ 0x7ab87d07ffc0] No VA display found for device /dev/dri/renderD128. Device creation failed: -22. Failed to set value 'vaapi=va:/dev/dri/renderD128,driver=iHD' for option 'init_hw_device': Invalid argument Error parsing global options: Invalid argument"

"[WRN] The WebRootPath was not found: "/var/lib/jellyfin/wwwroot". Static files may be unavailable. [ERR] FFmpeg exited with code 234"

Edit: appreciate all the help!

 

I've been running Jellyfin on a Synology DS923+ for a couple years with 'linuxserver/jellyfin:latest' with no issue until that big update recently. Suddenly it's borked...extremely slow speeds, failing to play files half the time, stuttering even when it does play. It was time for a hardware update regardless; it was a miracle that the NAS was able to run as many services on it as it was anyway.

So I built a Proxmox machine with the intent of adding hardware acceleration and transcoding (ideally I'd like to stream to a couple old CRTs): -ASRock B760M PRO RS -Intel i5-13500 -2x32GB Crucial DDR5-4800 -1TB WD SN850X NVMe

Using the Proxmox community Jellyfin script (https://community-scripts.github.io/ProxmoxVE/scripts?id=jellyfin&category=Media+%26+Streaming) I set up an LXC and the iGPU is supposedly being utilized properly. I added an NFS mount from the NAS's media folder to the Proxmox host, then bound the mount point to the LXC. So at this point, it is accessible to clients via web browser, but I'm having a few issues:

  1. (Probably a Prox issue but...) Jellyfin isn't seeing all the media. I added all the libraries and did a full scan, but *maybe *10% of the media is actually available. Hopefully this is a moot point because--

  2. My old docker config isn't available. I made an NFS mount from the NAS's docker folder to the Proxmox host and tried to route it to the LXC as well, but the Proxmox-NAS refuses to work so I'd need a workaround.

  3. I have no idea if my transcoding settings are right. Intel's specs for my CPU and Jellyfin's recommendations seems to conflict slightly, but between both sets of info there's still some settings that lack guidance. Basically, can someone with a computer engineering degree double check my settings? I tried a screenshot, but Lemmy didn't appreciate it

Hardware acceleration: Intel Quicksync (QSV) QSV Device: /dev/dri/renderD128

X H264

X HEVC

MPEG2

VC1

VP8

X VP9

X AV1

HEVC 10bit

VP9 10bit

HEVC RExt 8/10bit

HEVC RExt 12bit

X Prefer OS native DXVA or VA-API hardware decoders

X Enable hardware encoding

Enable Intel Low-Power H.264 hardware encoder

Enable Intel Low-Power HEVC hardware encoder

X Allow encoding in HEVC format

Allow encoding in AV1 format

Edit: forgot to include logs: "ffmpeg version 7.1.2-Jellyfin Copyright (c) 2000-2025 the FFmpeg developers built with gcc 13 (Ubuntu 13.3.0-6ubuntu2~24.04) configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto=auto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libharfbuzz --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc libavutil 59. 39.100 / 59. 39.100 libavcodec 61. 19.101 / 61. 19.101 libavformat 61. 7.100 / 61. 7.100 libavdevice 61. 3.100 / 61. 3.100 libavfilter 10. 4.100 / 10. 4.100 libswscale 8. 3.100 / 8. 3.100 libswresample 5. 3.100 / 5. 3.100 libpostproc 58. 3.100 / 58. 3.100 [AVHWDeviceContext @ 0x7ab87d07ffc0] No VA display found for device /dev/dri/renderD128. Device creation failed: -22. Failed to set value 'vaapi=va:/dev/dri/renderD128,driver=iHD' for option 'init_hw_device': Invalid argument Error parsing global options: Invalid argument"

"[WRN] The WebRootPath was not found: "/var/lib/jellyfin/wwwroot". Static files may be unavailable. [ERR] FFmpeg exited with code 234"

 

Fresh Proxmox install, having a dreadful time. Trying not to be dramatic, but this is much worse than I imagined. I'm trying to migrate services from my NAS (currently docker) to this machine.

How should Jellyfin be set up, lxc or vm? I don't have a preference, but I do plan on using several docker containers (assuming I can get this working within 28 days) in case that makes a difference. I tried WunderTech's setup guide which used an lxc for docker containers and a separate lxc of jellyfin. However that guide isn't working for me: curl doesn't work on my machine, most install scripts don't work, nano edits crash, and mounts are inconsistent.

My Synology NAS is mounted to the host, but making mount points to the lxc doesn't actually connect data. For example, if my NAS's media is in /data/media/movies or /data/media/shows and the host's SMB mount is /data/, choosing the lxc mount point /data/media should work, right?

Is there a way to enable iGPU to pass to an lxc or VM without editing a .conf in nano? When I tried to make suggested edits, the lxc freezes for over 30 minutes and seemingly nothing happens as the edits don't persist.

Any suggestions for resource allocation? I've been looking for guides or a formula to follow for what to provide an lxc or VM to no avail.

If you suggest command lines, please keep them simple as I have to manually type them in.

Here's the hardware: Intel i5-13500 64GB Crucial DR5-4800 ASRock B760M Pro RS 1TB WD SN850X NVMe

 

I'm assuming this isn't normal behavior, but copying and pasting commands into shell windows (host, VMs, LXCs, doesn't matter) doesn't work. I've noticed issues with curl too, despite saying it's installed and up-to-date, but one thing at a time...I'm also not convinced that edits made to conf files are persisting as a result. Is this a browser issue? As always, thanks for helping out a normie in need.

Edit: it's taking at least 20min for a simple conf edit to save. I have to assume that's abnormal too, running a i5-13500 by the way...confirmed, not saving conf edits

17
submitted 3 weeks ago* (last edited 3 weeks ago) by LazerDickMcCheese@sh.itjust.works to c/linux@lemmy.ml
 

Hello, not much of a Linux user (situations like this are why)...but long story short, I'm trying to rehab a ROG PC from 2018.

I made a bootable USB of the current Mint distro, but booting leads to a black screen. I tried compatibility mode, but the boot process hangs on "EFI stub: Measured initrd data into PCR 9"

The PC came with an Nvidia 2080, but it's actually a 980ti. Also there isn't integrated graphics here. Any troubleshooting advice would be cool

Update: if I select recovery mode then 'resume normal boot', Mint 21 works. However, this computer will be a gift to a tech-illiterate person, so that level of input will not suffice. I installed the recommended (and correct) Nvidia driver, but the results are the same

 

Great news! I started my selfhost journey over a year ago, and I'm finding myself needing better hardware. There's so many services I want that my NAS can't handle. And I unfortunately need to add GPU transcoding to my Jellyfin setup.

What's the best OS for a machine focused on containers and (getting started with) VMs? I've heard Proxmox

What CPU specs should I be concerned about?

I'm willing to buy a pre-built as long as its hardware has sufficient longevity.

 

I see the GRUB menu, then it goes to an inactive black screen. If I select recovery then resume, it works fine. As this is supposed to be a remote machine, the problem defeats the purpose. I've heard this is usually a GPU drivers issue, so I followed the suggestions here: https://documentation.ubuntu.com/server/how-to/graphics/install-nvidia-drivers/index.html

and here (I'm running 22.04 and can't update, separate issue though): https://askubuntu.com/questions/760934/graphics-issues-after-while-installing-ubuntu-16-04-16-10-with-nvidia-graphics

Yet I still have the problem with a black screen. While I'd like it to "just work", I'm also open to extreme measures including...

-removing the GPU (assuming that would help) -having a script run that auto-selects recovery then resume then logs in on my behalf (I'd need help figuring that out though)

I also updated the grub file after adding "nomodeset", that didn't fix it either.

 

For the uninitiated, this is software for music and it's notoriously complicated. I have a paid version from about a decade ago and I'm not giving them anymore of my money. Reddit used to have a vsttorrents guide for this, but it's been forcibly removed. I'm trying to get Komplete 15 Ultimate, with all the added stuff I'll probably never even look at

Edit: if anyone sees this, I'm still looking

 

I would love to seed (and cross-seed) my music library, but metadata tagging and renaming fucks the files up. How do I set up qBittorrent and Prowlarr to keep seeding after retagging?

 

Update: it was an issue with API keys due to a previous install.

Update 2: new problem, qBittorrent has an I/O issue, probably involving the final destination for the media: my Synology NAS. Any advice here is appreciated.

Update 3: I was having issues with mapping my Synology NAS as the root folders, so I restarted the *arrs and now they are unreachable. The solution was to reinstall them without uninstalling them because my computer is weird.

Once a year I try setting up Prowlarr, Sonarr, and Radarr and I felt confident so I reinstalled them. The *arrs are connected to qBittorrent (all tests succeeded) and Prowlarr (again, tests succeeded) and vice versa. I added every indexer that I could successfully connect to (which was most of them) and currently have all of the web UIs open : which work as expected. Everything seems to be communicating and functioning as intended so I tested Radarr. I found a popular movie and started monitoring it, this was about 30 minutes ago. It hasn't shown up in qBittorrent and I'm not sure what I'm missing; can someone help me troubleshoot? In other words, how do I know definitively that this movie I have selected will download and when will it download?

view more: next ›