-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postgres problem with the new 0.3.8 #3747
Comments
The startup log:
|
Are you using |
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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!
The text was updated successfully, but these errors were encountered: