I have read and followed all the instructions provided in the README.md.
I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
Every user can sign in. First one becomes admin, all other ones become users (directly activated)
Actual Behavior:
Only first user can log in. Everyone else becomes the following error:
You do not have permission to access this resource. Please contact your administrator for assistance.
Description
Bug Summary:
I want to sign in
Reproduction Details
Steps to Reproduce:
Have two different users sign in. First one becomes admin, second one can't log in at all.
Logs and Screenshots
Browser Console Logs:
Screenshots/Screen Recordings (if applicable):
Originally created by @simonfrey on GitHub (Nov 22, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7215
# Bug Report
## Installation Method
docker-compose.yml with oauth2proxy
```yml
services:
openwebui:
image: ghcr.io/open-webui/open-webui:v0.4.2
volumes:
- ./owebvolume:/app/backend/data
environment:
- 'HOST=0.0.0.0'
- 'WEBUI_URL=https://chat.XXX.de'
- 'ENABLE_OLLAMA_API=False'
- 'OPENAI_API_KEY=sk-proj-XXX'
- 'OPENAI_API_BASE_URL=http://llm-proxy-api:8080/llm/v1'
- 'ENABLE_COMMUNITY_SHARING=False'
- 'ENABLE_SIGNUP=True'
- 'DEFAULT_USER_ROLE=user'
- 'ENABLE_OAUTH_SIGNUP=True'
- 'WEBUI_AUTH_TRUSTED_NAME_HEADER=X-Forwarded-Email'
- 'WEBUI_AUTH_TRUSTED_EMAIL_HEADER=X-Forwarded-Email'
restart: unless-stopped
oauth2proxy:
image: quay.io/oauth2-proxy/oauth2-proxy:v7.6.0
environment:
OAUTH2_PROXY_HTTP_ADDRESS: 0.0.0.0:4180
OAUTH2_PROXY_UPSTREAMS: http://openwebui:8080/
OAUTH2_PROXY_PROVIDER: google
OAUTH2_PROXY_CLIENT_ID: "XXX.apps.googleusercontent.com"
OAUTH2_PROXY_CLIENT_SECRET: "GOCSPX-YYY"
OAUTH2_PROXY_EMAIL_DOMAINS: "XXX.de"
OAUTH2_PROXY_COOKIE_SECRET: "XXX="
OAUTH2_PROXY_COOKIE_SECURE: "false"
OAUTH2_PROXY_REDIRECT_URL: "https://chat.XXX.de/oauth2/callback"
OAUTH2_PROXY_GCP_HEALTHCHECKS: "true"
OAUTH2_PROXY_SKIP_AUTH_ROUTES: "GET=^/opensearch.xml"
restart: unless-stopped
entrypoint: "/bin/oauth2-proxy --custom-templates-dir=/oauth2proxy_template"
volumes:
- ./oauth2proxy_template:/oauth2proxy_template
ports:
- 4180:4180/tcp
```
## Environment
- **Open WebUI Version:** v0.4.2
- **Operating System:** Ubuntu Linux
- **Browser (if applicable):** Firefox
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
Every user can sign in. First one becomes admin, all other ones become users (directly activated)
## Actual Behavior:
Only first user can log in. Everyone else becomes the following error:
```
You do not have permission to access this resource. Please contact your administrator for assistance.
```
## Description
**Bug Summary:**
I want to sign in
## Reproduction Details
**Steps to Reproduce:**
Have two different users sign in. First one becomes admin, second one can't log in at all.
## Logs and Screenshots
**Browser Console Logs:**

**Screenshots/Screen Recordings (if applicable):**

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 @simonfrey on GitHub (Nov 22, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7215
Bug Report
Installation Method
docker-compose.yml with oauth2proxy
Environment
Open WebUI Version: v0.4.2
Operating System: Ubuntu Linux
Browser (if applicable): Firefox
Confirmation:
Expected Behavior:
Every user can sign in. First one becomes admin, all other ones become users (directly activated)
Actual Behavior:
Only first user can log in. Everyone else becomes the following error:
Description
Bug Summary:
I want to sign in
Reproduction Details
Steps to Reproduce:
Have two different users sign in. First one becomes admin, second one can't log in at all.
Logs and Screenshots
Browser Console Logs:
Screenshots/Screen Recordings (if applicable):