issue: Google oauth redirect does not work #4562

Closed
opened 2025-11-11 15:56:49 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @frenzybiscuit on GitHub (Mar 25, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

0.5.20

Ollama Version (if applicable)

none

Operating System

Debian 12

Browser (if applicable)

MacOS FIrefox

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 listed steps to reproduce the bug in detail.

Expected Behavior

Works as expected

Actual Behavior

When trying to log into google I get a access blocked: this apps request is invalid error 400: redirect_uri_mismatch

When I click on "i am a developer" it shows the redirect is trying to use http:// and not https:// which I believe is the root cause of the issue.

I've triple checked and I haven't put plain http:// anywhere in the variables, making me believe this is related to an internal code issue.

Steps to Reproduce

.

Logs & Screenshots

.

Additional Information

.

Originally created by @frenzybiscuit on GitHub (Mar 25, 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 Pip Install ### Open WebUI Version 0.5.20 ### Ollama Version (if applicable) none ### Operating System Debian 12 ### Browser (if applicable) MacOS FIrefox ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior Works as expected ### Actual Behavior When trying to log into google I get a access blocked: this apps request is invalid error 400: redirect_uri_mismatch When I click on "i am a developer" it shows the redirect is trying to use http:// and not https:// which I believe is the root cause of the issue. I've triple checked and I haven't put plain http:// anywhere in the variables, making me believe this is related to an internal code issue. ### Steps to Reproduce . ### Logs & Screenshots . ### Additional Information .
GiteaMirror added the bug label 2025-11-11 15:56:49 -06:00
Author
Owner

@Zyfax commented on GitHub (Mar 25, 2025):

Have you configured Authorized redirect URIs in your google account?
Based on the message, you have not.

@Zyfax commented on GitHub (Mar 25, 2025): Have you configured `Authorized redirect URIs` in your google account? Based on the message, you have not.
Author
Owner

@frenzybiscuit commented on GitHub (Mar 25, 2025):

Hi,

Yes.

Error 400: redirect_uri_mismatch

Image
Image

@frenzybiscuit commented on GitHub (Mar 25, 2025): Hi, Yes. ```Error 400: redirect_uri_mismatch``` ![Image](https://github.com/user-attachments/assets/92b83664-f638-4898-a0b1-7832877b08ba) ![Image](https://github.com/user-attachments/assets/119dff8a-0fbf-48da-87c1-43e09f50ef50)
Author
Owner

@frenzybiscuit commented on GitHub (Mar 25, 2025):

I guess I could try setting the authorized_redirect_uri to http:// instead of https:// but that seems insecure to me..

@frenzybiscuit commented on GitHub (Mar 25, 2025): I guess I could try setting the authorized_redirect_uri to http:// instead of https:// but that seems insecure to me..
Author
Owner

@Zyfax commented on GitHub (Mar 26, 2025):

Could it be the reverse proxy is not setting request header to https?

@Zyfax commented on GitHub (Mar 26, 2025): Could it be the reverse proxy is not setting request header to https?
Author
Owner

@frenzybiscuit commented on GitHub (Mar 26, 2025):

Could it be the reverse proxy is not setting request header to https?

Perhaps? There is a nginx reverse proxy, but its only the web server. There is no other proxy in front of open-webui.

Also, github works.

@frenzybiscuit commented on GitHub (Mar 26, 2025): > Could it be the reverse proxy is not setting request header to https? Perhaps? There is a nginx reverse proxy, but its only the web server. There is no other proxy in front of open-webui. Also, github works.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4562