At this point, the new user's browser is not displaying anything
Originally created by @handsomezhuzhu on GitHub (Apr 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
0.6.2
### Ollama Version (if applicable)
_No response_
### Operating System
CentOS 7
### 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 listed steps to reproduce the bug in detail.
### Expected Behavior
When the administrator sets the default user role to 'to be activated', new users will be placed on the 'to be activated' page after registration
### Actual Behavior
When the administrator sets the default user role to be activated, there is no response from new users after registration
### Steps to Reproduce
1. Set the default user role as' to be activated 'and allow new users to register and create new registrations
2. Put the user in a pending activation state, but the user cannot display the pending activation page
### Logs & Screenshots
```
2025-04-12 05:25:31.898 | INFO | open_webui.models.auths:insert_new_auth:108 - insert_new_auth - {}
2025-04-12 05:25:31.920 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:14054 - "POST /api/v1/auths/signup HTTP/1.1" 200 - {}
2025-04-12 05:25:32.002 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:14054 - "GET /api/config HTTP/1.1" 200 - {}
2025-04-12 05:25:32.506 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:14054 - "GET /api/changelog HTTP/1.1" 200 - {}
2025-04-12 05:25:32.578 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:50416 - "GET /api/v1/tools/ HTTP/1.1" 401 - {}
2025-04-12 05:25:32.649 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:14054 - "GET /api/v1/tools/ HTTP/1.1" 401 - {}
2025-04-12 05:25:45.847 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:10902 - "GET / HTTP/1.1" 304 - {}
2025-04-12 05:25:46.304 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:10902 - "GET /api/config HTTP/1.1" 200 - {}
2025-04-12 05:25:46.457 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:10902 - "GET /api/v1/auths/ HTTP/1.1" 200 - {}
2025-04-12 05:25:46.514 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:10902 - "GET /api/config HTTP/1.1" 200 - {}
2025-04-12 05:25:46.566 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:10902 - "GET /api/changelog HTTP/1.1" 200 - {}
2025-04-12 05:25:46.637 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:41132 - "GET /api/v1/tools/ HTTP/1.1" 401 - {}
2025-04-12 05:25:46.747 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:41132 - "GET /api/v1/tools/ HTTP/1.1" 401 - {}
2025-04-12 05:26:03.957 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:1176 - "GET / HTTP/1.1" 304 - {}
2025-04-12 05:26:04.498 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:1176 - "GET /api/config HTTP/1.1" 200 - {}
2025-04-12 05:26:04.661 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:1176 - "GET /api/v1/auths/ HTTP/1.1" 200 - {}
2025-04-12 05:26:04.782 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:1176 - "GET /api/config HTTP/1.1" 200 - {}
2025-04-12 05:26:04.946 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:1176 - "GET /api/changelog HTTP/1.1" 200 - {}
2025-04-12 05:26:05.055 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:33962 - "GET /api/v1/tools/ HTTP/1.1" 401 - {}
2025-04-12 05:26:05.168 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 58.249.112.77:33962 - "GET /api/v1/tools/ HTTP/1.1" 401 - {}
```
### Additional Information
At this point, the new user's browser is not displaying anything
GiteaMirror
added the bug label 2025-11-11 16:03:44 -06:00
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 @handsomezhuzhu on GitHub (Apr 12, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.2
Ollama Version (if applicable)
No response
Operating System
CentOS 7
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When the administrator sets the default user role to 'to be activated', new users will be placed on the 'to be activated' page after registration
Actual Behavior
When the administrator sets the default user role to be activated, there is no response from new users after registration
Steps to Reproduce
Logs & Screenshots
Additional Information
At this point, the new user's browser is not displaying anything