Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • iTeamWP

    (@iteamwp)

    Hi BackWpup Team,

    This does not seem to be fixed in the latest release.

    Our websites updated to 5.2.1 are still receiving this error.

    Here’s an example log (I’ve removed anything that identifies the website as a precaution):

    [INFO] BackWPup 5.2.1; A project of WP Media
    [INFO] WordPress 6.8.1 on REMOVED
    [INFO] Log Level: Normal
    [INFO] BackWPup job: Database Backup
    [INFO] Logfile is: backwpup_log_0ccd6a_2025-05-01_05-00-09.html
    [INFO] Backup file is: 2025-05-01_05-00-09_ZRRJTED202_ANRJTEFE02_DBDUMP.zip
    [01-May-2025 05:00:09] 1. Try to backup database …
    [01-May-2025 05:00:10] Connected to database REMOVED on localhost
    [01-May-2025 05:00:13] Added database dump “REMOVED” with 2.64 MB to backup file list
    [01-May-2025 05:00:13] Database backup done!
    [01-May-2025 05:00:13] 1. Trying to generate a manifest file …
    [01-May-2025 05:00:13] Added manifest.json file with 3.57 KB to backup file list.
    [01-May-2025 05:00:13] 1. Trying to create backup archive …
    [01-May-2025 05:00:13] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [01-May-2025 05:00:13] Backup archive created.
    [01-May-2025 05:00:13] Archive size is 2.61 MB.
    [01-May-2025 05:00:13] 3 Files with 2.64 MB in Archive.
    [01-May-2025 05:00:13] 1. Try to send backup file to Dropbox …
    [01-May-2025 05:00:14] Authenticated with Dropbox of user: REMOVED
    [01-May-2025 05:00:14] Uploading to Dropbox …
    [01-May-2025 05:00:15] Backup transferred to /REMOVED/2025-05-01_05-00-09_ZRRJTED202_ANRJTEFE02_DBDUMP.zip
    [01-May-2025 05:00:16] One file deleted from Dropbox
    [01-May-2025 05:00:16] ERROR: Exception caught in TypeError: WPMedia\BackWPup\StorageProviders\Subscriber::update_backup_history(): Argument #1 ($key) must be of type string, null given, called in /home/REMOVED/public_html/wp-includes/class-wp-hook.php on line 324

    Hello,

    I didn’t want to open a new thread but we are seeing the same issue on around 20 client sites all running BackWPUp and also started after the recent 5.1.3 update.

    Thanks

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @rsouzaam

    Do you have a rough ETA on when this will be released?

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @laszloszalvak

    Many thanks for the prompt reply and such a detailed response. I think this is probably the best response I’ve ever had from a dev on these forums.

    Your debug code made us hit our memory limits so we couldn’t get the file to write, but I updated it to just print the image URL and it returns the following: /public_html/wp-content/uploads//2020/06/Room-10-web-optimized.jpg

    Reviewing the slider with this file I can see the image reference is: $upload$//2020/06/Room-10-web-optimized.jpg

    I’ll be honest we didn’t actually build this slider so I’m unclear if that reference is correct but seems like we’re trying to pull a local file here as an external resource? The actual image appears to be working within the slider it’s just causing this warning in the logs..

    Thanks

    • This reply was modified 1 year, 11 months ago by iTeamWP.
    • This reply was modified 1 year, 11 months ago by iTeamWP.
    Thread Starter iTeamWP

    (@iteamwp)

    Hi,

    We use the following cronjob for WP: /usr/local/bin/php ~/public_html/wp-cron.php >/dev/null 2>&1

    Thread Starter iTeamWP

    (@iteamwp)

    The only JS files we have with random strings are the LiteSpeed generated ones.

    If we disable JS minification then only 1 JS file is made (even with JS combine turned on).

    It looks like the LS minification is causing the files to multiply?

    Thanks.

    • This reply was modified 4 years, 3 months ago by iTeamWP.
    Thread Starter iTeamWP

    (@iteamwp)

    Hi @qtwrk ,

    This issue has become a lot more common recently on our clients websites.

    We’ve noticed that when the issue occurs the CSS is included in the CSS HTML source so that’s not the cause of the issue.

    What is the cause is the CSS that is being generated by LiteSpeed.

    E.g. Recently the “About Us” page on our website suffered this issue.

    During this time the following file wp-content/litespeed/cssjs/ded8b.css?37e3d was only 25.8kB missing the majority if not all of our styles.

    After flushing the LiteSpeed cache the page returned to normal and the stylesheet changed to /wp-content/litespeed/cssjs/8b0ee.css?af9cf with a size of 177kB.

    So LiteSpeed had generated a CSS file for the page with ~150kB of styles missing from the stylesheet.

    As mentioned previously this issue has become increasingly common so would appreciate any advice as when this issue occurs it’s basically makes the site completely unusable for any visitors until we flush the cache.

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @qtwrk

    We are struggling to find reliable replication steps as the issue seems to occur at random on certain pages after making changes (not necessarily on the same page).

    Where do we go from here? Are you suggesting disabling HTTP/2 Push might be a good idea?

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @qtwrk

    Many thanks for the reply.

    We use the following CSS settings:
    – CSS Minify => ON
    – CSS Combine => ON
    – CSS HTTP/2 Push => ON
    – Inline CSS Async Lib = > ON

    All other CSS settings are OFF.

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @qtwrk

    Thanks for the reply.

    I’ve checked our domain settings and these are configured correctly.

    We already have content security policy in place configured by our htaccess file.

    We don’t think mixed content is to blame here.

    As nothing shows in the logs for a LiteSpeed css request on this page we believe the LiteSpeed CSS was not included in the page source and thus the visitors browser didn’t request it.

    Any ideas if this is feasible? If an error occurs with the LiteSpeed CSS merging would the file potentially not be included in the header of the page?

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @qtwrk

    We’ve not been able to replicate this issue ourselves yet, we’ve only had reports from clients regarding this issue.

    If we look at our apache logs we can’t see any LiteSpeed css requests when the user visits the broken page.

    e.g. we would usually expect to see something like the following: GET /wp-content/litespeed/cssjs/d350b.css?4e062 HTTP/2 200

    But we do not see this when we review the logs after a user report the problem to us.

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @wp-livechat

    Do you have any ETA on when this issue will be resolved?

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi @wp-livechat

    Could you confirm if this issue was fixed in the recent 9.0.20 release?

    I can’t see anything in the release notes regarding this issue specifically.

    Thanks.

    Thread Starter iTeamWP

    (@iteamwp)

    Hi wfyann,

    Thanks for your detailed response.

    Could you please clarify a couple more queries relating to this issue for me?

    1. Once you’ve completed your official checks and identified the plugin as critical, do you send out another email alert?
    2. What sort of time frame can we expect from Wordfence from update release to detecting it as critical?

    Thanks in advance!

    Thread Starter iTeamWP

    (@iteamwp)

    Great, thanks a lot Daniel!

Viewing 15 replies - 1 through 15 (of 16 total)