langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Dify does not work with SearXNG version 0.0.3 #186

New Issue
Closed
opened 2026-02-16 10:18:22 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 10:18:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @JasonBeiJing on GitHub (Apr 9, 2025).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The Dify Tool Marketplace has released a new version 0.0.3 of SearXNG. After installing this version, authorization fails with the following error message:
{
"code": "invalid_param",
"message": "PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"Error 400: {"error": "Invalid value \"all\" for parameter time_range"}"}",
"status": 400
}
The same URL works fine in SearXNG version 0.0.2.

please check， thank

✔️ Expected Behavior

same url, it should work in version 0.0.3

❌ Actual Behavior

error occured

Originally created by @JasonBeiJing on GitHub (Apr 9, 2025). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The Dify Tool Marketplace has released a new version 0.0.3 of SearXNG. After installing this version, authorization fails with the following error message: { "code": "invalid_param", "message": "PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"Error 400: {\"error\": \"Invalid value \\\"all\\\" for parameter time_range\"}"}", "status": 400 } The same URL works fine in SearXNG version 0.0.2. please check， thank ### ✔️ Expected Behavior same url, it should work in version 0.0.3 ### ❌ Actual Behavior error occured
yindo closed this issue 2026-02-16 10:18:22 -05:00
yindo commented 2026-02-16 10:18:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 9, 2025):

你好 @JasonBeiJing！我是一个可以帮助你解决bug、回答问题并成为贡献者的机器人。很高兴为你提供帮助，同时等待人类维护者的回复。

The error you're encountering indicates that the time_range parameter is not being accepted in SearXNG version 0.0.3, whereas it worked in version 0.0.2. This suggests that there might have been changes in the way time_range is handled or validated in the new version of SearXNG.

To address this issue, you can:

  1. Check the SearXNG Documentation: Look for any changes in the documentation of SearXNG version 0.0.3 that might explain the new expected format or valid values for the time_range parameter.

  2. Review the Dify Integration: Ensure that the Dify integration with SearXNG is updated to accommodate any changes in the parameter requirements. This might involve modifying how the time_range parameter is set or validated within Dify.

  3. Validate Parameter Values: Verify that the value being passed to time_range is valid according to the new version's requirements. If "all" is no longer a valid value, you may need to adjust it to a supported value.

If these steps do not resolve the issue, further investigation into the specific changes in SearXNG version 0.0.3 might be necessary to understand how to adapt the integration.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 9, 2025): <!-- Greeting --> 你好 @JasonBeiJing！我是一个可以帮助你解决bug、回答问题并成为贡献者的机器人。很高兴为你提供帮助，同时等待人类维护者的回复。 <!-- Answer --> The error you're encountering indicates that the `time_range` parameter is not being accepted in SearXNG version 0.0.3, whereas it worked in version 0.0.2. This suggests that there might have been changes in the way `time_range` is handled or validated in the new version of SearXNG. To address this issue, you can: 1. **Check the SearXNG Documentation**: Look for any changes in the documentation of SearXNG version 0.0.3 that might explain the new expected format or valid values for the `time_range` parameter. 2. **Review the Dify Integration**: Ensure that the Dify integration with SearXNG is updated to accommodate any changes in the parameter requirements. This might involve modifying how the `time_range` parameter is set or validated within Dify. 3. **Validate Parameter Values**: Verify that the value being passed to `time_range` is valid according to the new version's requirements. If "all" is no longer a valid value, you may need to adjust it to a supported value. If these steps do not resolve the issue, further investigation into the specific changes in SearXNG version 0.0.3 might be necessary to understand how to adapt the integration. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4bbc98f5-09fc-4ae7-9a39-78b598345a15?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4bbc98f5-09fc-4ae7-9a39-78b598345a15?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4bbc98f5-09fc-4ae7-9a39-78b598345a15?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4bbc98f5-09fc-4ae7-9a39-78b598345a15?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4bbc98f5-09fc-4ae7-9a39-78b598345a15?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4bbc98f5-09fc-4ae7-9a39-78b598345a15?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4bbc98f5-09fc-4ae7-9a39-78b598345a15?feedback_type=other)</sup>
yindo commented 2026-02-16 10:18:23 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 9, 2025):

From the api documentation, this can be resolved by selecting a value. https://docs.searxng.org/dev/search_api.html.

Can you take a look at this @AGIMaster

@crazywoola commented on GitHub (Apr 9, 2025): From the api documentation, this can be resolved by selecting a value. https://docs.searxng.org/dev/search_api.html. Can you take a look at this @AGIMaster
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#186
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?