github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

Issue: Google OAuth - after confirming the account redirected to the auth page #6049

New Issue
Closed
opened 2025-11-11 16:43:20 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 16:43:20 -06:00
Owner
Copy Link

Originally created by @dmytropoltorak on GitHub (Aug 12, 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.22

Ollama Version (if applicable)

v0.11.4

Operating System

Ubuntu 22.04.5 LTS

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

After user verification, I need to log in to the chat

Actual Behavior

I'm facing a problem using Google OAuth. After user verification, I am redirected to the authentication page

ENVs in docker-compose file:

Google SSO

  - ENABLE_GOOGLE_OAUTH=true
  - GOOGLE_CLIENT_ID=id
  - GOOGLE_CLIENT_SECRET=secret
  - GOOGLE_REDIRECT_URI=https://site/oauth/google/callback

In logs I don't find any errors about auth or something like that

Would you be able to help me find a solution?

Steps to Reproduce

  1. Open auth page
  2. Choose continue with Google
  3. Chose my user
  4. Press Continue
  5. Redirect to auth page

Logs & Screenshots

2025-08-12 05:36:08.434 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 172.19.0.1:0 - "GET /auth/callback/google?state=some_stage&code=4come_code&scope=email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+openid&authuser=1&hd=site.com&prompt=consent HTTP/1.1" 200

Additional Information

I'm using nginx for proxying to open-webui
Use this headers:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_redirect off;

proxy_cookie_path / "/; Secure; HttpOnly; SameSite=None";
Originally created by @dmytropoltorak on GitHub (Aug 12, 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.22 ### Ollama Version (if applicable) v0.11.4 ### Operating System Ubuntu 22.04.5 LTS ### 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 After user verification, I need to log in to the chat ### Actual Behavior I'm facing a problem using Google OAuth. After user verification, I am redirected to the authentication page ENVs in docker-compose file: # Google SSO - ENABLE_GOOGLE_OAUTH=true - GOOGLE_CLIENT_ID=id - GOOGLE_CLIENT_SECRET=secret - GOOGLE_REDIRECT_URI=https://site/oauth/google/callback In logs I don't find any errors about auth or something like that Would you be able to help me find a solution? ### Steps to Reproduce 1) Open auth page 2) Choose continue with Google 3) Chose my user 4) Press Continue 5) Redirect to auth page ### Logs & Screenshots 2025-08-12 05:36:08.434 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 172.19.0.1:0 - "GET /auth/callback/google?state=some_stage&code=4come_code&scope=email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+openid&authuser=1&hd=site.com&prompt=consent HTTP/1.1" 200 ### Additional Information I'm using nginx for proxying to open-webui Use this headers: proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; proxy_cookie_path / "/; Secure; HttpOnly; SameSite=None";
GiteaMirror added the bug label 2025-11-11 16:43:20 -06:00
GiteaMirror commented 2025-11-11 16:43:21 -06:00
Author
Owner
Copy Link

@dmytropoltorak commented on GitHub (Aug 12, 2025):

Its my mistake.
I removed this string from my nginx config file:
proxy_cookie_path / "/; Secure; HttpOnly; SameSite=None";

@dmytropoltorak commented on GitHub (Aug 12, 2025): Its my mistake. I removed this string from my nginx config file: `proxy_cookie_path / "/; Secure; HttpOnly; SameSite=None";`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#6049
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?