adding webSearch to librechat.yaml causes 'unrecognized key(s)' error

[iiainb]

I'm on my fourth day of trying to resolve this and have reached the point of asking for help in the knowledge I've probably done something stupid to cause the problem.

My librechat.yaml file works and gives me all the azure openai models I've included in it. If i add the webSearch information (even just a straight c&p from the documenation) I get an 'unrecognized keys' error in the logs and nothing in the yaml loads. If I add web_search as a capability under agents I get "Invalid enum value". Commenting webSearch out in both these spots allows the file to be implemented as expected.

Things I've tried that didn't help:

1. adjusting the order of the blocks in the yaml file
2. changing the config version on the yaml file
3. updating the librechat version on my docker build to the latest version
4. indenting webSearch under endpoints (this was an AI suggestion that I resisted until I was out of ideas, it just gives the unrecognized key(s) error for the new path)
5. minimal inclusion with just the serper api key
6. updated ENDPOINTS env var to azureOpenAI,agents
7. burning incense during deployment

Clearly I'm missing something basic, but I can't put my finger on it. Attaching my yaml in txt format librechatfile.txt

[danny-avila]

Hi @iiainb

First off, if you're trying to use web search, make sure you update (assuming docker):

Updating Instructions (docker):
https://www.librechat.ai/docs/local/docker#update-librechat

You can remove the webSearch config from the librechat.yaml entirely if you're also trying to use it. You can start with just environment variables:

# Search Provider
SERPER_API_KEY=your_serper_api_key
 
# Scraper
FIRECRAWL_API_KEY=your_firecrawl_api_key
 
# Reranker (only one of these)
JINA_API_KEY=your_jina_api_key
# or
COHERE_API_KEY=your_cohere_api_key

https://www.librechat.ai/docs/features/web_search

[danny-avila]

Also feel free to share relevant logs when you try again:

Log locations:

• Docker: Project root directory ./logs
• npm (non-docker): ./api/logs

There are two types of logs that can help diagnose the issue:

• debug logs (debug-YYYY-MM-DD.log)
• error logs (error-YYYY-MM-DD.log)

Error logs contain exact stack traces and are especially helpful, but both can provide valuable information.

Please only include the relevant portions of logs that correspond to when you reproduced the error.

[iiainb]

Thanks Danny,

Yes, docker pushing to an azure container app.

I've tried these steps but there's no indication the web search functionality is implemented and chat responses suggest no real time access (also the ui indicator is absent).

I followed the update instructions and I also only started working on this at the weekend, so I don't think it's likely to be due to dated code.

[iiainb]

Also feel free to share relevant logs when you try again:

Log locations:

• Docker: Project root directory ./logs
• npm (non-docker): ./api/logs

There are two types of logs that can help diagnose the issue:

• debug logs (debug-YYYY-MM-DD.log)
• error logs (error-YYYY-MM-DD.log)

Error logs contain exact stack traces and are especially helpful, but both can provide valuable information.

Please only include the relevant portions of logs that correspond to when you reproduced the error.

I'm not sure I see a reference to the issue in the docker logs. These are the container app log entries:
{"TimeStamp": "2025-05-29T01:59:02.1857559+00:00", "Log": "F \u001b[31m{\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857751+00:00", "Log": "F \u001b[31m "issues": [\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857774+00:00", "Log": "F \u001b[31m {\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857791+00:00", "Log": "F \u001b[31m "code": "unrecognized_keys",\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857808+00:00", "Log": "F \u001b[31m "keys": [\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857824+00:00", "Log": "F \u001b[31m "webSearch"\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.185784+00:00", "Log": "F \u001b[31m ],\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857857+00:00", "Log": "F \u001b[31m "path": [],\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857874+00:00", "Log": "F \u001b[31m "message": "Unrecognized key(s) in object: 'webSearch'"\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857891+00:00", "Log": "F \u001b[31m }\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857906+00:00", "Log": "F \u001b[31m ],\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857922+00:00", "Log": "F \u001b[31m "name": "ZodError"\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1857938+00:00", "Log": "F \u001b[31m}\u001b[39m"}
{"TimeStamp": "2025-05-29T01:59:02.1867389+00:00", "Log": "F 2025-05-29 01:59:02 \u001b[33m\u001b[3mwarn\u001b[23m\u001b[39m: \u001b[33m\u001b[3mRAG API is either not running or not reachable at undefined, you may experience errors with file uploads.\u001b[23m\u001b[39m"}

