Getting "Search is disabled (400 - Bad Request)" from the "explore" link
Using a slightly modified version of the docker-compose.yml file found in the repository. When starting it starts up I can see
WARN [ImmichServer] Search is disabled
so it seems like that's the cause.
But why is search disabled? What am I missing?
I can also see this error in the logs
24 Replies
Adding config here:
immich.env
base.yml
docker-compose.yml https://pastebin.com/5r94dM2X
Pastebin
version: "3.8"services: immich-server: extends: file: base...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
TYPESENSE_ENABLED=false will disable search
omg, sometimes I'm blind
It wasn't enough tho. When removing that line I also had to rename it from
immich-typesense
to just typesense
it's using just typesense
somewhere in the code and it's not configurable I guess
lol, the image recognition is really bad. But it works! Thanks for the helpIt uses typesense by default, but it is configurable
Is there any docs for how to configure it?
No, we haven't updated those yet ๐
How would change the name then?
One sec
GitHub
immich/infra.config.ts at main ยท immich-app/immich
Self-hosted photo and video backup solution directly from your mobile phone. - immich/infra.config.ts at main ยท immich-app/immich
I couldn't see it in the code either. But given that I missed the disabled ENV I'm clearly blind ๐
Lolol
cool. for some reason github wouldn't show me that line of code when seaching for just TYPESENSE
Weird
I mean, clearly it's to late on a friday for me to be doing anything like that. So I blame me for githubs problems as well
Lol, idk githubs new search seems to sometimes not work great either
Jwt secret isn't used anymore btw
Hi, I get the same error on a HP Proliant Microserver G7 N54L, using AMD Turion II Neo CPU... As long as I didn't disable typesense and machine learning, I can't run Immich.
By disabling typesense I am getting "Search is disabled..." error when doing a generic search (2019 for example). Is search linked with typesense and any metadata extracted from photos?
Is there anything I can do to in order to be able to use typesense and machine learning? How do i know that the problem is caused by the CPU?
Does a search with a
m:
prefix work?No, it makes no difference using m: prefix, I get the same error...

Ah well. Looks like we disable search when you don't run typesense. Hmm
OK. I remember now. Yes typesense is required for searching (always).
We are considering removing typesense from our stack though and using postgres directly for search in the future, but that is probably a ways off.
I see... Is there any way to bypass the CPU requirements in order to be able to run typesense and machine learning on my server?
I'm not 100% sure. You would probably have to look at the typesense documentation/github repository to see. I know that it can be compiled from source, which makes it possible to run on non-pre-build arches.
Sounds way too complicated for my skills. ๐ Anyway, thank you for your help, really appreciate it ๐