I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
:latest
Ollama Version (if applicable)
:latest
Operating System
Arch BTW
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.
Originally created by @xx1182 on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17257
### 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
:latest
### Ollama Version (if applicable)
:latest
### Operating System
Arch BTW
### 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
For Caddy
Myexemple.com {
handle_path /uiai/* {
reverse_proxy :3000
}
### Actual Behavior
It doesn't work
### Steps to Reproduce
Docker compose up -d
### Logs & Screenshots
Logs
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-25 08:54:34 -05:00
Not supported and Not planned. PLEASE look for existing issues/discussions before creating one.
<!-- gh-comment-id:3263739707 -->
@tjbck commented on GitHub (Sep 7, 2025):
Not supported and Not planned. PLEASE look for existing issues/discussions before creating one.
Why is this not supported? It's quite a common use case and shouldn't be hard to implement. Would love to have support for OpenWebUI being served under a subpath.
<!-- gh-comment-id:3508824596 -->
@muety commented on GitHub (Nov 9, 2025):
Why is this not supported? It's quite a common use case and shouldn't be hard to implement. Would love to have support for OpenWebUI being served under a subpath.
I would also like to have support for this. I will happily open a PR if maintainers are on board with the idea
<!-- gh-comment-id:4156458702 -->
@JAEarly commented on GitHub (Mar 30, 2026):
I would also like to have support for this. I will happily open a PR if maintainers are on board with the idea
@s-nt-s there is an existing discussion. Comment there. It is HARD to implement, in fact, extremely hard and requires a lot of testing. CC @muety
<!-- gh-comment-id:4222761569 -->
@Classic298 commented on GitHub (Apr 10, 2026):
@s-nt-s there is an existing discussion. Comment there. It is HARD to implement, in fact, extremely hard and requires a lot of testing. CC @muety
@s-nt-s there is an existing discussion. Comment there. It is HARD to implement, in fact, extremely hard and requires a lot of testing. CC @muety
The community needs this feature, and the community’s developers can work to implement it;
Arbitrarily rejecting the community’s proposal based on estimates of the workload is not a good choice.
<!-- gh-comment-id:4485284084 -->
@fkajerry commented on GitHub (May 19, 2026):
> [@s-nt-s](https://github.com/s-nt-s) there is an existing discussion. Comment there. It is HARD to implement, in fact, extremely hard and requires a lot of testing. CC [@muety](https://github.com/muety)
**The community needs this feature**, and the community’s developers can work to implement it;
Arbitrarily rejecting the community’s proposal based on estimates of the workload is not a good choice.
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 @xx1182 on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17257
Check Existing Issues
Installation Method
Docker
Open WebUI Version
:latest
Ollama Version (if applicable)
:latest
Operating System
Arch BTW
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
For Caddy
Myexemple.com {
handle_path /uiai/* {
reverse_proxy :3000
}
Actual Behavior
It doesn't work
Steps to Reproduce
Docker compose up -d
Logs & Screenshots
Logs
Additional Information
No response
@tjbck commented on GitHub (Sep 7, 2025):
Not supported and Not planned. PLEASE look for existing issues/discussions before creating one.
@muety commented on GitHub (Nov 9, 2025):
Why is this not supported? It's quite a common use case and shouldn't be hard to implement. Would love to have support for OpenWebUI being served under a subpath.
@JAEarly commented on GitHub (Mar 30, 2026):
I would also like to have support for this. I will happily open a PR if maintainers are on board with the idea
@s-nt-s commented on GitHub (Apr 10, 2026):
Why is this not supported????? It is a essential functionality
@Classic298 commented on GitHub (Apr 10, 2026):
@s-nt-s there is an existing discussion. Comment there. It is HARD to implement, in fact, extremely hard and requires a lot of testing. CC @muety
@fkajerry commented on GitHub (May 19, 2026):
The community needs this feature, and the community’s developers can work to implement it;
Arbitrarily rejecting the community’s proposal based on estimates of the workload is not a good choice.