mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-08 04:16:03 -05:00
[GH-ISSUE #15882] issue: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE for v0.6.16 and above for OpenShift (k8s) FIPS enabled environment #17705
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 @jayteaftw on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15882
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.16,v0.6.17,v0.6.18
Ollama Version (if applicable)
No response
Operating System
Openshift 4.17.9
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Expect open webui to start like it did in v0.16.15
Actual Behavior
In v0.6.16 and beyond, Open Webui now fails with error
crypto/fips/fips.c:154: OpenSSL internal error: FATAL FIPS SELFTEST FAILURESteps to Reproduce
Within an openshift(k8s) FIPS enabled environment, created a deployment file such as
Logs & Screenshots
Additional Information
I noticed that the cryptography package was added in v0.6.16. Could that be causing the issue?
@jayteaftw commented on GitHub (Jul 20, 2025):
Okay I have added OPENSSL_FORCE_FIPS_MODE=0, and open webui successfully started. However this means FIPS has been disabled which is not a working solutionAfter retesting this, I could not reproduce the results I claimed.
@rgaricano commented on GitHub (Jul 20, 2025):
The chromadb issue due to posthog recent update was fixed in v0.6.17
could you post the error log but with image: ghcr.io/open-webui/open-webui:v0.6.17 or image: ghcr.io/open-webui/open-webui:v0.6.18 ?
@jayteaftw commented on GitHub (Jul 20, 2025):
I tested both v.0.6.17 and v0.6.18 before posting but here are the logs for v.0.6.18
@rgaricano commented on GitHub (Jul 20, 2025):
I was searching about and there some workaround that you can try,
e GOFIPS=1to docker line)pip uninstall cryptography -yI would try one and then the other.
Another source of problems with FIPS is when installing Python with FIPS disabled, it may also be necessary to rebuild Docker/package, ensuring that FIPS is enabled.
(sorry but I haven't any FIPS enviroment to try)
(I would appreciate your feedback if you get any results.)
@jayteaftw commented on GitHub (Jul 21, 2025):
GOFIPS=1 did not work.
After uninstalling cryptography, open webui errors out
I also tried uninstall and reinstalling on the FIPS enabled system and it did not work.
@rgaricano commented on GitHub (Jul 21, 2025):
thanks for test,
could you do another try, just to be sure:
pip install -U cryptography[fips]and tryIf not work probably the best solution could be make a specific build similar to:
(but I think that this don't to be necessary as it was working fine before)
@rgaricano commented on GitHub (Jul 21, 2025):
Maybe we can continue that discussion in FIPS Compatibility?
@jayteaftw commented on GitHub (Jul 23, 2025):
I tried the pip install -U cryptography[fips] and it did not work but I think that is because crypto package does not have a fips tag. Also tried building a docker image with the requirement.txt file and it fails when import torchaudio
@icsy7867 commented on GitHub (Jul 24, 2025):
Came here searching for versions...
Though I would like to add that something else is amiss...
I see you are using openshift, which means you are using RHEL? Or some flavor of RHEL?
I dont know what check Open-WebUI is doing, but redhat actually handles most FIPS things in the kernel of the host.
And what do containers share with their host? Yep... the kernel... so if FIPS is enabled on the host and OPENSSL_FORCE_FIPS_MODE=0 lets open-webui run, then I am not sure what that is really doing... Your system/container will still be in FIPS mode, and the kernel should enforce the FIPS 140-2 or 140-3 requirements for the most part.
All this to say, it seems like something wonky is going on here...
However on my k8s cluster running on RHEL9, this does not fix it.
@jayteaftw commented on GitHub (Jul 24, 2025):
Hey I retested what I claimed and could not get the container to start with OPENSSL_FORCE_FIPS_MODE=0 with versions v0.6.16,17,18. This would make sense since FIPs is kernel level and would not make sense if a pod could simply disable FIPS. However whats interesting is
The latter seems possible but I dont understand the former.
@smithmh6 commented on GitHub (Aug 1, 2025):
I ran into this same issue, and it has nothing to do with sentence_transformers. I narrowed it down to PyAV, which is being installed by torchvision and torchaudio. PyAV relies on ffmpeg, which is non-FIPS compliant when installed by apt-get and linked to non-FIPS headers.
@jayteaftw commented on GitHub (Aug 11, 2025):
Tested v0.6.19 on a FIPS system and it seems to be working!