mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: [Latest stable 10.7.x to 10.8.0] ffmpeg not found after upgrade #3908
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mynamewastaken on GitHub (Jun 13, 2022).
Please describe your bug
After the upgrade to 10.8.0 I saw errors in the logs that
ffmpegwasn't found:I don't know that this caused any errors for me re: transcoding, but after updating the path in web ui settings to
/usr/lib/jellyfin-ffmpeg/ffmpegit was able to find it successfully. Perhaps just an informational issue that theffmpegbinary isn't being picked up properly.This is the official jellyfin container running on k3s backed by traefik as a reverse proxy (if the latter info is relevant).
Thanks,
Tim
Jellyfin Version
10.8.0
if other:
No response
Environment
Jellyfin logs
No response
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@fadenb commented on GitHub (Jun 19, 2022):
Can confirm the issue as well as the fix mentioned above.
Thanks @mynamewastaken :)
@jellyfin-bot commented on GitHub (Oct 19, 2022):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.