Optional object caching with account-specific connection settings.
Redis is available as an optional DirectAdmin feature. It is not switched on or connected to your applications automatically.
- Open DirectAdmin’s Redis screen and enable the account instance if you need it. Review the instance’s current connection and resource settings.
- Use the account-specific Unix socket or connection details shown by DirectAdmin. Do not copy another customer’s settings or point an app at a guessed shared service.
- For WordPress, install a compatible object-cache integration from a trusted source and follow that integration’s socket/authentication instructions. Use a unique prefix for each site sharing the account instance.
- Check the integration’s connection status and test important functions. Object caching is not full-page caching and does not guarantee faster performance for every workload.
- Monitor memory and account resources. Disable Redis if it is unused. Flush only the intended site’s cache; a broad flush can affect other sites sharing your account instance.
Do not expose Redis directly to the public Internet, use it as your only persistent data store, or assume cached data is backed up. The supported connection method and memory policy depend on the server configuration.
