Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5095] [BUG]: Underdocumented base url @ custom llm endpoint dialog + [FEAT] "Test API access" button #4912

New Issue
Closed
opened 2026-06-05 14:50:49 -04:00 by yindo · 6 comments
yindo commented 2026-06-05 14:50:49 -04:00
Owner
Copy Link
Copy Source

Originally created by @tattwamasii2p on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5095

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

Somehow the 404 error occurs, see the screenshots below.

A log file with stack traces & with trace_log_level would be helpful for debugging such errors.

Image Image

Are there known steps to reproduce?

No response

Originally created by @tattwamasii2p on GitHub (Mar 1, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5095 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? Somehow the 404 error occurs, see the screenshots below. A log file with stack traces & with trace_log_level would be helpful for debugging such errors. <img width="784" height="280" alt="Image" src="https://github.com/user-attachments/assets/395c2376-e758-4934-be1f-41e950107f17" /> <img width="1135" height="473" alt="Image" src="https://github.com/user-attachments/assets/8e843a94-d50a-4403-978d-55f932943a09" /> ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-06-05 14:50:49 -04:00
yindo closed this issue 2026-06-05 14:50:49 -04:00
yindo commented 2026-06-05 14:50:49 -04:00
Author
Owner
Copy Link
Copy Source

@tattwamasii2p commented on GitHub (Mar 1, 2026):

https://github.com/Mintplex-Labs/anything-llm/blob/1eae02e60fec5f7f9f245ea71c8f4385b1544f2e/frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/PromptReply/index.jsx#L52

<!-- gh-comment-id:3980349473 --> @tattwamasii2p commented on GitHub (Mar 1, 2026): https://github.com/Mintplex-Labs/anything-llm/blob/1eae02e60fec5f7f9f245ea71c8f4385b1544f2e/frontend/src/components/WorkspaceChat/ChatContainer/ChatHistory/PromptReply/index.jsx#L52
yindo commented 2026-06-05 14:50:49 -04:00
Author
Owner
Copy Link
Copy Source

@tattwamasii2p commented on GitHub (Mar 1, 2026):

The correct base_url is https://integrate.api.nvidia.com/v1 , you should document this in the UI for custom OpenAI-compatible LLM credentials dialog, or (less preferably) in the documentation for this dialog

<!-- gh-comment-id:3980378471 --> @tattwamasii2p commented on GitHub (Mar 1, 2026): The correct base_url is https://integrate.api.nvidia.com/v1 , you should document this in the UI for custom OpenAI-compatible LLM credentials dialog, or (less preferably) in the documentation for this dialog
yindo commented 2026-06-05 14:50:50 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 2, 2026):

For the generic provider it is up to the user to know/understand the correct base URL, since /v1 is not ubiquitous for every single endpoint - some are /openai/v1.

Having a rule or documentation around that in our docs would only confuse people more. The correct base URL should come from the documentation of the provider you are using via that connector

<!-- gh-comment-id:3985182884 --> @timothycarambat commented on GitHub (Mar 2, 2026): For the generic provider it is up to the user to know/understand the correct base URL, since `/v1` is *not* ubiquitous for every single endpoint - some are <baseurl>/openai/v1. Having a rule or documentation around that in our docs would only confuse people more. The correct base URL should come from the documentation of the provider you are using via that connector
yindo commented 2026-06-05 14:50:50 -04:00
Author
Owner
Copy Link
Copy Source

@tattwamasii2p commented on GitHub (Mar 2, 2026):

"base url" in the context of AnythingLLM is a concept that had been defined by AnythingLLM folks, and not a standard term. This is an invention of your team, and not a worldwide standard. You can make it clear what do you mean under it. If you cannot, then your communication skill is weak, and you can invite skilled tech writers who can explain it.

And you can provide users with a "Test API access" button to quickly check whether all is right.

<!-- gh-comment-id:3985218773 --> @tattwamasii2p commented on GitHub (Mar 2, 2026): "base url" in the context of AnythingLLM is a concept that had been defined by AnythingLLM folks, and not a standard term. This is an invention of your team, and not a worldwide standard. You can make it clear what do you mean under it. If you cannot, then your communication skill is weak, and you can invite skilled tech writers who *can* explain it. And you can provide users with a "Test API access" button to quickly check whether all is right.
yindo commented 2026-06-05 14:50:50 -04:00
Author
Owner
Copy Link
Copy Source

@tattwamasii2p commented on GitHub (Mar 2, 2026):

For example, you can provide a sample base url in the UI label right below the baseURL inputfield --- a label with the text value which ends with /v1, e.g. https://api.example.org/v1 --- this would make things much clearer

<!-- gh-comment-id:3985243462 --> @tattwamasii2p commented on GitHub (Mar 2, 2026): For example, you can provide a sample base url in the UI label right below the baseURL inputfield --- a label with the text value which ends with `/v1`, e.g. `https://api.example.org/v1` --- this would make things much clearer
yindo commented 2026-06-05 14:50:50 -04:00
Author
Owner
Copy Link
Copy Source

@tattwamasii2p commented on GitHub (Mar 2, 2026):

When the value of baseURL inputfield is non-empty and changed, you can reassign the label with "${baseURL_inputfield_value}/chat/completions" --- the user will match the label with his API provider docs and will directly see what's wrong with his input into baseURL inputfield value

And when the value of baseURL inputfield is changed back to empty, reassign the label to the literal "https://api.example.org/v1"

<!-- gh-comment-id:3985295954 --> @tattwamasii2p commented on GitHub (Mar 2, 2026): When the value of baseURL inputfield is non-empty and changed, you can reassign the label with `"${baseURL_inputfield_value}/chat/completions"` --- the user will match the label with his API provider docs and will directly see what's wrong with his input into baseURL inputfield value And when the value of baseURL inputfield is changed back to empty, reassign the label to the literal `"https://api.example.org/v1"`
yindo changed title from [GH-ISSUE #5095] [BUG]: Underdocumented base url @ custom llm endpoint dialog + [FEAT] "Test API access" button to [GH-ISSUE #5095] [BUG]: Underdocumented base url @ custom llm endpoint dialog + [FEAT] "Test API access" button 2026-06-07 16:32:40 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
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: Mintplex-Labs/anything-llm#4912
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?