|
| 1 | +--- |
| 2 | +description: What the Redis authentication change means for self-hosted Appsmith and how to upgrade for each deployment type. |
| 3 | +--- |
| 4 | + |
| 5 | +# Secure Redis on self-hosted Appsmith |
| 6 | + |
| 7 | +Appsmith uses Redis for session storage and caching. On some older self-hosted setups, the bundled Redis ran **without a password by default**, so a user who could reach it could read or write that data. Recent releases enable Redis authentication by default. |
| 8 | + |
| 9 | +**Quick impact check:** if your Redis already requires a password, you are not affected. Otherwise, follow the section for your deployment. |
| 10 | + |
| 11 | +## Docker / Docker Compose |
| 12 | + |
| 13 | +Upgrade to **v2.0 or later**. Password authentication on the embedded Redis is enabled by default, for both new and existing installs, so there is no manual step. You can find the latest release on the [Appsmith releases page](https://github.com/appsmithorg/appsmith/releases). |
| 14 | + |
| 15 | +If you are on a version older than v1.96, upgrade to **v1.99 first** (a required checkpoint), then move to v2.0 or later. See [Upgrade to Checkpoint Version](/getting-started/setup/instance-management/upgrade-to-checkpoint-version). |
| 16 | + |
| 17 | +## Kubernetes (Appsmith Helm chart) |
| 18 | + |
| 19 | +Upgrade to **chart 3.9.0 or later**, where the bundled Redis is password-protected by default. |
| 20 | + |
| 21 | +**Upgrading alone is not enough if your `values.yaml` sets `redis.auth.enabled: false`.** Remove that override, since it keeps Redis unauthenticated. If you already manage a Redis password, you keep using it. |
| 22 | + |
| 23 | +Full steps for every scenario: [Enable Redis Authentication](/getting-started/setup/installation-guides/kubernetes/enable-redis-auth). |
| 24 | + |
| 25 | +## External or cloud-managed Redis |
| 26 | + |
| 27 | +For AWS ElastiCache, Azure Cache for Redis, GCP Memorystore, or Redis Cloud, **enable authentication on the instance and connect with credentials**. The chart and container will not add it for you. |
| 28 | + |
| 29 | +Provider-specific formats and steps: [Enable authentication for external Redis](/getting-started/setup/instance-configuration/external-redis#enable-authentication). |
| 30 | + |
| 31 | +## How urgent is this? |
| 32 | + |
| 33 | +It depends on who can access your Appsmith instance. |
| 34 | + |
| 35 | +- **If your instance is publicly accessible with signups enabled, upgrade as soon as possible.** Anyone who can register and log in could reach Redis. |
| 36 | +- **If your instance is internal only and signups are disabled**, the exposure is limited to trusted users, so you can accept the risk until a normal maintenance window. |
| 37 | + |
| 38 | +If you have questions about upgrading or how this affects your deployment, reach out to support@appsmith.com. |
0 commit comments