Error log from the time the app restarted just shows:

{"errorLabelSet":{},"level":"error","message":"There was an uncaught error: connect ECONNREFUSED 172.18.0.4:27017","reason":{"commonWireVersion":0,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"logicalSessionTimeoutMinutes":null,"maxElectionId":null,"maxSetVersion":null,"servers":{"mongodb:27017":{"$clusterTime":null,"address":"mongodb:27017","arbiters":[],"electionId":null,"error":{"beforeHandshake":false,"errorLabelSet":{}},"hosts":[],"iscryptd":false,"lastUpdateTime":154940668,"lastWriteDate":0,"logicalSessionTimeoutMinutes":null,"maxBsonObjectSize":null,"maxMessageSizeBytes":null,"maxWireVersion":0,"maxWriteBatchSize":null,"me":null,"minRoundTripTime":0,"minWireVersion":0,"passives":[],"primary":null,"roundTripTime":-1,"setName":null,"setVersion":null,"tags":{},"topologyVersion":null,"type":"Unknown"}},"setName":null,"stale":false,"type":"Unknown"},"stack":"MongooseServerSelectionError: connect ECONNREFUSED 172.18.0.4:27017\n at _handleConnectionErrors (/app/api/node_modules/mongoose/lib/connection.js:1165:11)\n at NativeConnection.openUri (/app/api/node_modules/mongoose/lib/connection.js:1096:11)\n at async connectDb (/app/api/lib/db/connectDb.js:41:17)\n at async startServer (/app/api/server/index.js:38:3)"}
{"level":"error","message":"An error occurred while fixing Token indexes: Operation tokens.indexes() buffering timed out after 10000ms","stack":"MongooseError: Operation tokens.indexes() buffering timed out after 10000ms\n at Timeout. (/app/api/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:187:23)\n at listOnTimeout (node:internal/timers:581:17)\n at process.processTimers (node:internal/timers:519:7)"}
{"errorLabelSet":{},"level":"error","message":"There was an uncaught error: connect ECONNREFUSED 172.18.0.4:27017","reason":{"commonWireVersion":0,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"logicalSessionTimeoutMinutes":null,"maxElectionId":null,"maxSetVersion":null,"servers":{"mongodb:27017":{"$clusterTime":null,"address":"mongodb:27017","arbiters":[],"electionId":null,"error":{"beforeHandshake":false,"errorLabelSet":{}},"hosts":[],"iscryptd":false,"lastUpdateTime":154974083,"lastWriteDate":0,"logicalSessionTimeoutMinutes":null,"maxBsonObjectSize":null,"maxMessageSizeBytes":null,"maxWireVersion":0,"maxWriteBatchSize":null,"me":null,"minRoundTripTime":0,"minWireVersion":0,"passives":[],"primary":null,"roundTripTime":-1,"setName":null,"setVersion":null,"tags":{},"topologyVersion":null,"type":"Unknown"}},"setName":null,"stale":false,"type":"Unknown"},"stack":"MongooseServerSelectionError: connect ECONNREFUSED 172.18.0.4:27017\n at _handleConnectionErrors (/app/api/node_modules/mongoose/lib/connection.js:1165:11)\n at NativeConnection.openUri (/app/api/node_modules/mongoose/lib/connection.js:1096:11)\n at async connectDb (/app/api/lib/db/connectDb.js:41:17)\n at async startServer (/app/api/server/index.js:38:3)"}

[iiainb]

I've found a solution to this. My local npm version was behind and my deploy script was skipping over it. Thanks for the suggestions.

[LucasAFournier]

I am getting an "unrecognized key(s) in object: 'webSearch'" error when I start librechat using docker compose while trying to set up web search. I can't figure out how to fix it in my case (using a docker image). I have already checked I used the latest librechat version.