Originally created by @brunesIT on GitHub (Aug 22, 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.25
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22.04
Browser (if applicable)
Edge
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
I was hoping that with docker-compose I could start openwebui on a subdomain of my main domain, but when I do so, I encounter this issue... I currently want to set up a redirect with nginx proxy manager on the main domain n8n and on the other openwebui.
Actual Behavior
The assets are not loading.
Steps to Reproduce
start the server
start the docker container with openwebui
enter the subdomain and view the screen without loading
ITS MY FIRST TIME AT GITHUB SO I DON'T KNOW HOW TO USE IT IF IM I WRONG OR SOMETHING SORRY
Originally created by @brunesIT on GitHub (Aug 22, 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.25
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu 22.04
### Browser (if applicable)
Edge
### 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
I was hoping that with docker-compose I could start openwebui on a subdomain of my main domain, but when I do so, I encounter this issue... I currently want to set up a redirect with nginx proxy manager on the main domain n8n and on the other openwebui.
<img width="1890" height="606" alt="Image" src="https://github.com/user-attachments/assets/29623812-ec63-475d-a151-0644827bcea5" />
### Actual Behavior
The assets are not loading.
### Steps to Reproduce
start the server
start the docker container with openwebui
enter the subdomain and view the screen without loading
### Logs & Screenshots
### Additional Information
THE DOCKER COMPOSE YML
services:
open-webui:
image: ghcr.io/open-webui/open-webui:main
container_name: open-webui
ports:
- "8080:8080"
environment:
- OPENAI_API_KEY=sk-xxx
- OPENAI_API_BASE_URL=https://api.deepseek.com/v1
- MODEL_NAME=deepseek-chat
- DEFAULT_MODELS=deepseek-chat
- ENABLE_SIGNUP=true
- WEBUI_AUTH=true
- ENABLE_COMMUNITY_SHARING=false
- ENABLE_MODEL_FILTER=true
- PUBLIC_URL=https://domain.example.com/openwebui
- OAUTH_PROVIDER=oidc
- OAUTH_CLIENT_ID=xxxx.x.x.x.xxxx...
- OAUTH_CLIENT_SECRET=x.x.x.x.xx.x.xxx
- OAUTH_ISSUER=5c8fcb0c-x.x.x.xx.xx.xx.x
- OAUTH_REDIRECT_URI=https://domain.example.com/openwebui/oauth/callback
- OAUTH_SCOPE=openid profile email
- BASE_URL=/openwebui
volumes:
- open-webui:/app/backend/data
restart: unless-stopped
volumes:
open-webui:
ITS MY FIRST TIME AT GITHUB SO I DON'T KNOW HOW TO USE IT IF IM I WRONG OR SOMETHING SORRY
GiteaMirror
added the bug label 2025-11-11 16:47:09 -06:00
And yes, it doesn't work properly with the subdirectory, it's an intentional behavior.
Just set it as a subdomain, e.g. openwebui.example.com
@rgaricano commented on GitHub (Aug 22, 2025):
That's not a subdomain, it's a subdirectory.
And yes, it doesn't work properly with the subdirectory, it's an intentional behavior.
Just set it as a subdomain, e.g. openwebui.example.com
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 @brunesIT on GitHub (Aug 22, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.25
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22.04
Browser (if applicable)
Edge
Confirmation
README.md.Expected Behavior
I was hoping that with docker-compose I could start openwebui on a subdomain of my main domain, but when I do so, I encounter this issue... I currently want to set up a redirect with nginx proxy manager on the main domain n8n and on the other openwebui.
Actual Behavior
The assets are not loading.
Steps to Reproduce
start the server
start the docker container with openwebui
enter the subdomain and view the screen without loading
Logs & Screenshots
Additional Information
THE DOCKER COMPOSE YML
services:
open-webui:
image: ghcr.io/open-webui/open-webui:main
container_name: open-webui
ports:
- "8080:8080"
environment:
- OPENAI_API_KEY=sk-xxx
- OPENAI_API_BASE_URL=https://api.deepseek.com/v1
- MODEL_NAME=deepseek-chat
- DEFAULT_MODELS=deepseek-chat
- ENABLE_SIGNUP=true
- WEBUI_AUTH=true
- ENABLE_COMMUNITY_SHARING=false
- ENABLE_MODEL_FILTER=true
- PUBLIC_URL=https://domain.example.com/openwebui
- OAUTH_PROVIDER=oidc
- OAUTH_CLIENT_ID=xxxx.x.x.x.xxxx...
- OAUTH_CLIENT_SECRET=x.x.x.x.xx.x.xxx
- OAUTH_ISSUER=5c8fcb0c-x.x.x.xx.xx.xx.x
- OAUTH_REDIRECT_URI=https://domain.example.com/openwebui/oauth/callback
- OAUTH_SCOPE=openid profile email
- BASE_URL=/openwebui
volumes:
- open-webui:/app/backend/data
restart: unless-stopped
volumes:
open-webui:
ITS MY FIRST TIME AT GITHUB SO I DON'T KNOW HOW TO USE IT IF IM I WRONG OR SOMETHING SORRY
@brunesIT commented on GitHub (Aug 22, 2025):
the proxy configuration for openwebUI
@rgaricano commented on GitHub (Aug 22, 2025):
That's not a subdomain, it's a subdirectory.
And yes, it doesn't work properly with the subdirectory, it's an intentional behavior.
Just set it as a subdomain, e.g. openwebui.example.com
@brunesIT commented on GitHub (Aug 22, 2025):
@rgaricano So I need to buy a new domain? Im on Azure
@rgaricano commented on GitHub (Aug 22, 2025):
usually you can add subdomains as option in this kind of services, search in azure for info.