1. Are you running as the systemd service?
2. “Find” as in it doesn’t know where your folders are or “find” as in you told it where the media is but they’re not showing up? If former, configure your libraries in the UI. If latter, check logs, its probably a permissions issue.
3. Can you log in to the webui from the host machine itself? If so but not other devices on the LAN, then there’s a probably a setting somewhere that’s set to 127.0.0.1 that should be 0.0.0.0.

Automatic Mapping

If a user already exists on one or more connected servers, they can log in directly with their existing Jellyfin credentials. Jellyswarrm will automatically create a local user and set up the necessary server mappings.

If the same username and password exist on multiple servers, Jellyswarrm will link those accounts together automatically. This provides a smooth experience, giving the user unified access to all linked servers.

Really should audit the implementation of that feature. So when you first log in it automatically sends you’re credentials to every connected server?

I always thought this would make more sense to implement client side in the media player. But its probably easier to implement this way.

Regarding the specific issues mentioned: Nvidia support is subpar on Linux. There’s many distros that are specifically designed to handle all the graphics support for gaming and Ubuntu isn’t one of them.

Little bit of lore here: When I first started using Linux Nvidia support was better than ATI because they actually bothered to maintain a proprietary Linux driver. There were open source drivers for both but they weren’t performant. The proprietary ATI driver existed but it was maintained by one dude and required a goat sacrifice to install correctly. Since then, however, maybe after AMD bought ATI, they started investing in the open source driver. After that the open source driver just works and competes with the proprietary Nvidia driver. After that I’ve been brand loyal to AMD.

LibreWolf chewing up 3.2Gb is regrettably just normal for a modern browser. Firefox and Chrome will do this too. I’d be genuinely impressed though if Vivaldi has avoided that.

I don’t want to fault people for avoiding Arch’s instability in general but this is a very minor issue.

VLC is not a system critical package. I absolutely understand the mods choice to not put it in the RSS. At most they could put a notice in the pacman logs when it updates.

Interesting read. It sounds like that issue came upstream from Debian not Ubuntu though.

deprecating ffmpeg for half a year

wut

*btw

Not them but for me its LUKS on LVM for desktops. For laptops, archinstall with LVM on LUKS is sufficient.

SNAP BAD

About 10 years ago it was The Distro for first time linux users to prove they were a True Linux Enjoyer. Think a bunch of channers bragging about how they are the true linux master race because they edited a grub config.

Before Arch that role belonged to Gentoo. Since then that role has transitioned to NixOS who aren’t nearly as toxic but still culty. “Way of the future” etc.

All three of have high bars of entry so everyone has to take pride in the effort they put in to learn how to install their distro. Like getting hazed into a frat except you actually learn something.

The Ubuntu hatred is completely unrelated. That has to do with them being a corporate distro that keep making bad design decisions. And their ubiquity means everyone has to deal with their bad decisions. (snap bad)

Sounds like you don’t need the VPS then. Add a subdomain to your home IP. Port forward 443 and 80 to the sever. Run caddy to route the subdomain to localhost:8096. You will also need to tell jellyfin to accept on the new domain.

5 actually because you can use minimal hardware. You can probably just port forward your router and run caddy on the same jellyfin server but then expose your home IP address.

Obscuring home IP is the big one. You also don’t have to fiddle with opening ports on your router and maybe getting ISP attention for hosting on a residential network. But really obscuring home IP address would work.

Dirt simplest solution is caddy on the same jellyfin server and port forward 443 and 80 on your router to that host. Hopefully letsencrypt will work without a domain but I’m not sure.

But I ran into challenges getting my server safely accessible for users outside my LAN

FWIW:

1. vps + domain (optional?)
2. connect vps to home server with wireguard (eg Tailscale)
3. reverse proxy on the VPS forwarding to jellyfin (eg Caddy)

Obviously not as trivial or seamless as Plex. Also I wouldn’t try to complicate this setup by using docker for everything. But once its up you can basically host whatever you want on the WAN from your LAN.

I run commands as the root user so I use the root users configs. Usually that’s in /root/.config/ but it might be different in NixOS.

You’ll have to either copy your configs over to the root users config dirs. I highly recommend auditing what you copy though for security.

Every service is doing this as expenses and interest rates go up. Its the driving force of enshittification. All the VCs want internet startups to finally turn a profit.

It was there first and you can share it with friends more easily. For Plex you just register with the central server and share your username with your friends or w/e. Jellyfin has nothing like that.

If you even write one line of bash you are programming. The way you’re describing it only makes sense if you’re using the terminal like dmenu_run. You metaphor breaks down the moment someone so much as uses cd. Even worse once you throw a pipe or redirect in. All of this you absolutely will have to do when installing Arch.

Its absolutely irresponsible to tell people that installing and running Arch Linux is like talking to a discord bot.

If you’re mindlessly pasting commands, sure… but you have zero idea what your fucking with if you think bash is simpler than HTML.

In the context of maintaining an Arch distro you will absolutely need to understand that executing CLI commands is in fact programming.