[bug] [Issue]: Search is not working correctly on LAN, WAN, or with remote users. Just never loads, frequently. #6000

Closed
opened 2026-02-07 02:49:30 +03:00 by OVERLORD · 11 comments
Owner

Originally created by @Glynax on GitHub (Jun 12, 2024).

Please describe your bug

Me and a few of my friends have had a seemingly deteriorating experience with the search function. When I first spun up the server a few months ago it was all snappy and so much better than plex. But over the weeks the search has gotten so bad as to be completely unusable. Like the title says it happens on any client or browser or app we've tried, LAN, Remote or otherwise.
At first the search will attempt to work as we see the thing spinning like it's searching but we've literally let it do that for ~2 days and eventually the jellyfin UI goes blank and the spinner disappears and the search never finishes.
Doesn't seem to matter what we search, Breaking Bad, Smiling Friends, dragon ball, Bluey, etc. Playback is flawless but actually getting to and finding the specific things we want to watch is the issue. My only thought is I have rather large libraries and perhaps it's timing out or something trying to page through them? 13k movies, 2500 shows 1000 anime 700 cartoons and a few others that are pretty big like a (downloaded) youtube library and a rather large music library.
Not sure if it's related but sometimes the UI in general can take seconds to even appear so navigating through a library to find a specific thing is rather cumbersome as well. I've had a library this large the entire time, jellyfin just seemed to respond slower over the months for some reason.

Reproduction Steps

Attempt a search for any kind of media in any of my listed browsers or clients or conditions. As of the last month or so it does this almost every time we search. Of note sometimes specifically jellyfin media player on LAN works BUT not for remote and it takes several minutes to search. Browsers just spin either way.

Jellyfin Version

10.9.0

if other:

10.9.6

Environment

- OS: Ubuntu 23.10 desktop
- Linux Kernel: 6.5.0-35-generic
- Virtualization: Latest Docker, and latest Docker compose
- Clients: Desktop computer, Jellyfin media player
- Browser: Opera, Firefox, Google Chrome,
- FFmpeg Version: ffmpeg version 6.0.1-Jellyfin
- Playback Method: N/A
- Hardware Acceleration:
- GPU Model: Intel® HD Graphics 630
- Plugins: AniDB AniList AudioDB Bookshelf Cover Art Archive Fanart IMVDb Musicbrainz OMDB open subtitles playback reporting reports session cleaner skinmanager studio images tmdb tmdb box sets thetvdb theme songs themerr
- Reverse Proxy: nginx
- Base URL: /jellyfin
- Networking: Docker Bridge
- Storage: NFS shares via NAS

Compose
---
services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Detroit
      - JELLYFIN_PublishedServerUrl=192.168.0.5 #optional
      - DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel
    volumes:
      - /opt/jellyfin/library:/config
      - /media/nfs/:/media:shared
    network_mode: bridge
    ports:
      - 8096:8096
      - 8920:8920 #optional
      - 7359:7359/udp #optional
      - 1900:1900/udp #optional
    restart: unless-stopped
    devices:
      - /dev/dri:/dev/dri

Jellyfin logs

I haven't seen anything in the logs of note

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @Glynax on GitHub (Jun 12, 2024). ### Please describe your bug Me and a few of my friends have had a seemingly deteriorating experience with the search function. When I first spun up the server a few months ago it was all snappy and so much better than plex. But over the weeks the search has gotten so bad as to be completely unusable. Like the title says it happens on any client or browser or app we've tried, LAN, Remote or otherwise. At first the search will attempt to work as we see the thing spinning like it's searching but we've literally let it do that for ~2 days and eventually the jellyfin UI goes blank and the spinner disappears and the search never finishes. Doesn't seem to matter what we search, Breaking Bad, Smiling Friends, dragon ball, Bluey, etc. Playback is flawless but actually getting to and finding the specific things we want to watch is the issue. My only thought is I have rather large libraries and perhaps it's timing out or something trying to page through them? 13k movies, 2500 shows 1000 anime 700 cartoons and a few others that are pretty big like a (downloaded) youtube library and a rather large music library. Not sure if it's related but sometimes the UI in general can take seconds to even appear so navigating through a library to find a specific thing is rather cumbersome as well. I've had a library this large the entire time, jellyfin just seemed to respond slower over the months for some reason. ### Reproduction Steps Attempt a search for any kind of media in any of my listed browsers or clients or conditions. As of the last month or so it does this almost every time we search. Of note sometimes specifically jellyfin media player on LAN works BUT not for remote and it takes several minutes to search. Browsers just spin either way. ### Jellyfin Version 10.9.0 ### if other: 10.9.6 ### Environment ```markdown - OS: Ubuntu 23.10 desktop - Linux Kernel: 6.5.0-35-generic - Virtualization: Latest Docker, and latest Docker compose - Clients: Desktop computer, Jellyfin media player - Browser: Opera, Firefox, Google Chrome, - FFmpeg Version: ffmpeg version 6.0.1-Jellyfin - Playback Method: N/A - Hardware Acceleration: - GPU Model: Intel® HD Graphics 630 - Plugins: AniDB AniList AudioDB Bookshelf Cover Art Archive Fanart IMVDb Musicbrainz OMDB open subtitles playback reporting reports session cleaner skinmanager studio images tmdb tmdb box sets thetvdb theme songs themerr - Reverse Proxy: nginx - Base URL: /jellyfin - Networking: Docker Bridge - Storage: NFS shares via NAS Compose --- services: jellyfin: image: lscr.io/linuxserver/jellyfin:latest container_name: jellyfin environment: - PUID=1000 - PGID=1000 - TZ=America/Detroit - JELLYFIN_PublishedServerUrl=192.168.0.5 #optional - DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel volumes: - /opt/jellyfin/library:/config - /media/nfs/:/media:shared network_mode: bridge ports: - 8096:8096 - 8920:8920 #optional - 7359:7359/udp #optional - 1900:1900/udp #optional restart: unless-stopped devices: - /dev/dri:/dev/dri ``` ### Jellyfin logs ```shell I haven't seen anything in the logs of note ``` ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
OVERLORD added the bugstale labels 2026-02-07 02:49:30 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (Jun 12, 2024):

