Casino tournaments.REGISTER NOW GET FREE 888 PESOS REWARDS!

Multiple technical issue emails

wigglypoppins — Mon, 10 Mar 2025 15:00:08 +0000

Hello,

We’ve just had multiple successive technical issue emails in regards to a timeout error with this plugin, I’ve deactivated it for now until it’s resolved.

Site Details

WordPress version 6.7.2
Active theme: Craft Metropolis (version 2.0)
Current plugin: Meta pixel for WordPress (version 4.1.1)
PHP version 8.3.8

Error Details

Site Health cURL error 28

teepe — Sun, 19 Jan 2025 20:52:37 +0000

Hey there, I just set up my first wordpress website since ~12 years, on my windows machine, using the latest wordpress (6.7.1), nginx 1.25, MySql 8.0, and PHP 8.4. Nothing is on the website yet, except for the (default installed) akismet plugin and ‘Health Check & Troubleshooting‘. The latter tells me I get cURL timeouts on the API. The issue seems to be exactly as described in this previous post, except that I haven’t tried to add any endpoints via MySQL:

No firewall
No DNS interference
Am using SSL but works just fine, is also set in site settings
Also using nginx

Limit number of displayed galleries while creating a new album

SFrueh — Sun, 19 Jan 2025 10:36:23 +0000

Hello there,

our website is huge. We have tenthousands of photos in 2.621 galleries in 341 albums.
When I click on “add new album” the plugin needs a very long time to load the user interface because it displays ALL (!!!) 2.621 galleries. WordPress even warns me that the application is slowing down my website.

I have the fear that it will not finish loading and create a timeout when the number of my galleries increases further.

I absolutely don’t need it to display all 2.621 galleries when creating a new album. Displaying the last 50 galleries would be absolutely sufficiant.

Can I limit the number of galleries that are displayed while creating a new album?

Greetings,

SFrueh

Media Library not showing all images with “LOAD MORE”

swapot — Mon, 30 Dec 2024 19:51:58 +0000

I create my own month/year directories and upload about 250 images to each ‘month’ directory by SFTP (Filezilla). I then use the plugin ADD TO SERVER to have these added to the WP Media Library, the responsive sized image copies made, and image post pages created. This worked fine until I changed web hosting from shared hosting (Ngenx) to VPS (OpenLiteSpeed).

The issue I am having is that when I click “LOAD MORE” to show more than 80 images in one of these directories, it may add a few more images, and then I click it again and it may add some more – but doesn’t show all of the 250 or so images in the directory.

I am using a CDN (Cloudflare) and well as Redis Object Caching and LiteSpeed Caching, but I have tried this with all the caches purged and turned off and I still get the same behaivior.

This also is causing high loads on the server.

The new server is optimized, for wordpress/woocommerce with caching, etc.

I’m not sure how to troubleshoot something like this.

Any help appreciated.

time out tyring to activate plugin

MEMT-NETWORK — Thu, 28 Nov 2024 14:09:17 +0000

Hello,

I have a strong dedicated server.

WP limit 64 MB to max 265 MB

Memory limit is 512 MB

max_execution_time = 500

max_input_vars = 10000

Still i cant get the api page where you need to fill in your name and email. My site is connected with cloudflare, but after loading and loading i get a cloudflare page that it could not connect with the host.

While i can perfectly browse the website on mobile, an other computer in the meantime. What could cause this issue? I’m running on PHP 8.2

The current scan looks like it has failed

Mihai Papuc — Tue, 22 Oct 2024 22:53:17 +0000

