📄️ My requests are being blocked by CORS
1. Make sure you've configured CORS access in Unleash admin UI settings as defined in the Unleash CORS Policy docs. These settings can be changed in the Unleash Dashboard under Settings -> CORS Origins or by using the API. Allowing all origins (using a single asterisk) will address this matter and is a great starting point when troubleshooting the behavior.
📄️ Configuring Unleash to run over HTTPS
Preferred methods for setting up HTTPS in self-hosted instances, from highly recommended to those requiring more caution:
📄️ The email service is not working correctly on my self-hosted Unleash instance
When setting up your self-hosted Unleash instance, one of the available options is to configure an email service that will allow Unleash to send reset password and welcome emails to users.
📄️ I don't see a documented Unleash feature in my admin UI
Occasionally, users might come across a situation where a documented Unleash feature isn't visible in their admin UI. Here's how to troubleshoot this issue.
📄️ My feature flag is enabled but all/some of our users are not exposed to it
To confirm how users will have flags resolved, follow these steps:
📄️ My feature flag is not returned in the Frontend API/Edge/Proxy
By default, these endpoints will not return feature flags that are not enabled. This is mainly to save on bandwidth but it makes it a bit difficult to debug when features are not being returned.
📄️ My feature flag is returning unexpected results in my A/B/n test
Occasionally, users might come across a situation where a feature flag is returning unexpected results when running an A/B/n test.