Book a demo
Book a demo
Login

How to Find Redis Credentials and Fix Redis Connection Errors

Updated November 5, 2026 · 5 min read

Summarize with:
Share:

Every site on xCloud that uses the server’s Redis has its own Redis user, Redis password and Redis object cache key. You can find them on a WordPress site’s Caching page or under ‘Access Data’ → ‘Credentials’, which also shows the Redis Host and Redis Port a custom PHP or Laravel app needs. When a site shows a Redis connection or authentication error, the values in its wp-config.php usually no longer match these, which happens most often after a migration, an import or a clone. This guide shows where to find the credentials and how to fix the error.

Find the Redis credentials for a site

Step 1: Open the site’s Caching page

Go to ‘Sites’, open your site, then click ‘WordPress’ → ‘Caching’ in the left menu. On an Nginx server, the Redis User, Redis Password and Redis Object Cache Key fields appear under the Redis Object Cache switch while it is on. Click the eye icon to show the password and Copy to copy any value.

The Redis User, Redis Password and Redis Object Cache Key fields under Redis Object Cache on an Nginx site’s ‘WordPress’ → ‘Caching’ page

On an OpenLiteSpeed server, LiteSpeed Cache provides the object cache. The same three fields appear under the LiteSpeed Cache switch on the same page.

The Redis credentials under the LiteSpeed Cache switch on an OpenLiteSpeed site’s ‘WordPress’ → ‘Caching’ page

Step 2: Or open the site’s Credentials page

The same values are also listed in the Redis Credentials card under ‘Access Data’ → ‘Credentials’, next to the site’s other logins. The card also shows the Redis Host (127.0.0.1) and Redis Port (6379), each with a Copy button. It appears when the site has Redis credentials. Docker Compose sites, One-Click and template apps (except Lovable), and Paperclip sites have no Redis card.

The Redis Credentials card on the site’s ‘Access Data’ → ‘Credentials’ page

The Redis Object Cache Key is the prefix the site’s cache keys must start with. The site’s Redis user may only read and write keys with that prefix, so a site can’t use another site’s credentials, even on the same server.

Connect a custom PHP or Laravel app to Redis

A custom PHP or Laravel site deployed from Git has no Caching page, so its Redis values live only on the Credentials page. Your app needs all five of them in its .env file.

Step 1: Copy the values from the Credentials page

Open the site, then click ‘Access Data’ → ‘Credentials’. In the Redis Credentials card, copy Redis Host, Redis Port, Redis User, Redis Password (click the eye icon to show it) and Redis Object Cache Key.

The Redis Host and Redis Port fields in the Redis Credentials card on a custom PHP site’s ‘Access Data’ → ‘Credentials’ page

Step 2: Add them to your app’s .env file

Put each value in the matching variable. These are the names Laravel uses:

Credentials page .env variable
Redis Host REDIS_HOST
Redis Port REDIS_PORT
Redis User REDIS_USERNAME
Redis Password REDIS_PASSWORD
Redis Object Cache Key REDIS_PREFIX 
REDIS_HOST=127.0.0.1
REDIS_PORT=6379
REDIS_USERNAME=YOUR_REDIS_USER
REDIS_PASSWORD=YOUR_REDIS_PASSWORD
REDIS_PREFIX=YOUR_REDIS_OBJECT_CACHE_KEY

On a custom PHP site or a Node.js app, the card shows this note: “Your app must use the Redis Object Cache Key as its Redis key prefix (REDIS_PREFIX). This Redis user can only read and write keys that start with it.” An app that uses another prefix, or none, gets a NOPERM error. If your app has no prefix setting, add the key to the start of every key name yourself.

For a Laravel site, xCloud writes these values to .env for you when it deploys the repository on a server with Redis. Use the Credentials page to check them, or to set them again if you replaced the .env file.

Fix a Redis connection or authentication error

Typical messages are WRONGPASS invalid username-password pair or user is disabled, a NOPERM permission error, or the Redis Object Cache plugin reporting that it can’t connect. They mean the site is logging in to Redis with a user, password or key prefix that doesn’t match what xCloud set up for it.

The most common cause is a migration, import or clone. The new site gets its own Redis user, password and key (the key includes the site’s ID), but the copied wp-config.php can still contain the old site’s values.

