Originally created by @madpin on GitHub (Jul 9, 2024).
Bug Report
Description
Bug Summary:
The new version: 0.3.8 the website shows the error: "Internal Server Error"
And absolutely no logs in the terminal.
I'm using the docker-compose:
Steps to Reproduce:
With the postgres in another docker, I wasn't able to make it work.
If I turn off postgres, it was working fine with the sqlite.
Expected Behavior:
No errors :)
Actual Behavior:
[Describe what actually happened.]
Environment
Open WebUI Version: 0.3.8
Ollama (if applicable): NA
Operating System: Ubuntu, but actually Docker
Browser (if applicable): NA
Reproduction Details
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.
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
[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 @madpin on GitHub (Jul 9, 2024).
# Bug Report
## Description
**Bug Summary:**
The new version: 0.3.8 the website shows the error: "Internal Server Error"
And absolutely no logs in the terminal.
I'm using the docker-compose:
In my case:
```
owui:
image: ghcr.io/open-webui/open-webui:0.3.7
container_name: owui
user: 1002:1002
networks:
- caddy
- infra
- llm_infra
environment:
- PORT=8081
- GLOBAL_LOG_LEVEL=DEBUG
env_file:
- owui.env
volumes:
- ${HOME}/configs/open-webui:/app/backend/data
labels:
caddy: owui.xxxxx.com
caddy.reverse_proxy: "{{upstreams 8081}}"
restart: unless-stopped
```
**Steps to Reproduce:**
With the postgres in another docker, I wasn't able to make it work.
If I turn off postgres, it was working fine with the sqlite.
**Expected Behavior:**
No errors :)
**Actual Behavior:**
[Describe what actually happened.]
## Environment
- **Open WebUI Version:** 0.3.8
- **Ollama (if applicable):** NA
- **Operating System:** Ubuntu, but actually Docker
- **Browser (if applicable):** NA
## Reproduction Details
**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.
## 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
[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!
Are you using @ symbol for the password authentication by chance? That caused the issue for me with the migration, and I had to URL-encode the password. Keep us updated!
@tjbck commented on GitHub (Jul 10, 2024):
Are you using `@` symbol for the password authentication by chance? That caused the issue for me with the migration, and I had to [URL-encode the password](https://docs.sqlalchemy.org/en/20/core/engines.html#escaping-special-characters-such-as-signs-in-passwords). Keep us updated!
Of cooourse I'm not using the "@" sign in my password....
Hahaha, the worst thing: I had this problem at my work a few months ago.
Thanks a million, @tjbck, that was exactly the problem. <3
@madpin commented on GitHub (Jul 10, 2024):
Of cooourse I'm not using the "@" sign in my password....
Hahaha, the worst thing: I had this problem at my work a few months ago.
Thanks a million, @tjbck, that was exactly the problem. <3
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 @madpin on GitHub (Jul 9, 2024).
Bug Report
Description
Bug Summary:
The new version: 0.3.8 the website shows the error: "Internal Server Error"
And absolutely no logs in the terminal.
I'm using the docker-compose:
In my case:
Steps to Reproduce:
With the postgres in another docker, I wasn't able to make it work.
If I turn off postgres, it was working fine with the sqlite.
Expected Behavior:
No errors :)
Actual Behavior:
[Describe what actually happened.]
Environment
Open WebUI Version: 0.3.8
Ollama (if applicable): NA
Operating System: Ubuntu, but actually Docker
Browser (if applicable): NA
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
[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!
@madpin commented on GitHub (Jul 10, 2024):
The startup log:
@tjbck commented on GitHub (Jul 10, 2024):
Are you using
@symbol for the password authentication by chance? That caused the issue for me with the migration, and I had to URL-encode the password. Keep us updated!@madpin commented on GitHub (Jul 10, 2024):
Of cooourse I'm not using the "@" sign in my password....
Hahaha, the worst thing: I had this problem at my work a few months ago.
Thanks a million, @tjbck, that was exactly the problem. <3