Accessing my server through the url provided in Jellyfin quick start - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions) +--- Thread: Accessing my server through the url provided in Jellyfin quick start (/t-accessing-my-server-through-the-url-provided-in-jellyfin-quick-start)

Accessing my server through the url provided in Jellyfin quick start - severed - 2025-02-19 Hi! I am on CachyOS and have downloaded Jellyfin packages from the extra and cachyos repos. I was able to set up my server last night, but got stuck on adding files to my library and called it a night. Today I entered the url provided in the quick start guide to continue where I left off, but cannot access my server through the url. I am also a newbie to Linux and setting up any kind of server or anything related to networking, so I'm having a hard time knowing how to find documentation to help me for what I'm doing wrong. Any advice as to what I'm doing wrong? RE: Accessing my server through the url provided in Jellyfin quick start - TheDreadPirate - 2025-02-19 What, exactly, are you typing into your browser to access your Jellyfin? And does the CachyOS dashboard say that Jellyfin is running? RE: Accessing my server through the url provided in Jellyfin quick start - severed - 2025-02-20 I cannot see anywhere in my system or network information that I recognise as Jellyfin server running. I tried to access http://SERVER_IP:8096 with my ip instead of "SERVER_IP", but my browser says it can't find or access, though it did access it the night before, so my server is down maybe? I tried reinstalling jellyfin packages, but it says "libva-mesa-driver-1:24.2.6-3 and mesa-1:24.3.4-2 are in conflict", could this be a source of my issues? RE: Accessing my server through the url provided in Jellyfin quick start - TheDreadPirate - 2025-02-20 I have no idea. Arch is a whole different beast I am not familiar with. But a package conflict could 100% break Jellyfin or prevent it from installing properly altogether. Perhaps you could setup Docker and install Jellyfin that way? This would avoid package conflicts.