The user gets as message to refresh the web-page. Or get redirected to the login page.
Actual Behavior:
Once you log in with SSO, If your session is open for a while until you need to authorize again or after restart of open-webui. The WebSocket session does not recognize that authorization has expired and tries to continue using the current WebSocket session. All WebSocket requests get rejected internally until you refresh and re-authenticate.
The user does not get any notification or get redirected when trying to use the chat, instead, the chat hangs waiting for a response. And the chat-history does the same. The open-webui logs shows message of rejected websockets connections.
Description
Bug Summary:
WebSockets session does not understand that a user needs to re-authenticate.
Reproduction Details
Steps to Reproduce:
1- Login using SSO
2- Wait until the session times out or restart the open-webui backend/server
3- Do not refresh the webpage, try to use the chat
Originally created by @compemperor on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8805
# Bug Report
## Installation Method
Docker container with HAproxy as a reverse proxy.
## Environment
- **Open WebUI Version: v0.5.4**
- **Operating System: Ubuntu 24.04**
- **Browser : Microsoft Edge.**
## Expected Behavior:
The user gets as message to refresh the web-page. Or get redirected to the login page.
## Actual Behavior:
Once you log in with SSO, If your session is open for a while until you need to authorize again or after restart of open-webui. The WebSocket session does not recognize that authorization has expired and tries to continue using the current WebSocket session. All WebSocket requests get rejected internally until you refresh and re-authenticate.
The user does not get any notification or get redirected when trying to use the chat, instead, the chat hangs waiting for a response. And the chat-history does the same. The open-webui logs shows message of rejected websockets connections.
## Description
**Bug Summary:**
WebSockets session does not understand that a user needs to re-authenticate.
## Reproduction Details
**Steps to Reproduce:**
1- Login using SSO
2- Wait until the session times out or restart the open-webui backend/server
3- Do not refresh the webpage, try to use the chat
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 @compemperor on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8805
Bug Report
Installation Method
Docker container with HAproxy as a reverse proxy.
Environment
Open WebUI Version: v0.5.4
Operating System: Ubuntu 24.04
Browser : Microsoft Edge.
Expected Behavior:
The user gets as message to refresh the web-page. Or get redirected to the login page.
Actual Behavior:
Once you log in with SSO, If your session is open for a while until you need to authorize again or after restart of open-webui. The WebSocket session does not recognize that authorization has expired and tries to continue using the current WebSocket session. All WebSocket requests get rejected internally until you refresh and re-authenticate.
The user does not get any notification or get redirected when trying to use the chat, instead, the chat hangs waiting for a response. And the chat-history does the same. The open-webui logs shows message of rejected websockets connections.
Description
Bug Summary:
WebSockets session does not understand that a user needs to re-authenticate.
Reproduction Details
Steps to Reproduce:
1- Login using SSO
2- Wait until the session times out or restart the open-webui backend/server
3- Do not refresh the webpage, try to use the chat