Unable to connect error #285

New Issue

2025-11-11T14:15:25-06:00

GiteaMirror commented

2025-11-11 14:15:25 -06:00

Originally created by @meminens on GitHub (Feb 10, 2024).

Bug Report

Description

Bug Summary:
http://127.0.0.1:3000/ not opening

Steps to Reproduce:

ollama serve
docker run -d --network=host -v ollama-webui:/app/backend/data -e OLLAMA_API_BASE_URL=http://127.0.0.1:11434/api --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:main
Visit http://127.0.0.1:3000/
Firefox show Unable to connect
http://127.0.0.1:11434/ shows Ollama is running
http://127.0.0.1:11434/api shows 404 page not found

Expected Behavior:
http://127.0.0.1:3000/ should show login page

Actual Behavior:
http://127.0.0.1:3000/ shows unable to connect error

Environment

Operating System:
Latest Arch on x86_64
Browser (if applicable):
Firefox 122.0.1

Reproduction Details

Confirmation:

[x ] I have read and followed all the instructions provided in the README.md.
I have reviewed the troubleshooting.md document.
I have included the browser console logs.
[x ] I have included the Docker container logs.

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:

No WEBUI_SECRET_KEY provided
Generating WEBUI_SECRET_KEY
Loading WEBUI_SECRET_KEY from .webui_secret_key
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)

Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]

Installation Method

[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]

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!

Originally created by @meminens on GitHub (Feb 10, 2024). # Bug Report ## Description **Bug Summary:** http://127.0.0.1:3000/ not opening **Steps to Reproduce:** ``` ollama serve docker run -d --network=host -v ollama-webui:/app/backend/data -e OLLAMA_API_BASE_URL=http://127.0.0.1:11434/api --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:main Visit http://127.0.0.1:3000/ Firefox show Unable to connect http://127.0.0.1:11434/ shows Ollama is running http://127.0.0.1:11434/api shows 404 page not found ``` **Expected Behavior:** http://127.0.0.1:3000/ should show login page **Actual Behavior:** http://127.0.0.1:3000/ shows unable to connect error ## Environment - **Operating System:** Latest Arch on x86_64 - **Browser (if applicable):** Firefox 122.0.1 ## Reproduction Details **Confirmation:** - [x ] I have read and followed all the instructions provided in the README.md. - [x] I have reviewed the troubleshooting.md document. - [ ] I have included the browser console logs. - [x ] I have included the Docker container logs. ## Logs and Screenshots **Browser Console Logs:** [Include relevant browser console logs, if applicable] **Docker Container Logs:** ``` No WEBUI_SECRET_KEY provided Generating WEBUI_SECRET_KEY Loading WEBUI_SECRET_KEY from .webui_secret_key INFO: Started server process [1] INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit) ``` **Screenshots (if applicable):** [Attach any relevant screenshots to help illustrate the issue] ## Installation Method [Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.] ## 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!

GiteaMirror closed this issue

2025-11-11 14:15:25 -06:00

GiteaMirror commented

2025-11-11 14:15:26 -06:00

@meminens commented on GitHub (Feb 10, 2024):

Sorry, I didn't realize I should be visiting http://127.0.0.1:8080. It's working just fine.

@meminens commented on GitHub (Feb 10, 2024): Sorry, I didn't realize I should be visiting `http://127.0.0.1:8080`. It's working just fine.