[BUG]: Unable to get "Live web search and browsing" agent working using google custom search engine. Error: getaddrinfo ENOTFOUND - http errno: -3008 about anything-llm HOT 7 CLOSED

Note:

When setting up Google Custom Search I generated API under the following section (not sure if this is correct but didn't see another way to generate API):

Programmatic Access

Custom Search JSON API
Limit of 10,000 queries per day.

from anything-llm.

Note:

I was running AnythingLLM as "standard user" when I submitted this issue. But have since confirmed same error if I run AnythingLLMDesktop.exe from "admin" terminal.

from anything-llm.

Do you have another device you could try testing this on using the same API keys? Also when you ask it to scrape/tell you key features, does the agent chat show a message similar to @agent: Searching on Google for "useanything.com key features"?

It sounds like it may be your firewall blocking the google search endpoints. I have tried to replicate this using an invalid search engine ID and API key and cannot get the same error, so I don't think your keys are wrong.

from anything-llm.

I'm yet to try on another device.

However, what I have done since is the following:

1) Uninstalled from my user account (using the supplied exe and then deleting directories) and installed using my admin account.

2) Before enabling the "Live web search and browsing" agent I ran the following chat

@agent Can you scrape useanything.com and tell me the key features

Result: Same error

Text from Chat window (not cmd terminal)

Agent @agent invoked.
Swapping over to agent chat. Type /exit to exit agent execution loop early.
Could not respond to message.
fetch failed

Call stack:

[AgentHandler] Attached websocket plugin to Agent cluster
[AgentHandler] Attached chat-history plugin to Agent cluster
[AgentHandler] Attaching user and default agent to Agent cluster.
[AgentHandler] Attached rag-memory plugin to Agent cluster
[AgentHandler] Attached document-summarizer plugin to Agent cluster
[AgentHandler] Attached web-scraping plugin to Agent cluster
fetch failed TypeError: fetch failed

at async AIbitat.reply (C:\Users\xxx\AppData\Local\Programs\anythingllm-desktop\resources\backend\server.js:22526:25)
at async AIbitat.chat (C:\Users\xxx\AppData\Local\Programs\anythingllm-desktop\resources\backend\server.js:22377:19) {
cause: Error: getaddrinfo ENOTFOUND http
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'http'
}

3) Enabled the "Live web search and browsing" agent and ran the following chat

@agent Can you scrape useanything.com and tell me the key features

Result: Same (similar) error

but included
...
[AgentHandler] Attached web-scraping plugin to Agent cluster
[AgentHandler] Attached web-browsing plugin to Agent cluster

4) Signed up to Serper copied over API key and I got the exact same error.

5) Tried all of the above while having my Windows Firewall disabled and I got the exact same error.

from anything-llm.

@tugzii and to confirm you can send a chat - just a normal chat without @agent to the workspace with no issue? This error is coming from ollama not being able to connect to the Ollama instance you are using for chatting. If it is broken in agents it should also be broken in regular chatting as well.

There is a slight difference with ollama in regular chat vs agent chat (fetch api vs Ollama SDK), but the connection information provided should be all the same.

from anything-llm.

I'm new to Ollama and AnythingLLM but yes, chat seems to be connecting to my local instance of Ollama to answer me.

As mentioned in initial post, I did have to build the Ollama code using the following instructions and run it manually from the cmd prompt (i.e. not as a service and I never downloaded and installed the original Ollama using their installer)

ollama/ollama#3107 (comment)

See attach screenshots to confirm

from anything-llm.

I officially installed Ollama (for windows) and copied my compiled files to the official install location (instead of running from c:\Documents\Ollama):

C:\Users[username]\AppData\Local\Programs\Ollama

The errors above went away and I did get a response.

However, the response was not good as even thou it stated that it had scraped the website it gave me data from 2022.

Closing this bug report for now as the above issue no longer appears (but may raise a separate issue for the old scrape data)

from anything-llm.