hetayy 3 Posted July 18, 2025 Posted July 18, 2025 I've recently setup a new instance of Emby on CachyOS- a Linux Arch relative. Emby is able to view the currently configured library "Movie" and it's contents. But each time I attempt to play anything I get the error: "No compatible streams are currently available. Please try again later or contact your system administrator for details." At first I thought it was just a permissions issue and I hadn't given 'emby' rights to the files. I attempted to adjust permissions multiple times, the "Movie" library folder is fully accessible, and again Emby is able to display the contents entirely, just can't play the files. I attempted to add the user 'emby' to the group I made during the process, following along with the guide I'll link below, but always got the error that the user 'emby' does not exist. I could make the user manually, but I don't feel like this quite makes sense so continued poking around. Here's the guide I was following for permissions: https://wiki.archlinux.org/title/Emby While looking in my Emby logs I find this line in the error report, which I believe is happening each time I try to play anything. Quote System.ComponentModel.Win32Exception: System.ComponentModel.Win32Exception (2): An error occurred trying to start process '-ffprobe' with working directory '/home/hetayy'. No such file or directory That directory does exist. I'm not even sure it's relevant but I can't find anything else that stands out to me right now. If I had hair to pull out I'd be starting to. embyserver.txt
hetayy 3 Posted July 18, 2025 Author Posted July 18, 2025 I have discovered I am able to play the media on the Emby server from other devices. But not from my computer where the server is hosted. It effects all media.
Solution hetayy 3 Posted July 18, 2025 Author Solution Posted July 18, 2025 I've figured it out and feel a fool, but a happy fool! I had been starting the Emby server by simply running "emby-server" in my terminal which was running it as my user account. Needed to run "systemctl start emby-server". Was just too excited to get Emby up and going I suppose. Everything now works properly. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now