Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Bad request errror at the SearxngSearch Tool #2815

Closed
seonghobae opened this issue Jul 17, 2024 · 4 comments
Closed

[BUG] Bad request errror at the SearxngSearch Tool #2815

seonghobae opened this issue Jul 17, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@seonghobae
Copy link

Describe the bug
A clear and concise description of what the bug is.
SearxngSearch Tool shows Bad request error even I set tool properly.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Searxng tool
  2. Link with worker
  3. Run with Query
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.
Working without bad requests error.

Screenshots
If applicable, add screenshots to help explain your problem.
image
image

Flow
For security reason, I can't export this.

Setup

  • Installation: Docker
  • Flowise Version: 81918d5e3ccd
  • OS: Linux
  • Browser: Safari, Edge

Additional context
Add any other context about the problem here.
Searxng always works correctly.

@genwch
Copy link

genwch commented Jul 18, 2024

same here. attached error captured from langsmith
same issue on version 1.8.4 & 1.8.3

`BAD REQUEST

Error: BAD REQUEST
at SearxngSearch._call (/usr/local/lib/node_modules/flowise/node_modules/@langchain/community/dist/tools/searxng_search.cjs:120:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async SearxngSearch.call (/usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/tools.cjs:78:22)
at async /usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/src/agents.js:315:39
at async Promise.all (index 0)
at async AgentExecutor._call (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/src/agents.js:302:30)
at async AgentExecutor.invoke (/usr/local/lib/node_modules/flowise/node_modules/langchain/dist/chains/base.cjs:58:28)
at async ConversationalAgent_Agents.run (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/agents/ConversationalAgent/ConversationalAgent.js:119:19)
at async utilBuildChatflow (/usr/local/lib/node_modules/flowise/dist/utils/buildChatflow.js:258:15)
at async createInternalPrediction (/usr/local/lib/node_modules/flowise/dist/controllers/internal-predictions/index.js:7:29) `

@HenryHengZJ HenryHengZJ added the bug Something isn't working label Jul 22, 2024
@VoxBG
Copy link

VoxBG commented Aug 12, 2024

I also received BAD REQUEST from searxng until I set Language, Page No. and Safe Search in Additional Parameters in SearXNG in flowise UI.
image

@kstan79
Copy link

kstan79 commented Aug 25, 2024

how you guys make it working, it seems not fire at my side
image

@HenryHengZJ
Copy link
Contributor

Fixed in this PR: #3263

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants