mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
issue: "Please enter a prompt" error when using the ?q=... query
#5567
Reference in New Issue
Block a user
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?
Originally created by @jdeepwell on GitHub (Jun 17, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.14
Ollama Version (if applicable)
No response
Operating System
macOS 15.5 (24F74)
Browser (if applicable)
Chrome 136.0.7103.114
Confirmation
README.md.Expected Behavior
Open new OpenWebUI browser window with a URL like
https://open-webui.orb.local/?q=Hello+world&models=litellm.gpt-4.1Should start a new chat without any error messages.
Actual Behavior
Does start the new chat correctly but also gives the error message "Please enter a prompt"
Steps to Reproduce
https://open-webui.orb.local/?q=Hello+world&models=litellm.gpt-4.1Logs & Screenshots
Docker log
Browser console
Additional Information
Under the error message in the screenshot the correct prompt passed in via query is listed and the response is also fine – so everything seems to work as expected, except the error message…
@Classic298 commented on GitHub (Jun 17, 2025):
Cannot reproduce, works for me (0.6.14) No error shown, chat starts as intended
@Classic298 commented on GitHub (Jun 17, 2025):
Actually, I can reproduce now.
If you write a model Id that you do not have, then the error DOES NOT appear.
And if you write a model Id that YOU DO HAVE, then the ERROR appears.
I.e. if you have gpt4.1 and you write gpt5, you will not get an error.
If you have gpt4.1 and you write gpt4.1 as the model ID in the URL Parameter, then the error shows up. Yes.
@Classic298 commented on GitHub (Jun 17, 2025):
@jdeepwell i tried to reproduce it on 0.6.15 and can no longer reproduce it there.
Can you test on 0.6.15 please
@jdeepwell commented on GitHub (Jun 17, 2025):
@Classic298 Confirmed - does not happen anymore with 0.6.15 👍
(sorry to have bothered you, the 0.6.15 update yesterday went past me...🙏)
@Classic298 commented on GitHub (Jun 17, 2025):
Cool, thanks. Please close the issue