Smart Update fails: unable to correctly clone your website for further analysis

Follow

Comments

4 comments

  • Avatar
    Jorge Liauw

    It's true that Additional nginx directives prevent cloning of WordPress sites and thus the functionality of Smart Update. We are currently running Smart Update in a trial.

    Do you offer an other solution, workaround to make WordPress Smart Update working with Nginx directives enabled? We use the Nginx directives for HTTP Security headers and to block XMLRPC. So it's not an option to disable the directives during an update. Or do you have an script that will disable it temporary, run Smart Update and enable it?

    Looking forward!

     

    0
    Comment actions Permalink
  • Avatar
    Kenneth Thomsen

    There really should be an option to get around this. I cannot disable rewrite rules on a production website (which I guess is the point of smart update, that it actually clones the website, so I don't have to do it manually.)

    Please look into a fix for this. This feature is one of the most important features in WP Toolkit - and it should work with something as common as rewrites (Apache or NGINX... but in my case NGINX).

     

    1
    Comment actions Permalink
  • Avatar
    Alphamega

    There are NO rewrite rules in place and we still get this error.

    1
    Comment actions Permalink
  • Avatar
    Rogier Schoenmaker

    We removed all the rewrite rules that aren't required by Wordpress, and removed the nginx rules, but we still have the same issue with the first error message.

    Please expand this help page, or make the messages clearer.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request