Some configurations of the environment variable FEATURE_FLAGS are not working

[toddyoe]

📱 Client Type

Web (Desktop Browser)

💻 Operating System

Windows

📦 Deployment Platform

Self hosting Docker

🔧 Deployment Mode

server db (lobe-chat-database image)

📌 Version

2.0.0-next.110

🌐 Browser

Chrome, Firefox

🐛 Bug Description

The environment variable FEATURE_FLAGS is already set to -language_model_settings,-openai_api_key,-openai_proxy_url,-welcome_suggest,-clerk_sign_up,-dalle,+group_chat,-provider_settings,-api_key_manage, but the provider can still be configured or the model list can still be modified in the user settings. This issue did not exist in previous versions (v1.x).

📷 Recurrence Steps

No response

🚦 Expected Behavior

Once the FEATURE_FLAGS configuration is set, users cannot modify the supplier and model list, eliminating the need for an entry point in the user settings center.

📝 Additional Information

No response

🛠️ Willing to Submit a PR?

None

✅ Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a LobeChat issue and not a third-party library or provider issue.
• Check that this is a concrete bug. For Q&A, please use GitHub Discussions or join our Discord Server.

[lobehubbot]

@ONLY-yours - This is a feature:settings issue where FEATURE_FLAGS environment variable configurations are not properly disabling provider/model settings in the UI (regression from v1.x to v2.x). Please take a look.

[dosubot]

Your FEATURE_FLAGS syntax is correct and should disable provider/model configuration if the environment variable is properly loaded. In LobeChat v2.x, the UI and server logic still enforce these flags, so if users can still access provider/model settings, it's likely due to how Docker is passing the environment variable to the server process, not a change in the code logic itself.

Common causes and troubleshooting steps:

• Make sure FEATURE_FLAGS is set in your .env file, not directly in the Docker Compose file, and that Docker Compose references this .env file. The format should be:
  FEATURE_FLAGS="-language_model_settings,-provider_settings"
  (Quotes are recommended in .env, but in some Docker setups, removing them may help if parsing fails)
  source
• Restart the Docker containers after changing the .env file to ensure the new environment variables are loaded.
• Clear your browser cache or do a hard refresh to avoid stale UI.
• Check for any runtime config overrides or conflicting environment variables.
• If you are using static page generation or CDN caching, these can interfere with dynamic environment variable enforcement. This was a known issue in earlier versions and may still affect some Docker deployments source.
• You can check logs or add debugging to confirm that the server process is receiving the correct FEATURE_FLAGS value.

If all of the above are correct and the issue persists, it may be a regression or a limitation in how environment variables are propagated in your Docker/Next.js setup. This has been reported by other users as well, especially after static optimization changes in the app source.

Let me know if you want more detailed Docker Compose or .env examples, or if you need help checking the server logs for environment variable values.

To reply, just mention @dosu.

---

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

   

[github-actions]

Found 1 possible duplicate issue:

1. [Security bug] Client-side only validation of language_model_settings #8081

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[toddyoe]

Found 1 possible duplicate issue:

1. [[Security bug] Client-side only validation of language_model_settings #8081](https://github.com/lobehub/lobe-chat/issues/8081)

This issue will be automatically closed as a duplicate in 3 days.

* If your issue is a duplicate, please close it and 👍 the existing issue instead

* To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

This issue is different from the one you mentioned because I have already set -provider_settings.