Self-Hosted Lobechat Community Edition Issue After Rebuild

[mortag]

Dear Lobechat Team,

I'm attempting to self-host Lobechat and add support for additional languages. After rebuilding the project using:

pnpm install
pnpm build
and creating a Docker image via docker build, the deployed instance runs in Community Edition mode and disapear all login and signing box.
I would greatly appreciate if you help me to find problem.

Regards,

[dosubot[bot]]

Hi @mortag! I'm Dosu and I’m helping the lobe-chat team.

Your instance is running in "Community Edition" mode (no login/signup) because authentication is not enabled by default. To show the login and signup boxes, you need to set the correct environment variables for authentication before building and running your Docker image. For example, set NEXT_PUBLIC_ENABLE_NEXT_AUTH=1 to enable NextAuth, or NEXT_PUBLIC_ENABLE_CLERK_AUTH=1 for Clerk (though Clerk is not fully supported in Docker due to environment variable limitations) source.

For Docker deployments, it's recommended to use providers like Auth0, Azure AD, GitHub, Authentik, Zitadel, or Logto, and set their required environment variables as well source. If these variables are missing or misconfigured, authentication is disabled and the login/signup UI disappears source.

Double-check your Docker build and runtime environment to ensure the necessary authentication variables are present. If you made changes for language support, make sure they didn't affect your authentication config. If you still don't see login/signup, check your Docker logs for any errors related to authentication setup.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[mortag]

Hi @dosu!

Thank you for the clear explanation! I appreciate you identifying the core issue with authentication configuration. I'd like to implement authentication using Casdoor instead of the providers mentioned. Could you clarify:

Are there specific Casdoor environment variables I need to set beyond the standard NextAuth configuration?

Is any additional source code modification required when building with pnpm build?

Does Casdoor require special Docker build arguments or runtime configuration different from other OAuth providers?

Thanks,

[dosubot[bot]]

Casdoor is natively supported in Lobe Chat—no source code changes are needed, just environment variable configuration. You’ll need to set: AUTH_CASDOOR_ID (client ID), AUTH_CASDOOR_SECRET (client secret), AUTH_CASDOOR_ISSUER (OIDC issuer URL), NEXT_AUTH_SECRET (session encryption key), NEXT_AUTH_SSO_PROVIDERS (should be casdoor), and NEXTAUTH_URL (your Lobe Chat callback URL). If you want to use Casdoor webhooks, set CASDOOR_WEBHOOK_SECRET as well. These are in addition to the standard NextAuth variables, but all are handled via environment variables—no special Docker build args or runtime config are required beyond this. Make sure your Casdoor app’s redirect URL matches your deployment (e.g., http://localhost:3210/api/auth/callback/casdoor) and that your Lobe Chat version is up to date for best compatibility. More details and a full variable list are in the docs and codebase (example).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[mortag]

Thanks again and I just a question:
These environment variables must be set at RUNTIME (when launching the container), or during the build phase(with pnpm) or build image (with docker)?

[mortag]

Another thing:
My understanding based on the LICENSE file is that while LobeChat is distributed under Apache License 2.0, there are additional conditions for commercial and derivative usage:
Commercial usage without modifying the source is permitted.
However, if I develop and distribute a derivative work, I am required to obtain a commercial license from the producer.
That is true?

Thanks,

[mortag]

It is resolved.