[BUG]: searngx 403 forbidden error (malformed URL) #2194

Closed
opened 2026-02-28 05:58:53 -05:00 by deekerman · 1 comment
Owner

Originally created by @pspierce on GitHub (Mar 1, 2025).

How are you running AnythingLLM?

Docker (local)

What happened?

Running searxng locally via Docker. This was previously working; however, I am now seeing a 403 response from the CoT. This URL shown below is incorrect for searxng. It appears to me that "/search" is not being added.

Alright, the user tried to search using SearxNG again but got a 403 Forbidden error. The URL they used was “http://searxng:8080/?q=qbism&format=json”.

Image

If I exec a shell into the docker image and curl the proper URL, it is fine.

`anythingllm@7325f92d5080:$ curl --location --verbose --head --insecure http://searxng:8080/search?q=AnythingLLM%2520Searngx&format=json
[1] 1014
anythingllm@7325f92d5080:~$ * Trying 172.23.0.3:8080...

  • Connected to searxng (172.23.0.3) port 8080 (#0)

HEAD /search?q=AnythingLLM%2520Searngx HTTP/1.1
Host: searxng:8080
User-Agent: curl/7.81.0
Accept: /

  • Mark bundle as not supporting multiuse
    < HTTP/1.1 200 OK
    HTTP/1.1 200 OK
    < Content-Type: text/html; charset=utf-8
    Content-Type: text/html; charset=utf-8
    < Content-Length: 61269
    Content-Length: 61269
    < Server-Timing: total;dur=707.16, render;dur=3.693, total_0_wikipedia;dur=108.724, total_1_google;dur=507.633, total_2_wikidata;dur=570.83, total_3_duckduckgo;dur=701.018, load_0_wikipedia;dur=107.03, load_1_google;dur=495.176, load_2_wikidata;dur=567.532, load_3_duckduckgo;dur=694.545
    Server-Timing: total;dur=707.16, render;dur=3.693, total_0_wikipedia;dur=108.724, total_1_google;dur=507.633, total_2_wikidata;dur=570.83, total_3_duckduckgo;dur=701.018, load_0_wikipedia;dur=107.03, load_1_google;dur=495.176, load_2_wikidata;dur=567.532, load_3_duckduckgo;dur=694.545
    < X-Content-Type-Options: nosniff
    X-Content-Type-Options: nosniff
    < X-Download-Options: noopen
    X-Download-Options: noopen
    < X-Robots-Tag: noindex, nofollow
    X-Robots-Tag: noindex, nofollow
    < Referrer-Policy: no-referrer
    Referrer-Policy: no-referrer
    < Connection: close
    Connection: close
    `

How can I know the true URL that is being used on the backend? Could the response URL shown in CoT be a hallucination?

Are there known steps to reproduce?

No response

Originally created by @pspierce on GitHub (Mar 1, 2025). ### How are you running AnythingLLM? Docker (local) ### What happened? Running searxng locally via Docker. This was previously working; however, I am now seeing a 403 response from the CoT. This URL shown below is incorrect for searxng. It appears to me that "/search" is not being added. `Alright, the user tried to search using SearxNG again but got a 403 Forbidden error. The URL they used was “http://searxng:8080/?q=qbism&format=json”.` ![Image](https://github.com/user-attachments/assets/2856c4a6-a636-4887-a658-fb590c79f051) If I exec a shell into the docker image and curl the proper URL, it is fine. `anythingllm@7325f92d5080:$ curl --location --verbose --head --insecure http://searxng:8080/search?q=AnythingLLM%2520Searngx&format=json [1] 1014 anythingllm@7325f92d5080:~$ * Trying 172.23.0.3:8080... * Connected to searxng (172.23.0.3) port 8080 (#0) > HEAD /search?q=AnythingLLM%2520Searngx HTTP/1.1 > Host: searxng:8080 > User-Agent: curl/7.81.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 200 OK HTTP/1.1 200 OK < Content-Type: text/html; charset=utf-8 Content-Type: text/html; charset=utf-8 < Content-Length: 61269 Content-Length: 61269 < Server-Timing: total;dur=707.16, render;dur=3.693, total_0_wikipedia;dur=108.724, total_1_google;dur=507.633, total_2_wikidata;dur=570.83, total_3_duckduckgo;dur=701.018, load_0_wikipedia;dur=107.03, load_1_google;dur=495.176, load_2_wikidata;dur=567.532, load_3_duckduckgo;dur=694.545 Server-Timing: total;dur=707.16, render;dur=3.693, total_0_wikipedia;dur=108.724, total_1_google;dur=507.633, total_2_wikidata;dur=570.83, total_3_duckduckgo;dur=701.018, load_0_wikipedia;dur=107.03, load_1_google;dur=495.176, load_2_wikidata;dur=567.532, load_3_duckduckgo;dur=694.545 < X-Content-Type-Options: nosniff X-Content-Type-Options: nosniff < X-Download-Options: noopen X-Download-Options: noopen < X-Robots-Tag: noindex, nofollow X-Robots-Tag: noindex, nofollow < Referrer-Policy: no-referrer Referrer-Policy: no-referrer < Connection: close Connection: close ` How can I know the true URL that is being used on the backend? Could the response URL shown in CoT be a hallucination? ### Are there known steps to reproduce? _No response_
deekerman 2026-02-28 05:58:53 -05:00
Author
Owner

@pspierce commented on GitHub (Mar 1, 2025):

Close. Somehow, my settings were overwritten and - json was no longer an allowed format.

@pspierce commented on GitHub (Mar 1, 2025): Close. Somehow, my settings were overwritten and - json was no longer an allowed format.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anything-llm#2194
No description provided.