Understand the two Redis controls

Distinguish Snappy Redis service startup from application-specific Redis cache configuration.

Where Tools → Software → Redis Manager by Snappy / LiteSpeed Redis Cache

Before you start

Confirm Redis is included and that your application supports it.
Get the correct account-specific connection method from the provider; do not copy an example socket path.

1

Open Redis Manager by Snappy and read the service status.
2

Obtain the actual socket/host, port and any required authentication from the manager or support. Keep credentials private and do not assume the example in another screen is your assigned connection.
3

Configure the application’s supported object-cache integration with the confirmed settings. Test the connection before enabling it for a live site.
4

If disabling Redis later, disable the dependent application integration first so the website does not keep trying to use a stopped service.
5

Start Redis starts the account service. Use it only when you intend to allocate that service, then wait for the manager to report a completed state.

This is the service startup control; it was not clicked during capture.
6

Open LiteSpeed Redis Cache to review its integration guidance. The observed page says Redis must be configured by the administrator; it is not proof that the Snappy service is already configured.

This separate page requires administrator configuration; example paths are not account credentials.