blizo
Forum Replies Created
-
Many thanks @bisratlearn. Have saved us a lot of time!!
Hi @sharp1331
I downloaded the v8.1.1. from here:
https://developer.woocommerce.com/releases/I uploaded it to a temp folder inside the plugins folder. I then deleted the v8.2.0 woocommerce folder in plugins and renamed the temp folder to woocommerce.
I then deactivated auto updates on the woocommerce plugin so the new version doesn’t replace the old.
Hope that helps.
If you need any more info just ask.
I restored to the previous version of Woocommerce v8.1.1 and it fixed it.
- This reply was modified 2 years, 7 months ago by blizo.
Hi @giuse I am using this plugin for PHP:
https://en-gb.ww.wp.xz.cn/plugins/insert-php-code-snippet/I have added the code for a login form via the insert PHP plugin and added that PHP shortcode into the Content No Cache plugin.
The login form loads on the frontend and when I login the browser gets stuck on a white page with this URL:
example.com/wp-admin/admin-ajax.php?action=eos_dyn_get_contentDo you know why and any idea how to fix this?
After logging in the page should load but it’s getting stuck.
Logging in works using the form because when I return to the website the logged in menu loads.
- This reply was modified 2 years, 9 months ago by blizo.
Hi @tillkruess
Thanks for the tip. I wasn’t aware of New Relic.. At a quick glance some of the features look similar to DigitalOceans native insights?
I’ve attached DOs Redis insights from today. Does anything look critical?
The spike on the CPU usage at 11am was when the site crashed. How come the spike hasn’t gone down since? The cache is fuller?
None of the stats are at 100% which would suggest Redis isn’t failing?

- This reply was modified 2 years, 10 months ago by blizo.
How can I tell if Redis is helping or hindering this website?
It’s a Woocommerce site with about 500 products.
Hi @tillkruess
Thanks for the reply. I have tried what you recommended and the site still froze. There were 2 admins working on the backend when it happened.
I couldn’t even connect via SSH. I just had to wait for server to become responsive again.
I found this thread which describes the same problem with oom-killer in the syslog file and possible solutions for it:
https://serverfault.com/questions/344525/php-fpm-invokes-oom-killerI’ve tried the first recommendation by reducing ‘www.config’ settings. Here’s how it looks:
pm.max_children = 100
pm.start_servers = 25
pm.min_spare_servers = 25
pm.max_spare_servers = 40
pm.max_requests = 300The second recommendation I haven’t tried but if the server crashes again I might have to!
The Redis database side of things makes it more complicated for me to understand what to do next.
Would resizing the Droplet with more RAM fix this? Or would the Redis db also need more RAM?
I see there is a paid version of this plugin. Would that be a priority or hardware is the next best thing to try?
I also spotted this Redis warning in the syslog, is this anything to be concerned about?
Aug 8 14:39:07 project systemd[1]: Starting Clean php session files…
Aug 8 14:39:07 project sessionclean[1277008]: PHP Warning: Module "redis" is already loaded in Unknown on line 0
Aug 8 14:39:07 project systemd[1]: phpsessionclean.service: Deactivated successfully.
Aug 8 14:39:07 project systemd[1]: Finished Clean php session files.Thanks for your help. I greatly appreciate anything you can recommend.
Also here’s the server graphs for today.. The spike is when it crashed.





Hi @boozebrorsan I updated to version 3.0.6. and it now does the same error but only if there’s invalid fields. To replicate:
- Add item to cart
- Go to checkout
- Add normal billing details
- Use phone number: 5587
- Click “Place order”
- Klarna pop up shows this message “There has been an error with your address.. Please check fields: Phone number” (screenshot: https://i.ibb.co/rkY5r3D/pne.jpg)
- Enter a valid phone number
- Click “Place Order”
- Woo error message “Checkout error”
- Refresh checkout and this dev console error message shows “caught InvalidClientTokenError: The client token is invalid. Make sure it has not been tampered with in any way.”
When I try replicating this on the old plugin this Woo error message shows before the Klarna popup
Bad value: shipping_address.phone, billing_address.phone
And when I enter a valid phone number the Klarna checkout works.
bump….