Sudden error in web-search and title generation

[kunzaatko]

When I use web-search, suddenly there is an error.

This didn't happen earlier. Also there is the same issue with the automatic naming of the chat. The chat does not get named. The error at the stderr is for the title:

[00:19:33.880] ERROR (4007917): Service Unavailable
    err: {
      "type": "Error",
      "message": "Service Unavailable",
      "stack":
          Error: Service Unavailable
              at streamingRequest (file:///home/kunzaatko/.local/lib/chat-ui/node_modules/@huggingface/inference/dist/index.js:331:15)
              at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
              at async streamingRequest (file:///home/kunzaatko/.local/lib/chat-ui/node_modules/@huggingface/inference/dist/index.js:319:12)
              at async Module.textGenerationStream (file:///home/kunzaatko/.local/lib/chat-ui/node_modules/@huggingface/inference/dist/index.js:715:3)
              at async Module.generateFromDefaultEndpoint (/home/kunzaatko/.local/lib/chat-ui/src/lib/server/generateFromDefaultEndpoint.ts:12:20)
              at async generateTitle (/home/kunzaatko/.local/lib/chat-ui/src/lib/server/textGeneration/title.ts:53:10)
              at async Module.generateTitleForConversation (/home/kunzaatko/.local/lib/chat-ui/src/lib/server/textGeneration/title.ts:16:19)
    }                                                                                                                                                                                                            [

and for the web-search only:

[12:48:50.655] ERROR (4007917): Service Unavailable

Everything worked before and I am not aware of any changes I made since then. I use searxng locally hosted for the web-search with SEARXNG_QUERY_URL="http://localhost:8080/search?q=<query>", but the same thing happens when I run with a public instance as SEARXNG_QUERY_URL="https://paulgo.io/search?q=<query>" and even if I use local search USE_LOCAL_WEBSEARCH=true. It happens both when I run in docker and when I run it myself from the command-line with

npm run dev -- --open

Where could the problem be? Is anyone else experiencing this issue?

[kunzaatko]

For anyone who encounters this, I figured that the error was in the local searxng instance did not accept the specification of the json format therefore it returned html hence the parsing failed. You can research how to setup the searxng local instance to allow the json format here.