FYI: blocking /health API endpoint causes critical UI issues #5961
jerkstorecaller
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just posting this in case it helps others.
At one point after an update Librechat became unusable for me, I posted about it here: #4626 (but don't read that link for info, it's out-of-date and I was just logging random info, I have now found the issue)
My setup is Librechat behind nginx acting as reverse proxy. nginx uses basic_auth, with everything password-protected except some whitelisted endpoints. I do this because I'm not an IT guy, and I don't want to worry about cybersecurity: I want to set up a server once, and forget about it, without any risk of being hacked (basic_auth + fail2ban ensures that).
To get to the point, if you're running into any of these issues:
The culprit is a new /health API endpoint added in 0.7.6. Don't ask me why something so innucuous-sounding breaks the UI if it's blocked, it just does, and whitelisting it fixed all these problems for me. If you have the same basic_auth setup as me, and are reading this in the future and something else is broken, open your browser console and look for any 401 Unauthorized, that's probably a new endpoint you need to whitelist.
Corrected nginx.conf configuration:
Beta Was this translation helpful? Give feedback.
All reactions