+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Playback Error. Playback failed due to a fatal player error. (/t-solved-playback-error-playback-failed-due-to-a-fatal-player-error)
Pages:
1
2
RE: Playback Error. Playback failed due to a fatal player error. - jelly - 2024-07-11
I tried again, it says this
Pastebin’s SMART filters have detected potentially offensive or questionable content in your Paste.
The content you are trying to publish has been deemed potentially offensive or questionable by our filters, because of this you’re receiving this warning.
This Paste can only be published with the visibility set to "Private".
RE: Playback Error. Playback failed due to a fatal player error. - TheDreadPirate - 2024-07-11
Try zipping the file and just attaching it to a forum post.
RE: Playback Error. Playback failed due to a fatal player error. - jelly - 2024-07-11
here it is
RE: Playback Error. Playback failed due to a fatal player error. - TheDreadPirate - 2024-07-11
How are you starting Jellyfin? Are you running the docker command directly or using docker compose?
Also, looking at the tutorial and the output from docker inspect, you are not putting your permanent Jellyfin data in a private location. It is in /var/lib/docker/volumes. Which is technically fine, but not ideal.
The log confirms that it is A) looking in the right place for ffmpeg and B) failing to find it for some reason.
Try doing this.
1) Stop the jellyfin container.
2) Run this command. "sudo docker system prune -a". This will delete the temporary file system the container created (will not delete permanent data).
3) Start the jellyfin container. The previous command will force docker to pull down the jellyfin image again and recreate the virtual file system. Including, hopefully, jellyfin-ffmpeg within that virtual file system.
RE: Playback Error. Playback failed due to a fatal player error. - jelly - 2024-07-12
Hellooo. I was using docker (not compose)
Everything is working now
Now my family is watching a movie.
This is what I did...
Did 1 and 2.
Then I looked the official installation guide https://jellyfin.org/docs/general/installation/container
I used docker compose this time.
This is the docker-compose.yml file:
services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
network_mode: 'host'
volumes:
- /home/USER/docker/jellyfin/config
config- /home/USER/docker/jellyfin/cache
cache- type: bind
source: /home/USER/nfs_share/qbittorrent/downloads/media
target: /media
restart: 'unless-stopped'
I did 'docker compose up -d'...
And then it worked!!!.
I need to say that there were some failed attempts before I succeded using your solution, mostly because of tweaks on the docker-compose.yml file, but I stopped and pruned the jellyfin container before a new attempt.
I have a last question: there are some extra steps that I need to take to fully clean my server? I mean like deleting the docker volumes and things like that.
I'm very grateful for your time, patience and consideration
PD:
What I think caused this issue was this...
When I used 'docker pull jellyfin/jellyfin' I had some network problems, then I had to run this a lot of times. Then I solved my problem using this
https://stackoverflow.com/questions/47580528/error-response-from-daemon-get-https-registry-1-docker-io-v2-dial-tcp-look
But maybe this caused a file to be corrupt
I also had some blackouts here when setting jellyfin up
RE: Playback Error. Playback failed due to a fatal player error. - TheDreadPirate - 2024-07-12
The prune should have already cleaned up all the temporary data. If you have nothing you want to preserve from the previous instance, we can delete the volumes that you had created.
Code:
sudo docker volume lsThis will list out the remaining volumes. Based on the tutorial you probably called them jellyfin-config and jellyfin-cache
Code:
sudo docker volume inspect jellyfin-config jellyfin-cacheThis will show you info about it, including verifying that this is the volume located at /var/lib/docker/volumes. If so...
Code:
sudo docker volume rm jellyfin-config jellyfin-cacheThat should finish cleaning up the previous instance.
RE: Playback Error. Playback failed due to a fatal player error. - jelly - 2024-07-12
Done. Thank you again
RE: Playback Error. Playback failed due to a fatal player error. - nathan15065 - 2024-08-16
Hello, I have the same problem but am not very tech savvy at all. Where do I go in to do stuff with the command line? Im not even sure where the command line is.
RE: Playback Error. Playback failed due to a fatal player error. - TheDreadPirate - 2024-08-16
(2024-08-16, 07:01 PM)nathan15065 Wrote: Hello, I have the same problem but am not very tech savvy at all. Where do I go in to do stuff with the command line? Im not even sure where the command line is.
What OS are you running? And what problem do you have? Can you share your jellyfin logs via pastebin?
RE: Playback Error. Playback failed due to a fatal player error. - puloxtor - 2024-09-23
I had the same issue where a movie wouldn’t play in Jellyfin, and I kept getting a “Playback failed due to a fatal player error.” message. After some troubleshooting, I discovered that the file wouldn’t play because it was being seeded in qBittorrent.
The solution turned out to be pretty simple: I just had to stop the file from being seeded in qBittorrent, and then Jellyfin played it perfectly!
#My Setup
Here’s a quick rundown of my setup:
Proxmox VE: Running as my virtualization platform.
Ubuntu LXC: I have an unprivileged LXC container with Ubuntu running Docker running Jellyfin.
I’m using hardlinks between the files I download and the ones Jellyfin plays. This way, I don’t have to duplicate files in my storage.
#Conclusion
So if you run into a similar issue with Jellyfin, check if you have active downloads or files being seeded in qBittorrent. Stopping those downloads might just solve your playback problems!
Hope this helps someone out there!