I am the technical manager for the infrastructure at Turbocloud (turbocloud.com.br), and we are facing a problem with one of our servers. Requests made by the server https://br.yavin4846.com.br/, whose IP is 177.154.191.198, are being blocked by www.ads-software.com.
This block is directly impacting several more customers in our database, and we would like to request the release of the aforementioned IP so that we can resume normal service operations.
Thank you for your attention and I look forward to hearing from you as soon as possible.
Best regards,
Hugo Marinho Silva
Technical Manager – Turbocloud
I am writing to seek assistance regarding an issue we are experiencing with the Post Views Counter plugin on our website. Our server team has identified that the plugin is making frequent requests to Redis, which appears to be overloading the cache and causing performance issues, including occasional downtime. Below are some specific details regarding the errors encountered:
[Wed Sep 04 11:35:08.820303 2024] [proxy_fcgi:error] [pid 2606133:tid 127777716045504] [client 162.158.154.141:24232] AH01071: Got error 'PHP message: RedisException: socket error on read socket in /var/www/html/wp-content/object-cache.php:560
[Wed Sep 04 06:06:21.493693 2024] [proxy_fcgi:error] [pid 2925720:tid 127777370015424] [client 162.158.63.130:51030] AH01071: Got error 'PHP message: RedisException: read error on connection to /run/redis/redis-server.sock in /var/www/html/wp-content/object-cache.php:1986...Based on our analysis, it appears that the high volume of reads and writes to the Redis cache, particularly during peak usage times, is causing Redis to become overwhelmed. This issue seems to be exacerbated by the plugin’s behavior, which may be generating a burst of Redis operations, impacting the stability and performance of our website.
To address this issue, we would greatly appreciate your guidance on the following:
- Optimizing Redis Usage: Are there specific settings or recommendations within the Post Views Counter plugin to reduce the frequency of cache access or to batch/cache operations more efficiently?
- Configuration Adjustments: Are there specific Redis configurations or plugin settings that we can adjust to handle the high volume of requests without overwhelming the server?
- Best Practices: Any best practices for using the Post Views Counter with Redis caching that can help alleviate the load?
We appreciate any insights or adjustments you can suggest to optimize the plugin’s interaction with Redis, as maintaining the stability and performance of our website is critical.
Thank you for your prompt attention to this matter. Please let us know if you need any further information or access to logs to assist in diagnosing the issue.
Best regards,
Vimal Roy
Coin Edition
We are currently using the Redis Object Cache plugin on our WordPress website, a high-traffic multilingual news platform that primarily focuses on cryptocurrency and blockchain-related content. Our website has over 56,000 posts in total, available in 8 languages, and we publish 30-50 new articles daily. Our team of 20-30 users, including publishers from various regions, actively works on the website simultaneously—creating, updating, publishing, and translating content.
Recently, we have been encountering several persistent issues that are impacting our site’s performance, detailed below:
- Error Establishing Redis Connection: We frequently receive errors such as
RedisException: read error on connection to /run/redis/redis-server.sock. This typically occurs when clearing the cache for the first time each day, after periods of inactivity, or when creating new posts. Despite having ample resources available, Redis seems unable to handle the connections consistently. - Socket Errors and HTTP 500 Errors: We are experiencing repeated socket read failures and occasional HTTP 500 errors directly linked to Redis performance issues. These disruptions significantly affect our website’s availability and overall user experience.
- Plugin-Related Issues:
- WPML: Our website relies heavily on WPML for multilingual functionality, and we’ve noticed that Redis interactions frequently coincide with performance slowdowns when WPML is active.
- Yoast SEO: Essential for our SEO strategy, Yoast is also generating a high number of Redis requests, which could be contributing to the connection issues.
- Wordfence: Security is a priority for us, and Wordfence is critical. However, it appears to be interacting with Redis in a way that may be contributing to the overall load.
- Post Views Counter: We are currently evaluating whether this plugin is necessary, but it is also making frequent requests to Redis, adding to the load.
PFA :-
https://www.awesomescreenshot.com/image/50430705?key=30ccd35b8b9f97b73d55606783f2019b
https://www.awesomescreenshot.com/image/50430704?key=cba43d0b0718defbee585926508fb7e4
Given these challenges, we are seeking your expertise and guidance. Are there any known fixes, configurations, or optimizations within the Redis Object Cache plugin that could help mitigate these issues? Specifically, are there ways to reduce or optimize the load generated by these plugins or exclude certain requests to Redis?
If there are any previously discussed solutions or recommendations that you could direct us to, it would be greatly appreciated.
Thank you in advance for your assistance. We look forward to your insights on resolving these issues and enhancing the stability and performance of our Redis setup.
Best regards,
Vimal Roy
]]>Problem description: Loading the shop page takes very very long. You can actually watch parts appear and then disappear and re-appear again.
Analysis: I used Firefox Developer Tools and added/deleted blocks and found out that for each block multiple requests are sent to the woocommerce api. I’ll add them below. Using just the “all products” block, 3 or 4 requests are ok. But for each filter block I add, another 3 or so requests are added. This sums up.
I do understand that the filters are dynamic and thus have to access the api to find out which attributes to offer. But there must be a way to either reduce the number of requests or speed them up (maybe with caching?).
I took a look at your featured partners’ websites and noticed that I don’t see all those requests for them. So there must be a way.
I think it might be the same problem as described here, but there was no solution, the problem just disappeared … ? https://www.ads-software.com/support/topic/multiple-woocommerce-rest-api-calls/
These are the requests just to load the “all products” block. They seem redundant to me.
***/wp-json/wc/store/v1/products?orderby=date&order=desc&catalog_visibility=catalog&per_page=9&page=1&_locale=user
***/wp-json/wc/store/v1?_locale=user
***/wp-json/wc/store/v1/products?include=0&_locale=user
***/wp-json/wc/store/v1/products?_locale=userSystem Status Report
### WordPress Environment ###
WordPress address (URL): [Redacted]
Site address (URL): [Redacted]
WC Version: 9.1.4
Legacy REST API Package Version: Auf dieser Website ist das alte REST-API-Plugin nicht installiert.
Action Scheduler Version: ✔ 3.7.4
Log Directory Writable: ✔
WP Version: ❌ 6.5.5 - Es ist eine neuere Version von WordPress verfügbar (6.6.1)
WP Multisite: –
WP Memory Limit: 512 MB
WP Debug Mode: –
WP Cron: ✔
Language: de_DE
External object cache: –
### Server Environment ###
Server Info: Apache
PHP Version: 8.3.9
PHP Post Max Size: 128 MB
PHP Time Limit: 180
PHP Max Input Vars: 4000
cURL Version: 7.64.0
OpenSSL/1.1.1n
SUHOSIN Installed: –
MySQL Version: 8.0.33
Max Upload Size: 128 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔
### Database ###
[REDACTED]
### Post Type Counts ###
attachment: 126
customize_changeset: 114
custom_css: 1
ml-slide: 52
ml-slider: 1
nav_menu_item: 27
page: 28
post: 18
product: 4
rcb-banner-link: 4
rcb-cookie: 1
revision: 1884
shop_order_placehold: 5
ufaq: 4
wpcf7_contact_form: 1
wpforms: 1
wp_block: 11
wp_global_styles: 3
wp_navigation: 6
wp_template: 3
wp_template_part: 6
### Security ###
Secure connection (HTTPS): ✔
Hide errors from visitors: ✔
### Active Plugins (13) ###
Koko Analytics: von ibericode – 1.3.10
Antispam Bee: von pluginkollektiv – 2.11.6
The SEO Framework: von The-SEO-Framework-Team – 5.0.6
Contact Form 7: von Takayuki Miyoshi – 5.9.8
EWWW Image Optimizer: von Exactly WWW – 7.8.0
MetaSlider: von MetaSlider – 3.90.1
Mollie-Zahlungen für WooCommerce: von Mollie – 7.5.5
Real Cookie Banner (Free): von devowl.io – 4.7.13
Trusted Shops Easy Integration for WooCommerce: von vendidero – 2.0.2
Spectra: von Brainstorm Force – 2.15.0
Ultimate FAQ Accordion Plugin: von Etoile Web Design – 2.2.14
Germanized für WooCommerce: von vendidero – 3.17.1
WooCommerce: von Automattic – 9.1.4
### Inactive Plugins (5) ###
Flexible Checkout Fields: von WP Desk – 4.1.8
MetaSlider Lightbox: von MetaSlider – 1.13.2
PDF Invoices & Packing Slips for WooCommerce: von WP Overnight – 3.8.6
Simple Social Buttons: von WPBrigade – 5.2.0
WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels: von WebToffee – 4.6.0
### Dropin Plugins () ###
maintenance.php: maintenance.php
### Settings ###
API Enabled: –
Force SSL: –
Currency: EUR (€)
Currency Position: right_space
Thousand Separator: .
Decimal Separator: ,
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)
Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)
Connected to WooCommerce.com: –
Enforce Approved Product Download Directories: ✔
HPOS feature enabled: ✔
Order datastore: Automattic\WooCommerce\Internal\DataStores\Orders\OrdersTableDataStore
HPOS data sync enabled: –
### Logging ###
Enabled: ✔
Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2
Retention period: 30 Tage
Level threshold: –
Log directory size: 166 kB
### WC Pages ###
Shop-Basis: #15 - /produkte/
Warenkorb: #1868 - /warenkorb/ - Contains the woocommerce/cart block
Kasse: #1869 - /kasse/ - Contains the woocommerce/checkout block
Mein Konto: #1870 - /mein-konto/
Allgemeine Gesch?ftsbedingungen: #1872 - /agb/
### Theme ###
Name: nk-fse-child
Version: (Update auf Version 0 ist verfügbar)
Author URL:
Child Theme: ✔
Parent Theme Name: Twenty Twenty-Four
Parent Theme Version: 1.1 – 1.2 ist verfügbar
Parent Theme Author URL: https://de.www.ads-software.com
WooCommerce Support: ❌ Nicht deklariert
### Templates ###
Overrides: ***/wp-content/plugins/woocommerce/templates/block-notices/error.php
***/wp-content/plugins/woocommerce/templates/block-notices/notice.php
***/wp-content/plugins/woocommerce/templates/block-notices/success.php
### Admin ###
Enabled Features: activity-panels
analytics
product-block-editor
coupons
core-profiler
customize-store
customer-effort-score-tracks
import-products-task
experimental-fashion-sample-products
shipping-smart-defaults
shipping-setting-tour
homescreen
marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
product-custom-fields
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page
launch-your-store
Disabled Features: experimental-blocks
minified-js
pattern-toolkit-full-composability
product-pre-publish-modal
printful
settings
async-product-editor-category-field
product-editor-template-system
Daily Cron: ✔ Next scheduled: 2024-06-17 09:25:58 +00:00
Options: ✔
Notes: 67
Onboarding: completed
### Action Scheduler ###
Abgeschlossen: 66
Oldest: 2024-05-17 04:56:01 +0000
Newest: 2024-06-16 10:46:18 +0000
Ausstehend: 18
Oldest: 2024-06-16 19:47:18 +0000
Newest: 2024-07-01 14:04:40 +0000
Fehlgeschlagen: 5
Oldest: 2024-05-20 12:21:11 +0000
Newest: 2024-06-13 20:34:47 +0000
### Status report information ###
Generated at: 2024-08-02 09:58:12 +00:00My site has become extremely slow recently and after examining server logs I can see a huge amount of requests by WooCommerce for block CSS files. EG:
GET /wp-content/plugins/woocommerce/assets/client/blocks/reviews-by-category.css HTTP/1.0 200 10810
There are around a dozen different requests every second for around 4 seconds in periodic bursts.
Is this intended? I don’t use blocks (I’m using Avada page builder) and I’d like to disable this if possible.
Thanks.
]]>
Hi, we are having a problem with the plugin.
We have tons of Stripe requests being fired on pages like the Product page which shouldn’t have them.
It may be due to Stripe fraud features however as we do not have fraud at all, we do not need these requests.
It’s impacting the speed of the product page and speed score which as you know is quite important when it comes to SEO etc..
Is there any way to stop these requests from being fired using a filter in the plugin or by adding some code to the theme?
Thanks
]]>we have the same problem as described in the thread here:
https://www.ads-software.com/support/topic/excessive-ajax-use-on-site/
Sadly we don’t see the option to disable AJAX requests entirely in your plugin. It calles over 100 times per minute per user so the server breaks down.
So where exactly is the option to disable this or to fix this problem?
Kind regards,
Jan
We have noticed a significant increase in requests to the following path on a page using Learnpress: /?lp_test_wp_remote=1. After investigating the source code, we found references to “lp_test_wp_remote” in the following files:
wp-content/plugins/learnpress/inc/admin/class-lp-admin-notice.php
wp-content/plugins/learnpress/learnpress.php
We would like to know if this behavior is normal and if there is any way to stop or limit these requests. Additionally, we would appreciate guidance on whether it is necessary to keep this functionality active.
Thanks. Best regards.
]]>I noticed that for every request made by a client to my site homepage, my server generates dns queries for woocommerce.com then connects to it using https before generating the response, thus adding unaccpetable delay (~1-4 seconds) and unnecessary traffic.
Debugging already made:
- Making sure that woocommerce tracking is not enabled
- Installing a fresh test environment
But the problem persists.
How to stop woocommerce querying and connecting to woocommerce.com?
]]>