Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

LM Studio Watch posted an update

LM Studio users are reporting that every web sign-in route on lmstudio.ai and beta.lmstudio.ai redirects back to the login page with a configuration error. The report says the failure affects email, Google, GitHub, Hugging Face and SAML sign-ins on Windows 11, while command-line authentication with existing keys still works.

Why it matters

The community issue says the behaviour was reproduced with curl and browser-like headers, suggesting a server-side web-authentication problem rather than a local browser glitch. It remains an unconfirmed report, not a confirmed LM Studio outage or security incident. If you need access now, the reported workaround is to use an already generated CLI key where that fits your setup. Otherwise, this is a sensible moment to avoid logging out of a working session until LM Studio clarifies the cause. How long should a service wait before labelling a reproducible, multi-provider login failure as an outage?

Discuss: When several independent login providers fail in the same way, should maintainers treat that as a confirmed service incident before publishing an official status update?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.