Jellyfin Forum
JellySearch - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Development (https://forum.jellyfin.org/f-development)
+--- Forum: Plugin Development (https://forum.jellyfin.org/f-plugin-development)
+--- Thread: JellySearch (/t-jellysearch)

Pages: 1 2 3 4 5 6

RE: JellySearch - keklol - 2024-12-05

(2024-11-17, 11:08 AM)Druidblack Wrote:
(2024-10-15, 04:48 PM)need4swede Wrote: Would love to try this, but I am running Jellyfin on bare metal (Windows).

Anyone know of a way to get this working?

https://github.com/arnesacnussem/jellyfin-plugin-meilisearch

That's a great alternative, thanks for sharing!

RE: JellySearch - kandykarter - 2024-12-11

(2024-12-05, 03:49 AM)keklol Wrote:
(2024-11-17, 11:08 AM)Druidblack Wrote:
(2024-10-15, 04:48 PM)need4swede Wrote: Would love to try this, but I am running Jellyfin on bare metal (Windows).

Anyone know of a way to get this working?

https://github.com/arnesacnussem/jellyfin-plugin-meilisearch

That's a great alternative, thanks for sharing!

Yeah this is fantastic. I DO use a reverse proxy but it's an uncommon one and I never got Jellysearch working properly. This plugin worked right away with minimal fiddling. Thanks!

RE: JellySearch - twilco - 2025-01-08

(2024-08-20, 05:54 PM)Topomov Wrote: My setup runs on a Synology which reverse proxy (nginx) as far as I know does not allow to easily add routing rules in a docker compose. It's most likely my fault; I failed to fully get it working on my setup.

I also use Synology DSM reverse proxy and I setup Jellysearch today. Since you can't make the necessary changes to the ngnix configuration via the limited GUI, you need to ssh into the NAS to make the changes manually. 

Using this syno forum post as inspiration, you should:
  1. Make a reverse proxy for Jellyfin using the DSM GUI (in Control Panel -> Login Portal -> Advanced -> Reverse Proxy)
  2. Connect over SSH and open the file at "/etc/nginx/sites-enabled/server.ReverseProxy.conf" and find the "server" block that corresponds to the Jellyfin reverse proxy you configured in step 1. 
  3. Copy the entire contents of the "server" block to a text editor and apply the changes described in the Jellysearch description (it's just adding the "if ($arg_searchTerm)" block at the beginning of the "location" block)
  4. Using the Synology DSM GUI, remove the reverse proxy you configured in step 1, as it will conflict with the manual one we're about to create
  5. Copy the modified "server" block you copied in step 2 to a new file inside "/etc/nginx/sites-enabled/" (I named my file the hostname of the previously configured reverse proxy, e.g. "jellyfin.myaccount.synology.me", but you can use any filename you wish). You'll need to use vi to do this, so "sudo vi /etc/nginx/sites-enabled/your.file.name", then press "i" to enter insertion mode, then you can paste the file contents, then press escape to exit insertion mode, then enter ":wq" and hit enter to save and close the file.
  6. Once you've created the manual nginx server configuration in step 5, we want to make sure the resulting nginx configuration is valid. Run "sudo nginx -t" to test the configuration. If it passes, then you can reload ngnix to apply the change using "sudo nginx -s reload"
  7. That's it!

A note regarding the modification of the "server" block. You'll be adding this bit at the beginning of the "location" block:

Code:
    if ($arg_searchTerm) {
        proxy_pass http://jellysearch:5000;
        break;
    }

Make sure that the url specified here matches the address of the host machine on which you're running Jellysearch, and that the port matches the host port that's mapped to port 5000 in the container.

Hope that helps! Jellysearch is lightning fast compared to built-in search, and far more functional and flexible. Having gone through this process, I think it was totally worth it.

Edit: I've also setup the Meilisearch plugin, which is great because it's simpler, requires no tinkering with reverse proxy, works with all clients (I assume), and works over LAN unlike Jellysearch. Comparing the two, Jellysearch seems to respond much faster, so I think I'll keep both implemented, such that the plug-in is used over LAN and Jellysearch over WAN.

RE: JellySearch - JellyHunter - 2025-01-08

I wonder when/if this will even be a official alternative for Jellyfin?

RE: JellySearch - thymon - 2025-01-13

Hello,

I'm here to find a bit of help because everything seems to be properly implemented, yet it's not working.

Jellysearch shows no errors in the logs:

Code:
warn: Microsoft.AspNetCore.Hosting.Diagnostics[15]
      Overriding HTTP_PORTS '8080' and HTTPS_PORTS ''. Binding to values defined by URLS instead 'http://0.0.0.0:5000'.
info: JellySearch.Jobs.IndexJob[0]
      Indexing items...
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://0.0.0.0:5000
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /app
info: JellySearch.Jobs.IndexJob[0]
      Indexed 233886 items, it might take a few moments for Meilisearch to finish indexing


And Meilisearch is receiving requests from Jellysearch as expected :

Code:
2025-01-13T15:00:00.252755Z  INFO HTTP request{method=PUT host="192.168.10.100:7700" route=/indexes/items/settings/sortable-attributes query_parameters= user_agent=Meilisearch .NET (v0.15.0) status_code=202}: meilisearch: close time.busy=127µs time.idle=2.86ms
2025-01-13T15:00:00.259024Z  INFO HTTP request{method=PUT host="192.168.10.100:7700" route=/indexes/items/settings/searchable-attributes query_parameters= user_agent=Meilisearch .NET (v0.15.0) status_code=202}: meilisearch: close time.busy=144µs time.idle=5.49ms
2025-01-13T15:00:00.265120Z  INFO HTTP request{method=PUT host="192.168.10.100:7700" route=/indexes/items/settings/displayed-attributes query_parameters= user_agent=Meilisearch .NET (v0.15.0) status_code=202}: meilisearch: close time.busy=88.1µs time.idle=5.31ms
2025-01-13T15:00:00.266777Z  INFO index_scheduler: A batch of tasks was successfully completed with 1 successful tasks and 0 failed tasks.
2025-01-13T15:00:00.274445Z  INFO HTTP request{method=PUT host="192.168.10.100:7700" route=/indexes/items/settings/ranking-rules query_parameters= user_agent=Meilisearch .NET (v0.15.0) status_code=202}: meilisearch: close time.busy=118µs time.idle=8.60ms
2025-01-13T15:00:00.289329Z  INFO index_scheduler: A batch of tasks was successfully completed with 3 successful tasks and 0 failed tasks.
2025-01-13T15:00:00.309443Z  INFO index_scheduler: A batch of tasks was successfully completed with 1 successful tasks and 0 failed tasks.


I've modified my NPM configuration (Yes I use port 9096 Grinning-face )

[Image: image.png]

However, it's not working — the search in Jellyfin doesn't return any results.
I have to undo the NPM modification to restore Jellyfin's search functionality.
As a result, I can't take advantage of Jellysearch.

Do you have any idea where the issue might be coming from?

RE: JellySearch - thymon - 2025-01-24

I still haven’t been able to get JellySearch working.

Everything seems to be OK, but it’s probably an issue with the reverse proxy. I’m stuck.

Could anyone help me out?
Thanks in advance Smiling-face

RE: JellySearch - domi - 2025-01-29

(2025-01-24, 08:34 AM)thymon Wrote: I still haven’t been able to get JellySearch working.

Everything seems to be OK, but it’s probably an issue with the reverse proxy. I’m stuck.

Could anyone help me out?
Thanks in advance Smiling-face


Can you post the logs of JellySearch after you did a few searches?

RE: JellySearch - nothingveryobvious - 2025-01-30

Is this still working for people?

https://github.com/arnesacnussem/jellyfin-plugin-meilisearch

I got it running on 10.10.5 but my search speeds were even slower.

RE: JellySearch - kandykarter - 2025-01-31

Yeah I have the same issue. I couldn't get Jellysearch working with my weird reverse proxy, so I installed the plugin. The search results are BETTER, but just as slow as the standard search is.

I really hope search in general is helped by the EFCore refactoring they're doing, because it's abysmal in its current state.

RE: JellySearch - souvik29766 - 2025-04-01

(2024-08-16, 11:12 AM)keklol Wrote: [Image: icon.svg]

A fast full-text search proxy for Jellyfin

https://gitlab.com/DomiStyle/jellysearch

(I am not the author but this seems very interesting)

I have installed Jellyfin server on my windows 11 PC, the search option in Jellyfin is extremely slow, please tell me how to install Jelly search without docker.