Originally created by @lowlyocean on GitHub (Apr 1, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.6.0
Ollama Version (if applicable)
No response
Operating System
Docker on Linux
Browser (if applicable)
Chrome
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have listed steps to reproduce the bug in detail.
Expected Behavior
Should be able to connect to a non-secure tool server
Actual Behavior
Browser prevents connecting to an HTTP tool server, if the Open-WebUI instance is itself accessed via secure HTTPS
Steps to Reproduce
Serve tool server over insecure HTTP on local network
Serve Open-WebUI over secure HTTPS
Try to connect to the tool server and notice the browser console complains about "mixed content"
Logs & Screenshots
N/A
Additional Information
I suspect the connection to the tool server would need to be handled server-side... otherwise the user needs to do one of these:
Enable mixed-content within their browser (not secure)
Expose the tool server over https (requires reverse proxy and SSL certs)
Stop accessing OWUI over HTTPS (not secure)
Originally created by @lowlyocean on GitHub (Apr 1, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.0
### Ollama Version (if applicable)
_No response_
### Operating System
Docker on Linux
### Browser (if applicable)
Chrome
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have listed steps to reproduce the bug in detail.
### Expected Behavior
Should be able to connect to a non-secure tool server
### Actual Behavior
Browser prevents connecting to an HTTP tool server, if the Open-WebUI instance is itself accessed via secure HTTPS
### Steps to Reproduce
Serve tool server over insecure HTTP on local network
Serve Open-WebUI over secure HTTPS
Try to connect to the tool server and notice the browser console complains about "mixed content"
### Logs & Screenshots
N/A
### Additional Information
I suspect the connection to the tool server would need to be handled server-side... otherwise the user needs to do one of these:
1) Enable mixed-content within their browser (not secure)
2) Expose the tool server over https (requires reverse proxy and SSL certs)
3) Stop accessing OWUI over HTTPS (not secure)
GiteaMirror
added the bug label 2025-11-11 15:59:52 -06:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @lowlyocean on GitHub (Apr 1, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.0
Ollama Version (if applicable)
No response
Operating System
Docker on Linux
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
Should be able to connect to a non-secure tool server
Actual Behavior
Browser prevents connecting to an HTTP tool server, if the Open-WebUI instance is itself accessed via secure HTTPS
Steps to Reproduce
Serve tool server over insecure HTTP on local network
Serve Open-WebUI over secure HTTPS
Try to connect to the tool server and notice the browser console complains about "mixed content"
Logs & Screenshots
N/A
Additional Information
I suspect the connection to the tool server would need to be handled server-side... otherwise the user needs to do one of these:
@tjbck commented on GitHub (Apr 1, 2025):
https://docs.openwebui.com/openapi-servers/faq#-q-why-isnt-my-local-openapi-tool-server-accessible-from-the-webui-interface