I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Pip Install
Open WebUI Version
0.6.43
Ollama Version (if applicable)
No response
Operating System
ubuntu 22.04
Browser (if applicable)
No response
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 provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
INFO level is doing Info only.
If you enable logging on multi user system, the logs are flooded with URL requests/access logs.
Expected is to be able to have all relevant INFO and ERROR and above in the main webui.log and the requests/accesses INFO and DEBUG into a access.log (similar as with nginx or apache)
Independent which source it is, the ERRORS and above shall appear in the webui.log!
Actual Behavior
you can either disable access logs totally or keep them in the main log. No option to separate.
it would be perfect to provide a sample how to configure it
or even better to add a flag --access-log-file to separate the access logs into a own file
Originally created by @dpalic on GitHub (Jan 2, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20324
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Pip Install
### Open WebUI Version
0.6.43
### Ollama Version (if applicable)
_No response_
### Operating System
ubuntu 22.04
### Browser (if applicable)
_No response_
### 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 **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
INFO level is doing Info only.
If you enable logging on multi user system, the logs are flooded with URL requests/access logs.
Expected is to be able to have all **relevant** INFO and ERROR and above in the main webui.log and the requests/accesses INFO and DEBUG into a access.log (similar as with nginx or apache)
Independent which source it is, the ERRORS and above shall appear in the webui.log!
### Actual Behavior
you can either disable access logs totally or keep them in the main log. No option to separate.
```
2026-01-02 09:26:21.838 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /_app/immutable/nodes/7.wd9KRmTJ.js HTTP/1.1" 304
2026-01-02 09:26:21.838 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /_app/immutable/chunks/ZpR27Sr8.js HTTP/1.1" 304
2026-01-02 09:26:21.839 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /_app/immutable/nodes/36.DeH_9tDl.js HTTP/1.1" 304
2026-01-02 09:26:21.843 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /_app/immutable/chunks/BZ4vDKbQ.js HTTP/1.1" 304
2026-01-02 09:26:21.843 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /_app/immutable/chunks/Nos9qo-N.js HTTP/1.1" 304
2026-01-02 09:26:21.844 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /_app/immutable/chunks/Dwiv2xQV.js HTTP/1.1" 304
2026-01-02 09:26:21.845 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /_app/immutable/chunks/9HvU6daC.js HTTP/1.1" 304
2026-01-02 09:26:22.523 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/config HTTP/1.1" 200
2026-01-02 09:26:22.738 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/auths/ HTTP/1.1" 200
2026-01-02 09:26:22.783 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/config HTTP/1.1" 200
2026-01-02 09:26:22.785 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/users/user/settings HTTP/1.1" 200
2026-01-02 09:26:22.914 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/users/0934cb82-c12a-49af-9df3-11d6b8406b51/profile/image HTTP/1.1" 200
2026-01-02 09:26:22.965 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/configs/banners HTTP/1.1" 200
2026-01-02 09:26:22.973 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:282 - No requirements found in frontmatter.
2026-01-02 09:26:22.975 | INFO | open_webui.utils.plugin:load_tool_module_by_id:102 - Loaded module: tool_essentials
2026-01-02 09:26:22.977 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/users/user/settings HTTP/1.1" 200
2026-01-02 09:26:22.978 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/tools/ HTTP/1.1" 200
2026-01-02 09:26:23.046 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/folders/ HTTP/1.1" 200
2026-01-02 09:26:23.047 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/chats/all/tags HTTP/1.1" 200
2026-01-02 09:26:23.049 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/version HTTP/1.1" 200
2026-01-02 09:26:23.066 | INFO | open_webui.routers.openai:get_all_models:474 - get_all_models()
2026-01-02 09:26:23.066 | INFO | open_webui.routers.ollama:get_all_models:328 - get_all_models()
2026-01-02 09:26:23.133 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/chats/pinned HTTP/1.1" 200
2026-01-02 09:26:23.177 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/chats/?page=1 HTTP/1.1" 200
2026-01-02 09:26:33.172 | ERROR | open_webui.routers.ollama:send_get_request:99 - Connection error:
2026-01-02 09:26:44.172 | ERROR | open_webui.routers.ollama:send_get_request:99 - Connection error:
2026-01-02 09:26:44.239 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/models HTTP/1.1" 200
2026-01-02 09:26:44.341 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/models/model?id=bader-location HTTP/1.1" 200
2026-01-02 09:26:44.368 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/version/updates HTTP/1.1" 200
2026-01-02 09:26:44.377 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/tools/ HTTP/1.1" 200
2026-01-02 09:26:44.411 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/functions/ HTTP/1.1" 200
2026-01-02 09:26:44.591 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/knowledge/search/files?page=1 HTTP/1.1" 200
2026-01-02 09:26:44.591 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/knowledge/search HTTP/1.1" 200
2026-01-02 09:26:44.592 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/notes/search?query= HTTP/1.1" 200
2026-01-02 09:26:44.653 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/knowledge/search/files?page=1 HTTP/1.1" 200
2026-01-02 09:26:44.654 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/knowledge/search HTTP/1.1" 200
2026-01-02 09:26:44.661 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 1.2.3.4:0 - "GET /api/v1/notes/search?query= HTTP/1.1" 200
```
### Steps to Reproduce
LOG_LEVEL=DEBUG /home/me/.pyenv/versions/3.11.10/bin/open-webui serve
### Logs & Screenshots
see above
### Additional Information
it would be perfect to provide a sample how to configure it
or even better to add a flag --access-log-file to separate the access logs into a own file
GiteaMirror
added the bug label 2026-05-05 21:41:32 -05:00
If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
If you found a solution in any of these issues, please share it here to help others
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
<!-- gh-comment-id:3704887061 -->
@owui-terminator[bot] commented on GitHub (Jan 2, 2026):
🔍 **Similar Issues Found**
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
1. [#20155](https://github.com/open-webui/open-webui/issues/20155) **issue:**
*by dhaern • Dec 24, 2025 • `bug`*
2. [#20107](https://github.com/open-webui/open-webui/issues/20107) **issue:**
*by mengdeer589 • Dec 22, 2025 • `bug`*
3. [#20196](https://github.com/open-webui/open-webui/issues/20196) **issue:**
*by dhaern • Dec 27, 2025 • `bug`*
4. [#19877](https://github.com/open-webui/open-webui/issues/19877) **issue:**
*by dotmobo • Dec 11, 2025 • `bug`*
5. [#20019](https://github.com/open-webui/open-webui/issues/20019) **issue:**
*by j63440490 • Dec 17, 2025 • `bug`*
<details>
<summary>Show 5 more related issues</summary>
6. [#19777](https://github.com/open-webui/open-webui/issues/19777) **issue:**
*by Yaute7 • Dec 05, 2025 • `bug`*
7. [#19861](https://github.com/open-webui/open-webui/issues/19861) **issue:**
*by QuitHub • Dec 10, 2025 • `bug`*
8. [#20092](https://github.com/open-webui/open-webui/issues/20092) **issue:**
*by VideoRyan • Dec 22, 2025 • `bug`*
9. [#19864](https://github.com/open-webui/open-webui/issues/19864) **issue:**
*by Haervwe • Dec 10, 2025 • `bug`*
10. [#19563](https://github.com/open-webui/open-webui/issues/19563) **issue:**
*by naruto7g • Nov 28, 2025 • `bug`*
</details>
---
💡 **Tips:**
- If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
- If you found a solution in any of these issues, please share it here to help others
*This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
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 @dpalic on GitHub (Jan 2, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20324
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
0.6.43
Ollama Version (if applicable)
No response
Operating System
ubuntu 22.04
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
INFO level is doing Info only.
If you enable logging on multi user system, the logs are flooded with URL requests/access logs.
Expected is to be able to have all relevant INFO and ERROR and above in the main webui.log and the requests/accesses INFO and DEBUG into a access.log (similar as with nginx or apache)
Independent which source it is, the ERRORS and above shall appear in the webui.log!
Actual Behavior
you can either disable access logs totally or keep them in the main log. No option to separate.
Steps to Reproduce
LOG_LEVEL=DEBUG /home/me/.pyenv/versions/3.11.10/bin/open-webui serve
Logs & Screenshots
see above
Additional Information
it would be perfect to provide a sample how to configure it
or even better to add a flag --access-log-file to separate the access logs into a own file
@owui-terminator[bot] commented on GitHub (Jan 2, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#20155 issue:
by dhaern • Dec 24, 2025 •
bug#20107 issue:
by mengdeer589 • Dec 22, 2025 •
bug#20196 issue:
by dhaern • Dec 27, 2025 •
bug#19877 issue:
by dotmobo • Dec 11, 2025 •
bug#20019 issue:
by j63440490 • Dec 17, 2025 •
bugShow 5 more related issues
#19777 issue:
by Yaute7 • Dec 05, 2025 •
bug#19861 issue:
by QuitHub • Dec 10, 2025 •
bug#20092 issue:
by VideoRyan • Dec 22, 2025 •
bug#19864 issue:
by Haervwe • Dec 10, 2025 •
bug#19563 issue:
by naruto7g • Nov 28, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.