alexlii1971 Guess there is no difference, once the page is cached the PHP is bypassed and a HTML is severed so I guess that there is no real difference. But I have not benchmarked it. So if you do not use WP Rocket redis might be just fine. With WP Rocket you have a few more options of handling your cache, when to clean it, what to clean at what point etc. With redis the Nginx-Helper-Plugin is a bit more limited even though I guess you might be able to add some code to achieve what you want.

      Hello Lens

      Thanks for reply.

      Actually, I did not touched wp Rocket before, as for as I know it is a paid plugin, and did not find an free version when I searched on Wordpress.

      it would be great if like share a screenshot of Wp-rocket here.

      Thanks

        4 months later

        Thanks to @Lens for creating this topic, otherwise I wouldn't have figured it out. This is a serious issue with WordOps's default WP Rocket configuration that it doesn't work well with WoCommerce installations.

        There is no issue for the logged in users but suppose a Guest is browsing the site and he clicks "Add to Cart", the page will display 405 not allowed error page.

        As mentioned by OP, the workaround is using Satellite NGINX Configuration which is pretty easy to do. I hope the master @VirtuBox will do the needful in the upcoming update 🙂

          12 days later

          nsgoyat
          hello friend how are you an inquiry
          open correct this error 405
          I am with this same problem without being able to solve it
          if you have any help like getting out of this problem it is appreciated.

            6 days later

            nsgoyat There is no issue for the logged in users but suppose a Guest is browsing the site and he clicks "Add to Cart", the page will display 405 not allowed error page.

            So, Wp-rocket is not compatible with Woocommerce please?

            Thanks

                alexlii1971 WordOps's --wprocket configuration isn't compatible with Woocommerce.

                  5 months later

                  Also just had a 405 issue with a site using WP Rocket - but NOT a WooCommerce issue, this was giving a 405 error and blocking logging in to the WP Admin area (login page loads but 405 on submitting).
                  This was also resolved using the Rocket Nginx config as above. The site was using a hidden login page so I suspect that may have been the issue, as this config bypasses caching for all Post requests. Not digging in to it further as we'll probably ditch WP Rocket anyway.

                  8 months later
                  22 days later

                  How is this still an issue? This seems like a major, major bug.

                    bennettwebgroup WordOps hasn't received any major updates for more than a year. The leader developer @VirtuBox is unable to get some free time for the project.

                    For the time being, you can use Rocket NGINX Configuration as mentioned by the OP.

                      3 years later

                      Well my friends... After 4.5 years, the issue still persists!

                      I'm using --wprocket along with Perfmatters with changing login URL to something else, so it's not the normal wp-admin login URL. After i hit LOGIN button, the 405 Not Allowed appeared.

                      I know i just can use the Satellite Nginx config, but yeah, i just need to tell the devs that the problem still exist till now. Thanks.

                      405 Not Allowed

                        febryanvaldo

                        Well my friends... After 4.5 years, the issue still persists!

                        I'm using --wprocket along with Perfmatters with changing login URL to something else, so it's not the normal wp-admin login URL. After i hit LOGIN button, the 405 Not Allowed appeared.

                        It's not the same issue though. You're changing the login url which is non-standard WordPress behaviour.

                        There's 3 ways round it: 1. don't change the login url, 2. use the custom Rocket NGINX config as you said (takes 2 minutes to set up), or 3. don't use WP Rocket (Nginx FastCGI does the same thing natively, add a couple of extra plugins if you want things like minifiy or database optimization etc).

                          If you try to POST to a static page, Nginx will return a 405. That's okay; it's expected.

                          To solve the issue, you must ensure WP-Rocket does not create a static page for your custom login page. I don't know how you do it, but a configuration must be somewhere.

                          So, it's not a WordOps problem (and not WP-Rocket, either, I guess). There's nothing for WO to solve.

                          Hosted by VirtuBox