Hi, it seems like your issue report has the following item(s) that need to be addressed:

  • You have not filled in the environment completely.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

@jellyfin-bot commented on GitHub (Jun 12, 2024): Hi, it seems like your issue report has the following item(s) that need to be addressed: - You have not filled in the environment completely. This is an automated message, currently under testing. Please file an issue [here](https://github.com/jellyfin/jellyfin-triage-scripts/issues) if you encounter any problems.
Author
Owner

@v3DJG6GL commented on GitHub (Jun 25, 2024):

I do face the same/a similar issue: The search is super laggy and sometimes returns no results at all or takes up to a minute (or more) to return the search results.
It seems to me as this issue was introduced with the version 10.9.x
I never had so much trouble with searching back when I was using 10.8.x.
Also, my library is indeed a larger one. But that was also the case before I upgraded to v10.9.x

@v3DJG6GL commented on GitHub (Jun 25, 2024): I do face the same/a similar issue: The search is super laggy and sometimes returns no results at all or takes up to a minute (or more) to return the search results. It seems to me as this issue was introduced with the version 10.9.x I never had so much trouble with searching back when I was using 10.8.x. Also, my library is indeed a larger one. But that was also the case before I upgraded to v10.9.x
Author
Owner

@alanman87 commented on GitHub (Jul 9, 2024):

I do face the same/a similar issue: The search is super laggy and sometimes returns no results at all or takes up to a minute (or more) to return the search results. It seems to me as this issue was introduced with the version 10.9.x I never had so much trouble with searching back when I was using 10.8.x. Also, my library is indeed a larger one. But that was also the case before I upgraded to v10.9.x

This has been my and my shared users' exact experience. Search is extremely slow at best and non functional at times.

@alanman87 commented on GitHub (Jul 9, 2024): > I do face the same/a similar issue: The search is super laggy and sometimes returns no results at all or takes up to a minute (or more) to return the search results. It seems to me as this issue was introduced with the version 10.9.x I never had so much trouble with searching back when I was using 10.8.x. Also, my library is indeed a larger one. But that was also the case before I upgraded to v10.9.x This has been my and my shared users' exact experience. Search is extremely slow at best and non functional at times.
Author
Owner

@felix920506 commented on GitHub (Jul 10, 2024):

What storage device do you have the database on?

@felix920506 commented on GitHub (Jul 10, 2024): What storage device do you have the database on?
Author
Owner

@Glynax commented on GitHub (Jul 10, 2024):

What storage device do you have the database on?

a 2TB Hynix platinum NVMe.

@Glynax commented on GitHub (Jul 10, 2024): > What storage device do you have the database on? a 2TB Hynix platinum NVMe.
Author
Owner

@v3DJG6GL commented on GitHub (Jul 10, 2024):

What storage device do you have the database on?

4x Samsung PM9A3 960GB U.2 SSD (580000 IOPS read / 70000 IOPS write) on a RAIDZ2 array.

@v3DJG6GL commented on GitHub (Jul 10, 2024): > What storage device do you have the database on? 4x Samsung PM9A3 960GB U.2 SSD (580000 IOPS read / 70000 IOPS write) on a RAIDZ2 array.
Author
Owner

@Glynax commented on GitHub (Aug 2, 2024):

I just wanted to add another data point. I've started jellyfin completely from scratch new database new install and everything in docker. on 10.9.8 and everything was perfect for a week or two with search and things working. Now search is deteriorating already just like before only faster. Paranormal Activity spins forever in a search remote in chrome and local on jellyfin desktop app and opera. But for example searching smiling friends works after a minute or so of it looking. Can't tell why some searches work and others just don't anymore.

@Glynax commented on GitHub (Aug 2, 2024): I just wanted to add another data point. I've started jellyfin completely from scratch new database new install and everything in docker. on 10.9.8 and everything was perfect for a week or two with search and things working. Now search is deteriorating already just like before only faster. Paranormal Activity spins forever in a search remote in chrome and local on jellyfin desktop app and opera. But for example searching smiling friends works after a minute or so of it looking. Can't tell why some searches work and others just don't anymore.
Author
Owner

@jellyfin-bot commented on GitHub (Dec 1, 2024):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Dec 1, 2024): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
Author
Owner

@Glynax commented on GitHub (Dec 1, 2024):

I don't have any new logs as this issue was so back breaking I had to go back to plex. But I do want to add if it were to be fixed I'd spin jellyfin back up.

@Glynax commented on GitHub (Dec 1, 2024): I don't have any new logs as this issue was so back breaking I had to go back to plex. But I do want to add if it were to be fixed I'd spin jellyfin back up.
Author
Owner

@jellyfin-bot commented on GitHub (Apr 1, 2025):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Apr 1, 2025): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
Author
Owner

@jellyfin-bot commented on GitHub (Apr 23, 2025):

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Apr 23, 2025): This issue was closed due to inactivity.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#6000