github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #2441] null is not an object (evaluating 'l.userContext.join') when using system prompt with external API (OpenAI, Groq etc) #51548

New Issue
Closed
opened 2026-05-05 12:36:21 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-05 12:36:21 -05:00
Owner
Copy Link

Originally created by @JamesBedwell on GitHub (May 21, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/2441

Bug Report

Description

Bug Summary:
When using a system prompt in combination with an external API such as OpenAI or Groq, the following error appears:

Uh-oh! There was an issue connecting to llama3-70b-8192.
null is not an object (evaluating 'l.userContext.join')

Steps to Reproduce:
Set up an external API endpoint such as OpenAI or Groq, set a system prompt in Settings > General, and send any message to a model on the external API (tested on Groq's llama-3-70b-8192 and OpenAI's gpt4 and gpt4o).

Expected Behavior:
Get a response from the AI which considers the system prompt

Actual Behavior:
Error message appears:

Uh-oh! There was an issue connecting to llama3-70b-8192.
null is not an object (evaluating 'l.userContext.join')

Environment

  • Open WebUI Version: v0.1.125

  • Ollama (if applicable): N/A

  • Operating System: macOS Sonoma and iOS 17

  • Browser (if applicable): Safari on macOS and iOS

Reproduction Details

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:
[Include relevant Docker container logs, if applicable]

Screenshots (if applicable):
Screenshot 2024-05-21 at 4 02 35 PM

Installation Method

Docker

Additional Information

[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]

Note

If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Originally created by @JamesBedwell on GitHub (May 21, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/2441 # Bug Report ## Description **Bug Summary:** When using a system prompt in combination with an external API such as OpenAI or Groq, the following error appears: ``` Uh-oh! There was an issue connecting to llama3-70b-8192. null is not an object (evaluating 'l.userContext.join') ``` **Steps to Reproduce:** Set up an external API endpoint such as OpenAI or Groq, set a system prompt in Settings > General, and send any message to a model on the external API (tested on Groq's llama-3-70b-8192 and OpenAI's gpt4 and gpt4o). **Expected Behavior:** Get a response from the AI which considers the system prompt **Actual Behavior:** Error message appears: ``` Uh-oh! There was an issue connecting to llama3-70b-8192. null is not an object (evaluating 'l.userContext.join') ``` ## Environment - **Open WebUI Version:** v0.1.125 - **Ollama (if applicable):** N/A - **Operating System:** macOS Sonoma and iOS 17 - **Browser (if applicable):** Safari on macOS and iOS ## Reproduction Details **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. - [ ] I have included the browser console logs. - [ ] I have included the Docker container logs. ## Logs and Screenshots **Browser Console Logs:** [Include relevant browser console logs, if applicable] **Docker Container Logs:** [Include relevant Docker container logs, if applicable] **Screenshots (if applicable):** <img width="631" alt="Screenshot 2024-05-21 at 4 02 35 PM" src="https://github.com/open-webui/open-webui/assets/6438738/0d461a95-8ab8-4c07-adc8-f849df1aa79b"> ## Installation Method Docker ## Additional Information [Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.] ## Note If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
GiteaMirror commented 2026-05-05 12:36:23 -05:00
Author
Owner
Copy Link

@justinh-rahb commented on GitHub (May 21, 2024):

As usual with any new release, we often do some fixes afterwards that push direct to main and build new Docker images. If you haven't already done so as of 3hrs ago please try re-pulling again.

<!-- gh-comment-id:2121821614 --> @justinh-rahb commented on GitHub (May 21, 2024): As usual with any new release, we often do some fixes afterwards that push direct to `main` and build new Docker images. If you haven't already done so as of 3hrs ago please try re-pulling again.
GiteaMirror commented 2026-05-05 12:36:25 -05:00
Author
Owner
Copy Link

@JamesBedwell commented on GitHub (May 21, 2024):

Running watchtowerrr to update the docker image fixed it, thanks so much!On 21 May 2024, at 4:10 PM, Justin Hayes @.***> wrote:
As usual with any new release, we often do some fixes afterwards that push direct to main and build new Docker images. If you haven't already done so as of 3hrs ago please try re-pulling again.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

<!-- gh-comment-id:2121914995 --> @JamesBedwell commented on GitHub (May 21, 2024): Running watchtowerrr to update the docker image fixed it, thanks so much!On 21 May 2024, at 4:10 PM, Justin Hayes ***@***.***> wrote: As usual with any new release, we often do some fixes afterwards that push direct to main and build new Docker images. If you haven't already done so as of 3hrs ago please try re-pulling again. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#51548
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?