I have been getting this timeout error while scanning this site for a couple of weeks now. I have looked into all the recommended materials and similar requests from this forum (eg. https://www.ads-software.com/support/topic/scan-engine-error-the-signature-is-invalid/). I reset the plugin (removing all its data and reinstalling it), I modified the max execution time / step to 12, and I enabled debugging.
Here are the last few lines from the debug log:

[Oct 22 15:38:15:1729636695.479332:4:info] Setting up scanRunning and starting scan
[Oct 22 15:38:15:1729636695.478234:4:info] Setting up error handling environment
[Oct 22 15:38:15:1729636695.476406:4:info] Requesting max memory
[Oct 22 15:38:15:1729636695.382269:4:info] Checking saved cronkey against cronkey param
[Oct 22 15:38:15:1729636695.380667:4:info] Checking cronkey: 8bff7771734c658af02e3c2de7e9ee1d (expecting 8bff7771734c658af02e3c2de7e9ee1d)
[Oct 22 15:38:15:1729636695.379479:4:info] Fetching stored cronkey for comparison.
[Oct 22 15:38:15:1729636695.376399:4:info] Verifying start request signature.
[Oct 22 15:38:15:1729636695.288254:4:info] Scan engine received request.
[Oct 22 15:38:05:1729636685.483775:4:info] Scan process ended after forking.
[Oct 22 15:38:04:1729636684.385128:4:info] Starting cron with normal ajax at URL https://site.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=8bff7771734c658af02e3c2de7e9ee1d&signature=109030b1a828633236222cc36a21601f3262bda0303552c8c813bc5528acde93
[Oct 22 15:38:04:1729636684.382247:4:info] Cached result for scan start test: true
[Oct 22 15:38:04:1729636684.381415:4:info] getMaxExecutionTime() returning config value: 12
[Oct 22 15:38:04:1729636684.380584:4:info] Got value from wf config maxExecutionTime: 12
[Oct 22 15:38:04:1729636684.293910:4:info] Calling startScan(true)
[Oct 22 15:38:02:1729636682.201197:4:info] Entered fork()
[Oct 22 15:38:02:1729636682.183762:4:info] Forking during malware scan (1875) to ensure continuity.

During the test scan, I also enabled WP_DEBUG, but I did not get any relevant error in the debug log either.

I am also sending the report by email to wftest at WF, mentioning my forum username in the report.

Please let me know what other steps I could try to solve this problem.

Session expired error on Order Received page

wpusr1 — Mon, 07 Oct 2024 17:12:21 +0000

Hi,

On my WordPress site using Stripe, (using test mode)after the checkout, I get the “Sorry, your session has expired. Return to shop” message. I dont see the Order placed message though I can see the order placed in Woocommerce-> Orders

I tried with the Storefront theme and I could see the same behaviour.

Please see the Woocommerce Reports


WordPress Environment

WordPress address (URL): https://mysite.com
Site address (URL): https://mysite.com
WC Version: 9.3.3
Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.
Action Scheduler Version: ✔ 3.8.1
Log Directory Writable: ✔
WP Version: 6.6.2
WP Multisite: –
WP Memory Limit: 512 MB
WP Debug Mode: –
WP Cron: ✔
Language: en_US
External object cache: – Server Environment

Server Info: LiteSpeed
PHP Version: 8.2.23
PHP Post Max Size: 2 GB
PHP Time Limit: 600
PHP Max Input Vars: 16384
cURL Version: 7.87.0
OpenSSL/1.1.1w

SUHOSIN Installed: –
MySQL Version: 8.0.39
Max Upload Size: 1 GB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ❌ Your server does not have the SoapClient class enabled - some gateway plugins which use SOAP may not work as expected.
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔ Database

WC Database Version: 9.3.3
WC Database Prefix: wp_
Total Database Size: 94.44MB
Database Data Size: 88.54MB
Database Index Size: 5.90MB
wp_woocommerce_sessions: Data: 0.19MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_actions: Data: 0.08MB + Index: 0.11MB + Engine InnoDB
wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_logs: Data: 0.06MB + Index: 0.03MB + Engine InnoDB
wp_bookly_appointments: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_categories: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_customer_appointments: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
wp_bookly_customers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_email_log: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_forms: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_gift_card_type_services: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_gift_card_type_staff: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_gift_card_types: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_gift_cards: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
wp_bookly_holidays: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_bookly_log: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_mailing_campaigns: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_bookly_mailing_list_recipients: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_bookly_mailing_lists: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_mailing_queue: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_news: Data: 0.08MB + Index: 0.00MB + Engine InnoDB
wp_bookly_notifications: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_notifications_queue: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_orders: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_payments: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_bookly_schedule_item_breaks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_bookly_sent_notifications: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_series: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_service_extras: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
wp_bookly_services: Data: 0.06MB + Index: 0.02MB + Engine InnoDB
wp_bookly_sessions: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_shop: Data: 0.06MB + Index: 0.00MB + Engine InnoDB
wp_bookly_staff: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_bookly_staff_categories: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_staff_preference_orders: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_staff_schedule_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_bookly_staff_services: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_stats: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_bookly_sub_services: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_bookly_tags: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_comments: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wp_duplicator_packages: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
wp_e_events: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_giftvouchers_activity: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_giftvouchers_list: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_giftvouchers_setting: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_giftvouchers_template: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_litespeed_url: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_litespeed_url_file: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
wp_options: Data: 6.14MB + Index: 0.14MB + Engine InnoDB
wp_postmeta: Data: 65.52MB + Index: 3.03MB + Engine InnoDB
wp_posts: Data: 14.52MB + Index: 0.38MB + Engine InnoDB
wp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wc_admin_note_actions: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
wp_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB
wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB
wp_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_product_meta_lookup: Data: 0.02MB + Index: 0.11MB + Engine InnoDB
wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB Post Type Counts

attachment: 203
cartflows_flow: 1
cartflows_step: 2
custom_css: 2
customize_changeset: 36
elementor_library: 3
nav_menu_item: 52
page: 39
post: 2
product: 46
product_variation: 5
revision: 1449
shop_order: 6
wp_global_styles: 3
wp_navigation: 1
wpcf7_contact_form: 2
wpgv_voucher_product: 135 Security

Secure connection (HTTPS): ✔
Hide errors from visitors: ✔ Active Plugins (19)

Astra Pro: by Brainstorm Force – 4.8.3
Premium Starter Templates: by Brainstorm Force – 4.3.9
Bookly Custom Fields (Add-on): by Nota-Info – 4.4
Bookly Pro (Add-on): by Nota-Info – 8.2
Bookly Service Extras (Add-on): by Bookly – 5.8
Bookly Stripe (Add-on): by Nota-Info – 4.7
Bookly: by Nota-Info – 24.0
Classic Widgets: by WordPress Contributors – 0.3
Contact Form 7: by Takayuki Miyoshi – 5.9.8
Duplicate Page: by mndpsingh287 – 4.5.4
Duplicator: by Duplicator – 1.5.11
Duplicator: by Duplicator – 1.5.11
Elementor: by Elementor.com – 3.24.5
Flexible Shipping: by Octolize – 4.25.8
Gift Cards (Gift Vouchers and Packages) (WooCommerce Supported): by codemenschen – 4.4.4
LiteSpeed Cache: by LiteSpeed Technologies – 6.5.1
Ultimate Addons for Elementor: by Brainstorm Force – 1.36.36
WooCommerce Stripe Gateway: by WooCommerce – 8.7.0
WooCommerce: by Automattic – 9.3.3 Inactive Plugins (2)

CartFlows: by CartFlows Inc – 2.0.9
Checkout Plugins - Stripe for WooCommerce: by Checkout Plugins – 1.10.0 Settings

Legacy API Enabled: –
Force SSL: –
Currency: GBP (￡)
Currency Position: left
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 days
Level threshold: –
Log directory size: 202 KB WC Pages

Shop base: #1445 - /shop/
Cart: #1446 - /cart/ - Contains the [woocommerce_cart] shortcode
Checkout: #1447 - /checkout/ - Contains the [woocommerce_checkout] shortcode
My account: #9 - /my-account/
Terms and conditions: #3214 - /terms-conditions/ Theme

Name: Child
Version: 1.0.0
Author URL: 
Child Theme: ✔
Parent Theme Name: Astra
Parent Theme Version: 4.8.3
Parent Theme Author URL: https://wpastra.com/about/?utm_source=theme_preview&utm_medium=author_link&utm_campaign=astra_theme
WooCommerce Support: ✔ Templates

Overrides: – 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
pattern-toolkit-full-composability
product-custom-fields
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
printful
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
product-pre-publish-modal
settings
async-product-editor-category-field
product-editor-template-system
blueprint
reactify-classic-payments-settings

Daily Cron: ✔ Next scheduled: 2024-10-08 11:17:15 +00:00
Options: ✔
Notes: 71
Onboarding: skipped Action Scheduler

Complete: 140
Oldest: 2024-09-08 16:42:25 +0000
Newest: 2024-10-07 16:12:51 +0000

Failed: 20
Oldest: 2024-07-27 11:17:10 +0000
Newest: 2024-10-07 15:10:28 +0000

Pending: 5
Oldest: 2024-10-07 17:12:51 +0000
Newest: 2024-11-02 15:08:03 +0000 Status report information

Generated at: 2024-10-07 16:56:24 +00:00

Kindly have a look.. any help toward rectifying this issue is highly appreciated.
Thanks a lot..

Bulk edit posts very slow performance

Bobot — Mon, 19 Aug 2024 18:58:44 +0000

I recently installed WP 6.6.1 on my shared host. All standard config, no plug ins. Imported about 100 posts from Blogger as a base. Attempts to do any bulk edit of posts in the Post menu is extremely slow and eventually leads to a Gateway 504 timeout. For example, this timeout occurs if I choose about 25 posts in bulk edit and simply apply the “published” option again to them. Changing any one bulk item post can take 5 seconds or more. Is this just a caveat on shared hosting? Please see detail from web host below.

My site health info shows this but not sure it is an issue:
Page cache is not detected but the server response time is OK Performance
Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.
Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:
cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.

Median server response time was 159 milliseconds. This is less than the recommended 600 milliseconds threshold.
No client caching response headers were detected.
A page cache plugin was not detected.

Here is some site info details:
Server architecture Linux 4.18.0-553.8.1.lve.el8.x86_64 x86_64
Web server Apache
PHP version 8.2.21 (Supports 64bit values)
PHP SAPI fpm-fcgi
PHP max input variables 6200
PHP time limit 90
PHP memory limit 768M
Max input time 60
Upload max filesize 512M
PHP post max size 512M
cURL version 7.61.1 OpenSSL/1.1.1k
Is SUHOSIN installed? No

Database
Extension mysqli
Server version 10.6.18-MariaDB-log
Client version mysqlnd 8.2.21

WordPress Constants
WP_MEMORY_LIMIT 256M
WP_MAX_MEMORY_LIMIT 768M

I reached out to my web host provider and they responded with this, suggesting I contact WordPress support:

Thank you for contacting Technical Support, I've taken a look at your WordPress install with the posts bulk update feature issue that you're having. 
I am able to replicate the issue, it appears to take longer than 90s to complete which is why it's getting the 503 error. 
The part that is a big a head scratcher the SQL query it runs to enumerate the posts it completes within the first second, MySQL is left untouched from that point forward, and when I do a bulk update in WordPress CLI for these posts but instead of 10, doing 100, it completes in under the 90s cut off. 
Even then when checking the load on the server when running the bulk change within WordPress is not taxing the CPU. 
Considering that you're using wordpress in nearly it's stock configuration I can only chalk this up to a coding error or bug within WordPress' software.

[stimul10@ecngx308 allthingsbobot.com]$ time wp post update $(seq 400 500) --post_status=publish
Success: Updated post 400.
Success: Updated post 401.
Success: Updated post 402.
Success: Updated post 403.
Success: Updated post 404.
Success: Updated post 405.
Success: Updated post 406.
Success: Updated post 407.
Success: Updated post 408.
Success: Updated post 409.
Success: Updated post 410.
Success: Updated post 411.
Success: Updated post 412.
Success: Updated post 413.
Success: Updated post 414.
Success: Updated post 415.
Success: Updated post 416.
Success: Updated post 417.
Success: Updated post 418.
Success: Updated post 419.
Success: Updated post 420.
Success: Updated post 421.
Success: Updated post 422.
Success: Updated post 423.
Success: Updated post 424.
Success: Updated post 425.
Success: Updated post 426.
Success: Updated post 427.
Success: Updated post 428.
Success: Updated post 429.
Success: Updated post 430.
Success: Updated post 431.
Success: Updated post 432.
Success: Updated post 433.
Success: Updated post 434.
Success: Updated post 435.
Success: Updated post 436.
Success: Updated post 437.
Success: Updated post 438.
Success: Updated post 439.
Success: Updated post 440.
Success: Updated post 441.
Success: Updated post 442.
Success: Updated post 443.
Success: Updated post 444.
Success: Updated post 445.
Success: Updated post 446.
Success: Updated post 447.
Success: Updated post 448.
Success: Updated post 449.
Success: Updated post 450.
Success: Updated post 451.
Success: Updated post 452.
Success: Updated post 453.
Success: Updated post 454.
Success: Updated post 455.
Success: Updated post 456.
Success: Updated post 457.
Success: Updated post 458.
Success: Updated post 459.
Success: Updated post 460.
Success: Updated post 461.
Success: Updated post 462.
Success: Updated post 463.
Success: Updated post 464.
Success: Updated post 465.
Success: Updated post 466.
Success: Updated post 467.
Success: Updated post 468.
Success: Updated post 469.
Success: Updated post 470.
Success: Updated post 471.
Success: Updated post 472.
Success: Updated post 473.
Success: Updated post 474.
Success: Updated post 475.
Success: Updated post 476.
Success: Updated post 477.
Success: Updated post 478.
Success: Updated post 479.
Success: Updated post 480.
Success: Updated post 481.
Success: Updated post 482.
Success: Updated post 483.
Success: Updated post 484.
Success: Updated post 485.
Success: Updated post 486.
Success: Updated post 487.
Success: Updated post 488.
Success: Updated post 489.
Success: Updated post 490.
Success: Updated post 491.
Success: Updated post 492.
Success: Updated post 493.
Success: Updated post 494.
Success: Updated post 495.
Success: Updated post 496.
Success: Updated post 497.
Success: Updated post 498.
Success: Updated post 499.
Success: Updated post 500.

real 1m43.933s
user 0m16.938s
sys 0m0.708s

You might want to reach out to the Developers of WordPress see what they suggest or at least them know that doing bulk edits is leading WordPress to lock up when attempting to do so, but that bulk edits work from CLI and when it happens there is no queries stuck in MySQL nor a high load from PHP.

Keeps Crashing Our Site

FAOU — Thu, 08 Aug 2024 18:48:57 +0000

I received a notification from Wordfence that it was not able to update rules or something, so I clicked on the link to try to update them. Wordfence keeps crashing our site. It does not appear to need an update, but with it on no one can get to our site without this error:

Request Timeout

This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase ‘Connection Timeout’.

Dropbox – Will Not Upload – Tried It All

itrss — Wed, 31 Jul 2024 19:17:00 +0000

made sure php has enough memory

disabled possible conflicting plugins

re authenticated dropbox

removed plugin, re-installed

tried lots of settings, tar

tried increasing timeout things.

i have tried so much – i dont know what to try yet.

log is useless

[31-Jul-2024 12:51:11]?Call to files/upload_session/append_v2 with 4 MB of data, with parameters {“cursor”:{“session_id”:”pid_upload_session:ABIIEpdTdHayAytwtuW2bbosBMFbvlzqMmxNbLV2Iej0lBQxyw”,”offset”:163577856}}
[31-Jul-2024 12:52:11]?Restart after 83 seconds.
[31-Jul-2024 12:52:12]?Uploading 4 MB of data
[31-Jul-2024 12:52:12]?Call to files/upload_session/append_v2 with 4 MB of data, with parameters {“cursor”:{“session_id”:”pid_upload_session:ABIIEpdTdHayAytwtuW2bbosBMFbvlzqMmxNbLV2Iej0lBQxyw”,”offset”:167772160}}
[31-Jul-2024 12:53:12]?/home1/iprsscom/public_html/cozzia/wp-content/plugins/backwpup/src/Infrastructure/Http/Client/WpHttpClient.php: Dropbox API: cURL error 28: Operation timed out after 60001 milliseconds with 0 bytes received
[31-Jul-2024 12:53:12]?Restart after 61 seconds.
[31-Jul-2024 12:53:13]?ERROR: Step aborted: too many attempts!
[31-Jul-2024 12:53:13]?ERROR: Job has ended with errors in 1595 seconds. You must resolve the errors for correct execution.