Troubleshooting guide

Redis Connection Refused: Checks for WordPress, Nextcloud and Web Apps

Troubleshoot Redis connection refused errors caused by stopped services, socket/TCP mismatch, bind settings, firewall rules and app configuration.

Remote support availableCommercial systemsService: Redis Support
Redisconnection refusedWordPressNextcloudcache

What this problem usually means

Redis connection refused usually means the application is trying to reach Redis on the wrong socket/port, Redis is stopped, the bind configuration blocks access, or the app and Redis are in different containers/networks.

Production caution: Changing Redis bind or protected-mode settings without understanding exposure can create a security risk. Redis should not be publicly accessible.

Common symptoms

  • WordPress object cache errors
  • Nextcloud Redis/file locking errors
  • Application logs show connection refused
  • Redis service fails after restart
  • Containers cannot resolve the Redis hostname

Common causes

  • Redis service stopped or failed to start
  • Application expects TCP but Redis uses a Unix socket
  • Wrong hostname inside Docker Compose network
  • Firewall or bind setting blocks access
  • Authentication/password mismatch
  • Redis memory policy or config prevents normal operation

Safe first checks

These checks are intended to help identify the direction of the issue. Always adjust paths, service names and commands for your environment.

Check Redis service

systemctl status redis-server --no-pager

Test Redis locally

redis-cli ping

Check listening sockets

ss -tulpn | grep redis

Check Docker networking

docker compose ps && docker compose logs redis --tail=80

Typical fixes

  • Match app config to Redis socket, host and port
  • Fix Docker service names and networks
  • Keep Redis private and protected from the internet
  • Check authentication configuration
  • Tune maxmemory policy for cache use cases
  • Restart dependent apps only after Redis is confirmed healthy

When to get help

Get help if the system is production-facing, customer data is involved, backups are uncertain, or the issue affects revenue, security or uptime. We can review the logs, confirm the cause and quote a fixed-scope fix where appropriate.

Need this fixed?

Get remote support for this issue.

Fixed technical support starts from $499. Emergency incident support is $199/hr with a minimum window.

Contact Us

Related guides