mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #10887] 500: Internal Error #16065
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#16065
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 @peter-ch on GitHub (Feb 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10887
I upgraded to version 0.5.17 and all I see is 500: Internal Error now, nothing else. Clearing the cache, reinstalling with --force-reinstall didn't fix it.
@1zilc commented on GitHub (Feb 27, 2025):
same here!
@jmio23 commented on GitHub (Feb 27, 2025):
+1
Also noticed it is downloading files from GitHub every time it starts, I don't think this should be happening ?
@fti7 commented on GitHub (Feb 27, 2025):
Same here. No Errors in Log
@galvanoid commented on GitHub (Feb 27, 2025):
Same here, 500: internal error.
@peyloride commented on GitHub (Feb 27, 2025):
Same here, lost 1 hour because of this
@HougeLangley commented on GitHub (Feb 27, 2025):
@lyp49472060 commented on GitHub (Feb 27, 2025):
+1
@zyh1994 commented on GitHub (Feb 27, 2025):
I have the same problem, but i roll bak to v0.5.16, the question does not appear. so i think that the version 0.5.17 has some problem, it needs to be fixed
@baptisterajaut commented on GitHub (Feb 27, 2025):
Checking in with same issue.
Admin access is still there for the record.
I've noticed openai was enabled without api key and was causing some 500, disabling openai integration did not fix the issue.
I tried disabling basically everything in the admin, to no change. (Including the onedrive integration that causes an error in the js console)
Cleared all browser caches, no change.
I'm using a pip installation, not docker.
@lumitry commented on GitHub (Feb 27, 2025):
I'm on Docker install, getting same issue. Can't even log in as my admin account. Getting error in chrome devtools related to the onedrive file picker, it seems?
@gaby commented on GitHub (Feb 27, 2025):
Ping @tjbck
@ycros commented on GitHub (Feb 27, 2025):
Ah, crypto.randomUUID only exists in a HTTPS (secure) context.
@Yoshi-OOF commented on GitHub (Feb 27, 2025):
Same issue here
@anomaly256 commented on GitHub (Feb 27, 2025):
haven't touched it for a few weeks and decided to upgrade 5 minutes ago, lucky timing 😄
@ghost commented on GitHub (Feb 27, 2025):
same issue
@Tanamaz commented on GitHub (Feb 27, 2025):
same issue
@HougeLangley commented on GitHub (Feb 27, 2025):
The general process for updating openwebui is to check for a new version being pushed, and then wait for 3 hours to see if there are any new threads in the issues section before proceeding with the update.
@Iatbzh commented on GitHub (Feb 27, 2025):
+1
@NikolasTh90 commented on GitHub (Feb 27, 2025):
Same issue here. The developers need to provide a fix as soon as possible @
@peter-ch commented on GitHub (Feb 27, 2025):
Reverting to .16 fixes it so I guess let's just wait for the maintainers to notice.
@ollybrain commented on GitHub (Feb 27, 2025):
same issue
@mtzortzis commented on GitHub (Feb 27, 2025):
Same issue. Are there any instructions on rolling back docker container?
@galvanoid commented on GitHub (Feb 27, 2025):
Recreate: ghcr.io/open-webui/open-webui:0.5.16
@Iatbzh commented on GitHub (Feb 27, 2025):
+1
@Fusili commented on GitHub (Feb 27, 2025):
Also having the same issue. It only happens on the chat page. If I manually type the address to any pages like /admin or /admin/settings, it will load that page. Still gives 500 error when navigating back to chat.
@muslu commented on GitHub (Feb 27, 2025):
+2
@jadersimoes commented on GitHub (Feb 27, 2025):
Same issue here after updating through watchtower
@FengKeWG commented on GitHub (Feb 27, 2025):
+1
@NikolasTh90 commented on GitHub (Feb 27, 2025):
Use image ghcr.io/open-webui/open-webui:0.5.16 instead of ghcr.io/open-webui/open-webui:main
@arty-hlr commented on GitHub (Feb 27, 2025):
Big big lack of testing on that one... or maybe generally
@alaerock commented on GitHub (Feb 27, 2025):
or add
WEBUI_DOCKER_TAG=0.5.16to the .env file if used@mtzortzis commented on GitHub (Feb 27, 2025):
not using a .env so I guess I'll have to recreate it, thank you
@jhstatewide commented on GitHub (Feb 27, 2025):
Oh, I didn't realize you were paying for a support contract.
@ollybrain commented on GitHub (Feb 27, 2025):
Recreate: ghcr.io/open-webui/open-webui:0.5.16
Sounds nice, but how will it be with the GPU usage?
@jaceyang97 commented on GitHub (Feb 27, 2025):
+1 revert back to 0.5.16 solves the problem temporarily
@arty-hlr commented on GitHub (Feb 27, 2025):
@ollybrain I made it with
:0.5.16-cudaas a tag@ollybrain commented on GitHub (Feb 27, 2025):
YES, it works. thank you very much for the quick support.
@gtfxing commented on GitHub (Feb 27, 2025):
DATA_DIR=CHANGEHERE TO YOUR DIR uvx --python 3.11 open-webui@0.5.16 serve
DATA_DIR=~/.open-webui uvx --python 3.11 open-webui@0.5.16 serve
@bailei951 commented on GitHub (Feb 27, 2025):
+1
@wqshmzh commented on GitHub (Feb 27, 2025):
SAME HERE
@Kaliytor commented on GitHub (Feb 27, 2025):
+++++++++++1！
@aspwebchh commented on GitHub (Feb 27, 2025):
+++++++++++++1
@emrothenberg commented on GitHub (Feb 27, 2025):
Solving Error in v0.5.17 Using Ngrok (Bypass HTTPS)
Issue:
The error occurs because the application is running over HTTP without SSL encryption. This causes browsers and other clients to block access or show security warnings when trying to connect.
Workaround:
Using Ngrok, you can create a secure HTTPS tunnel to your local server. This also enables remote access to the service.
Steps:
Sign Up for Ngrok
Download and Install Ngrok
PATHfor easy access.Authenticate Ngrok
YOUR_AUTH_TOKENwith the authentication token provided in your Ngrok dashboard.Expose Local Server
3000, start an Ngrok tunnel with:http://localhost:3000.Benefits of This Method:
This method ensures you can access your application securely without modifying the backend to support SSL.
@cl93a commented on GitHub (Feb 27, 2025):
Same issue
@sunruichao commented on GitHub (Feb 27, 2025):
Same here, 500: internal error.
@Kaliytor commented on GitHub (Feb 27, 2025):
how to roll bak, I use rasp+openmidiavault+compose+docker, and I don't know how to download the older version
@cupuyc1 commented on GitHub (Feb 27, 2025):
after update im having 500 error pls. fix it
@HougeLangley commented on GitHub (Feb 27, 2025):
pip install open-webui==0.5.16 --force-reinstall@sdcgi commented on GitHub (Feb 27, 2025):
Same issue. Using Docker + watchtower, must be after an auto update. 0.5.17
@rabinnh commented on GitHub (Feb 27, 2025):
Same, broken release.
@nonsleepr commented on GitHub (Feb 27, 2025):
This is, indeed an issue with OneDrive when Open-WebUI is served via HTTP, @emrothenberg's workaround (or Tailscale's TLS in my case) resolves the issue.
@melianor commented on GitHub (Feb 27, 2025):
Logging in through http://localhost:3000 works as it should.
As soon as one opens Open Webui with the IP address of the machine that has open webui running, the error 500: Internal Error is presented after login
Reproduce the error:
So why does this work when opened through localhost, but not with IP ?
@qwerpoiugb commented on GitHub (Feb 27, 2025):
+1
@qwerpoiugb commented on GitHub (Feb 27, 2025):
thx
@sdcgi commented on GitHub (Feb 27, 2025):
localhost workarround confirmed
@rabinnh commented on GitHub (Feb 27, 2025):
For those using the docker image, just change the docker "run" command to use the previous version. Instead of
ghcr.io/open-webui/open-webui:mainuse:
ghcr.io/open-webui/open-webui:v0.5.16@washcontacnet1 commented on GitHub (Feb 27, 2025):
After update to 0.5.17, I had the same problem.
What I did
At Docker Stoped the container and click remove.
At CMD, the following prompts
1 - Reinstall version 0.5.16
pip install open-webui==0.5.16 --force-reinstall
2 - Force Docker to use the old version
docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:v0.5.16
And it's all, everything is works again.
NOTE: I tried to find the solution for 4 hours after identify the problem, the solution ahead works to me, if works to you too, let me know.
@melianor commented on GitHub (Feb 27, 2025):
Rolling back to the last version is hopefully not the final resolution of this issue ;)
@washcontacnet1 commented on GitHub (Feb 27, 2025):
I agree, but, do you have the final solution?
I have the same trouble that you have.
OpenwebUI works on local host, but not work on IP.
I have a lot of user using by IP, and everybody was waiting a solution.
When the problem is solved at 0.5.17 version (or in another one), I will update again.
@emrothenberg commented on GitHub (Feb 27, 2025):
You can use ngrok, as I detailed here in a previous answer:
https://github.com/open-webui/open-webui/issues/10887#issuecomment-2688377059
@sdcgi commented on GitHub (Feb 27, 2025):
Having a really strange issue now. Rolled back to 0.5.16, can log in (no error) but the page is blank. But if you wait a few minutes the interface appears. Literally minutes. This can't have any connection to the 0.5.17 issue...can it??
@andyarcha commented on GitHub (Feb 27, 2025):
I also had the same issue and pulled v0.5.16 with docker. All works again on v0.5.16
@zmdtk commented on GitHub (Feb 27, 2025):
Same issue here. It is resolved by reverting back to previous version 0.5.16
@harrywang commented on GitHub (Feb 27, 2025):
#10909 I had the same issue
@somera commented on GitHub (Feb 27, 2025):
Same here #10903
v0.5.16 -> works
v0.5.17 -> TypeError
@TheMasterFX commented on GitHub (Feb 27, 2025):
Same
@spolspol commented on GitHub (Feb 27, 2025):
reported same here with more details: #10912
@TheMasterFX commented on GitHub (Feb 27, 2025):
If I go to "http://mydomain.com:3000/admin/settings" the page at least loads and you can edit some settings
@erock530 commented on GitHub (Feb 27, 2025):
Seems crypto.randomUUID() only works behind SSL. See Link
I got it working using SSL behind nginx. I run open-webui in a docker container on a Linux server.
This is what I did as a workaround:
Create a DNS entry on a domain you have control over (ex. llm.internal.domain.com) and point the A record to the internal IP of your server that hosts the openweb-ui.
On the server that has both nginx installed and running the docker container:
$ sudo certbot certonly --manual --preferred-challenges dns -d "llm.internal.domain.com"Follow certbot instructions.
Add the SSL lines for the generated certs to your nginx config that handles "llm.internal.domain.com" :
listen 443 ssl; server_name llm.internal.domain.com; ssl_certificate /etc/letsencrypt/live/llm.internal.domain.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/llm.internal.domain.com/privkey.pem;Make sure you have appropriate proxy_pass lines.
location / { proxy_pass http://127.0.0.1:8080/; }Again, this worked for me for how I have the architecture built.
@TheMasterFX commented on GitHub (Feb 27, 2025):
Maybe a fix could be that ENABLE_ONEDRIVE_INTEGRATION=False disables everything which has something to do with Onedrive (py + ts)
@spolspol commented on GitHub (Feb 27, 2025):
@erock530 forcing setup with additional proxy for SSL is not really solving the issue. It shold not be requirement.
@erock530 commented on GitHub (Feb 27, 2025):
@spolspol
agreed. this was just a workaround that worked for me. I agree though, if SSL isn't being used, then using crypto.randomUUID() should be avoided and replaced with another func and not be a requirement.
@derekbsnider commented on GitHub (Feb 27, 2025):
Also having the exact same issue. Glad it's not just me. I'm running open-webui under WSL (without docker).
With Admin PowerShell I used this to allow external access:
Everything works fine with localhost:8080.
When using the 192.168.1.X:3000 address, I can log in, I can access the admin panel, but everything else displays "500: Internal Error" in the browser. This worked fine with the previous release.
@mcollinsece commented on GitHub (Feb 27, 2025):
Same issue. I'm fronting with a traefik load balancer, so I thought it was something with my routes. Spent 2 hours troubleshooting until I found this post. Downgrading to v0.5.16 fixed it.
@tjbck commented on GitHub (Feb 27, 2025):
Fixed with 0.5.18
@somera commented on GitHub (Feb 27, 2025):
Works now. Thx!
@tjbck commented on GitHub (Feb 27, 2025):
PSA: We Need YOUR Help!
First, I want to sincerely apologize for the recent issue with version 0.5.17. It has been resolved in 0.5.18, and I truly appreciate your patience. However, I want to take this moment to talk about something bigger—something we can’t fix alone.
The truth is, we’re not a big tech company with unlimited resources. We’re a small, dedicated team doing everything we can to make this project the best it can be, but we’re stretched thin. Mistakes happen, and while we move quickly to fix them, the reality is that we need more hands, more eyes, and more help.
That’s why we’re asking for your support. One of the biggest things you can do is use the
:devbranch image instead of:main—it’s as simple as changing the Docker image tag to:dev. This helps us catch potential issues earlier, preventing headaches for everyone.But beyond that, we need testers, contributors, bug reports, and feedback. Every little bit helps more than you can imagine. If you’ve ever wanted to be part of something meaningful—to help build and shape something great—now’s the time.
This community is only as strong as the people in it, and right now, we need YOU. If you can help in any way, please do. Together, we can ensure this project continues to thrive.
Thank you for being here. Thank you for believing in this. And thank you in advance for stepping up—you are what makes this possible. 💙
@somera commented on GitHub (Feb 27, 2025):
@tjbck sounds goot. I can set up a second instance myself. But I only have time to take a look at it once a week. It would be difficult to do it more often.
@melianor commented on GitHub (Feb 27, 2025):
I'll gladly give feedback as we here at home use open webui :)
@derekbsnider commented on GitHub (Feb 27, 2025):
This was fixed pretty quick, so kudos to you!
@aspwebchh commented on GitHub (Feb 28, 2025):
Last night's problem, did not fix, but peace of mind to sleep, should believe that wake up, 0.5.18 will certainly be released quickly, to solve the problem
@tomcatai commented on GitHub (Jun 16, 2025):
文件夹下面的env.exmple重新命名为env