Import site with Redis pro enabled fails

Issue Summary

One or two sentence summary of the issue.

Troubleshooting Questions

We have enabled an existing site at Cloudways hosting with Redis Pro. If we export this and try to import it into a newly created Wordpress environment in Local, we get the following error message. What can we do to resolve this.
We have already tried to install Redis pro in the local Wordpress site before importing. Any help is welcome.

Fatal error: Uncaught RedisCachePro\Exceptions\PhpRedisMissingException: Object Cache Pro requires the PHP extension PhpRedis 3.1.1 or newer. The PhpRedis extension is not loaded in this environment (fpm-fcgi). If it was installed, be sure to load the extension in your php.ini and to restart your PHP and web server processes. in /Users/jaykersten/Local Sites/bielocal/app/public/wp-content/mu-plugins/redis-cache-pro/src/Connectors/PhpRedisConnector.php on line 40

( ! ) RedisCachePro\Exceptions\PhpRedisMissingException: Object Cache Pro requires the PHP extension PhpRedis 3.1.1 or newer. The PhpRedis extension is not loaded in this environment (fpm-fcgi). If it was installed, be sure to load the extension in your php.ini and to restart your PHP and web server processes. in /Users/jaykersten/Local Sites/bielocal/app/public/wp-content/mu-plugins/redis-cache-pro/src/Connectors/PhpRedisConnector.php on line 40

Replication

When we import from an existing site to start working local.

System Details

  • Which version of Local is being used?
    Latest

  • What Operating System (OS) and OS version is being used?
    Latest Mac OS On macbook pro 16 M1Max

  • Attach the Local Log. See this Help Doc for instructions on how to do so:

Security Reminder

Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

I had the same problem, i changed the name of mu-plugins in wp-content before exporting the web site with «All in one migration» WordPress plugin. I guess it would work with other cloning extensions. The key here is to turn off the plug-in before the exportation. Ounce the exportation is done, reactivate the mu-plugins in the web site on cloud ways.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.