github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-22 06:02:06 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

Unable to Connect Automatic1111 to Open WebUI #2937

New Issue
Closed
opened 2025-11-11 15:17:53 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 15:17:53 -06:00
Owner
Copy Link

Originally created by @NullEqualsZero on GitHub (Dec 6, 2024).

Installation Method

Open WebUI

  • Installation Method: Docker (running inside WSL)
  • Version: WEBUI_BUILD_VERSION c4ea31357f49d08a14c86b2bd85fdcd489512e91
  • Python Version (in container): 3.11.10

Automatic1111

  • Installation Method: Local on Windows
  • Arguments Used: --listen --api

Environment

  • Ollama Version: 0.4.7 (although not relevant)
  • System Python Version (outside Docker): 3.12.3
  • Operating System:
    • Base OS/WSL : Windows 11/ WSL Ubuntu
    • Automatic1111 Host: Windows (same as above)

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior

Automatic1111 should successfully connect to Open WebUI when the URL http://127.0.0.1:7860/ is provided.

Actual Behavior

When entering the URL http://127.0.0.1:7860/ into Open WebUI, the following error is returned:

Oops! The URL you provided is invalid. Please double-check and try again.

The URL appears to be correct, so it’s unclear why this error is occurring.

Logs and Errors

Docker Logs

The output of docker logs open-webui is attached in the file open-webui-logs.txt

Browser Console Logs

Error messages from the browser console:

index.ts:73 GET http://127.0.0.1:8080/images/api/v1/config/url/verify 400 (Bad Request)

Reproduction Details

Steps to Reproduce

  1. Start Open WebUI in Docker with the following configuration:
    • Docker running inside WSL.
    • Open WebUI accessible via http://127.0.0.1:8080.
  2. Start Automatic1111 locally on Windows with the arguments --listen --api.

(The whole file )

@echo off
set PYTHON=
set GIT=
set VENV_DIR=
set COMMANDLINE_ARGS=--xformers --listen --enable-insecure-extension-access --api
call webui.bat
  1. Attempt to connect Automatic1111 to Open WebUI by providing the URL http://127.0.0.1:7860/.

Observed Behavior

The error message is displayed:

Oops! The URL you provided is invalid. Please double-check and try again.

Additional Information

  • Networking Context:
    • Docker runs inside WSL on the same machine where Automatic1111 is hosted on Windows.
    • Docker uses 127.0.0.1:8080 for Open WebUI.

If additional information or logs are required, please let me know. Thank you!

Originally created by @NullEqualsZero on GitHub (Dec 6, 2024). ## Installation Method ### Open WebUI - **Installation Method:** Docker (running inside WSL) - **Version:** `WEBUI_BUILD_VERSION c4ea31357f49d08a14c86b2bd85fdcd489512e91` - **Python Version (in container):** `3.11.10` ### Automatic1111 - **Installation Method:** Local on Windows - **Arguments Used:** `--listen --api` ## Environment - **Ollama Version:** `0.4.7` (although not relevant) - **System Python Version (outside Docker):** `3.12.3` - **Operating System:** - **Base OS/WSL :** Windows 11/ WSL Ubuntu - **Automatic1111 Host:** Windows (same as above) ## Confirmation: - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior Automatic1111 should successfully connect to Open WebUI when the URL `http://127.0.0.1:7860/` is provided. ## Actual Behavior When entering the URL `http://127.0.0.1:7860/` into Open WebUI, the following error is returned: ``` Oops! The URL you provided is invalid. Please double-check and try again. ``` The URL appears to be correct, so it’s unclear why this error is occurring. ## Logs and Errors ### Docker Logs The output of `docker logs open-webui` is attached in the file [open-webui-logs.txt](https://github.com/user-attachments/files/18040091/open-webui-logs.txt) ### Browser Console Logs Error messages from the browser console: ``` index.ts:73 GET http://127.0.0.1:8080/images/api/v1/config/url/verify 400 (Bad Request) ``` ## Reproduction Details ### Steps to Reproduce 1. Start Open WebUI in Docker with the following configuration: - Docker running inside WSL. - Open WebUI accessible via `http://127.0.0.1:8080`. 2. Start Automatic1111 locally on Windows with the arguments `--listen --api`. (The whole file ) ```bash @echo off set PYTHON= set GIT= set VENV_DIR= set COMMANDLINE_ARGS=--xformers --listen --enable-insecure-extension-access --api call webui.bat ``` 3. Attempt to connect Automatic1111 to Open WebUI by providing the URL `http://127.0.0.1:7860/`. ### Observed Behavior The error message is displayed: ``` Oops! The URL you provided is invalid. Please double-check and try again. ``` ## Additional Information - **Networking Context:** - Docker runs inside WSL on the same machine where Automatic1111 is hosted on Windows. - Docker uses `127.0.0.1:8080` for Open WebUI. If additional information or logs are required, please let me know. Thank you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
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#2937
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?