Step 1: Turn the object cache off and on again

On the site’s ‘WordPress’ → ‘Caching’ page, turn the switch off, wait until the spinner next to it stops, then turn it on again:

  • Nginx: use the Redis Object Cache switch.
  • OpenLiteSpeed: use the LiteSpeed Cache switch.

The Redis Object Cache switch on the site’s ‘WordPress’ → ‘Caching’ page

Turning it back on writes the site’s current Redis user, password, key prefix and Redis database to wp-config.php and updates the site’s Redis user on the server. Reload the site afterwards and check that the error is gone. In WordPress, Settings → Redis (the Redis Object Cache plugin) shows whether the site can connect.

If the Redis Password field still doesn’t appear after you turn the cache back on, contact support so the site’s Redis password can be set up again.

Step 2: Make sure the Redis service is running

If the error continues, check Redis itself. Open the server, then go to ‘Management’ → ‘Settings’. In Server Utilities, find Redis and check that its status is Active. Click Restart if it isn’t running. If Redis isn’t in the list, install it from Install a Service below the table, then repeat Step 1.

The Redis row with its status and Restart button in Server Utilities under the server’s ‘Management’ → ‘Settings’

Step 3: Set the values by hand only if you manage wp-config.php yourself

This step is for Nginx sites using the Redis Object Cache plugin only. On OpenLiteSpeed, xCloud stores the values in LiteSpeed Cache’s own settings instead of these constants: enter them in LiteSpeed Cache → Cache → Object in WordPress admin, or simply use Step 1.

xCloud manages these constants for you, so you don’t normally need to edit them. If you use your own Redis plugin settings, copy the values from Step 1 of the first section and keep them in this form:

define( 'WP_REDIS_PASSWORD', [ 'REDIS_USER', 'REDIS_PASSWORD' ] );
define( 'WP_REDIS_PREFIX', 'REDIS_OBJECT_CACHE_KEY' );
define( 'WP_REDIS_DATABASE', REDIS_DATABASE_NUMBER );
define( 'WP_REDIS_SELECTIVE_FLUSH', true );

Replace the placeholders with the values from the site’s Caching page. Don’t copy them from another site or an old backup: they belong to one site only.

  • WP_REDIS_DATABASE: each site has its own Redis database number, and its Redis user may only select that database. Without this line the site uses database 0 and Redis answers with a NOPERM error. The number isn’t shown in the dashboard, so copy the WP_REDIS_DATABASE line from the wp-config.php xCloud wrote for this site, or run Step 1 once to write it.
  • WP_REDIS_SELECTIVE_FLUSH: the site’s Redis user isn’t allowed to empty the whole database (FLUSHDB), so the plugin must clear only the site’s own keys.

If the site was migrated with Redis Object Cache Pro still active, xCloud can’t turn on its own Redis Object Cache until Object Cache Pro is turned off. Use the Object Cache Pro switch on the same Caching page first.

Check the Redis users over SSH

If you can connect over SSH as root or a sudo user (see how to add SSH keys), each site’s Redis user and its key-prefix permission are listed in the server’s Redis ACL file:

sudo cat /etc/redis/users.acl

Use this to check that a site’s Redis user exists. Copy passwords from the dashboard, not from this file.

Frequently asked questions

Why does my site show a Redis error after a migration or clone?

Each xCloud site connects to Redis with its own Redis user, password and object cache key. A migrated or cloned site gets new values, but the copied wp-config.php can still hold the old ones, so Redis rejects the login or the keys. Turn the object cache off and on again from the site’s Caching page to write the current values.

Does turning Redis Object Cache off and on delete my data?

No. It only clears cached objects, which WordPress rebuilds from the database. Your site may be a little slower until the cache warms up again.

Can two sites on the same server share one Redis password?

No. Each site has its own Redis user and object cache key, and its Redis user can only read and write keys that start with that site’s key. Always copy the credentials of the site you are configuring.

Which Redis host and port does my custom PHP or Laravel app use?

Redis runs on the same server as your site, so the host is 127.0.0.1 and the port is 6379. Both are shown with the site’s Redis User, Redis Password and Redis Object Cache Key under ‘Access Data’ → ‘Credentials’.

If you run into any issues, feel free to reach out to our support team.