mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 06:03:26 -05:00
The problem with working on a local network #417
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#417
Reference in New Issue
Block a user
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?
Originally created by @CoderDodo2022 on GitHub (Mar 5, 2024).
Bug Report
Description
Bug Summary:
[When you try to log in from another device connected to the same local network, you receive: "Account activation is waiting for an administrator to access the WebUI. The status of your account is currently awaiting activation. To access the WebUI, please contact the administrator. Administrators can manage user statuses from the admin panel."
Steps to Reproduce:
[I have set up an Ollamа Server Windows 10 computer for the snap-in, running on a local network and accepting requests on a subsequent request: http://192.168.0.219:11434 .
On the server, I also installed a docker server, on which I created an administrator account, using this link: docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --open-webui name --always restart ghcr.io/open-webui/open-webui:main .
On another device that I want to connect to (the device connects on the same LAN), I downloaded the docker container in accordance with the instruction: docker run -d -p 3000:8080 -e OLLAMA_API_BASE_URL=http://192.168.0.219:11434 -v open-webui:/app/backend/data --name is open-webui --restart is always ghcr.io/open-webui/open-webui:main]
Expected Behavior:
[I assumed that when trying to connect from another device, we would be able to send a request to the admin console on the main server so that we could confirm registration from the administrator account and use it safely. In this case, the account itself will be displayed on the main server.]
Actual Behavior:
[But in fact, when I log in from the second device, I only get a message about an incorrect username or password (if I try to enter administrator credentials), or when I try to register, I log in, but the message is displayed in full screen: "Account Activation Pending Contact Admin for WebUI Access Your account status is currently pending activation. To access the WebUI, please reach out to the administrator. Admins can manage user statuses from the Admin Panel." At the same time, no new accounts are displayed on the main server.]
Environment
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Open webui via docker container, ollama server via .exe application ]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
@justinh-rahb commented on GitHub (Mar 5, 2024):
Thank you for your detailed bug report. It seems there's a misunderstanding regarding how open-webui instances handle user databases. Each instance operates with its own local user database, which means separate instances won't automatically share user data or account statuses.
You actually don't need to install and run separate open-webui instances on each device. Instead, users on the same LAN can connect directly to the open-webui instance running on your server.
Based on the information you provided, here’s a simplified way to achieve what you're looking for:
Setup open-webui on the Server Only: Install and run the open-webui instance only on your server machine (e.g., the Windows 10 computer where you've set up the Ollama Server). Use the following command (which you've likely already done):
Accessing from Other Devices: Instead of installing open-webui on each device, users on the same LAN can simply access the open-webui instance running on your server by navigating to
http://192.168.0.219:3000(assuming192.168.0.219is the server's IP and3000is the port you've exposed). This way, all users interact with the same backend and user database, ensuring a consistent experience and shared data access.Ensure Network Accessibility: Make sure your LAN settings and any firewalls are configured to allow traffic to and from the server on the required port (
3000in this example).This setup minimizes complexity and ensures all users on your LAN can access the same open-webui instance without needing separate installations. It also circumvents the issue you encountered with account activations not being shared across instances.
@CoderDodo2022 commented on GitHub (Mar 5, 2024):
Sorry for wasting your time, I'm new to docker and just starting to learn everything, thank you for your thorough and detailed help.
Also, I will give the launch code of the docker container with which everything worked for me, for those who find themselves in the same situation as me:
docker run -d -p 192.168.0.219:3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main@justinh-rahb commented on GitHub (Mar 5, 2024):
No waste of time at all, I commend you for following the template with a detailed description as it made forming an answer with an LLM very quick, thorough, and tailored to your scenario.