Forum Replies Created

Viewing 15 replies - 1 through 15 (of 127 total)
  • Similar issue, it also won’t let me add an accordion object. I opened a bug report on it. https://github.com/elementor/elementor/issues/29220

    gmariani405

    (@gmariani405)

    it’s been two weeks and it was “in testing” like over a week ago. whats going on?

    Thread Starter gmariani405

    (@gmariani405)

    @wfmargaret I’ve requested my hosting vendor to take a look and see if they find anything. I’ve had them look in the past regarding any specific IPs and modsec which they did not find anything. I’m not hopeful but I figured i’d ask regardless. I’ll let you know what they say.

    also checking up on this… any update?

    Thread Starter gmariani405

    (@gmariani405)

    Sorry for the delayed reply, I don’t always have time to troubleshoot WordFence right away. I tested your recommendations on about 8 sites. Here were my results:

    Site 1: High Sensitivity. Changed to Standard Scan and it scanned without issue
    Site 2: Standard Scan. Scanned without issue
    Site 3: High Sensitivity. Changed to Standard Scan and it scanned without issue
    Site 4: High Sensitivity. Changed to Standard Scan and it failed. Changed max scan time from 0 -> 20, it failed.

    Site 5: High Sensitivity. Changed to Standard Scan and it failed. Changed max scan time from 0 -> 20, it failed.
    Site 6: High Sensitivity. Changed to Standard Scan and it scanned without issue
    Site 7: Standard Scan. Failed. Changed max scan time from 0 -> 20, it failed.
    Site 8: Standard Scan. Scanned without issue
    Site 9: High Sensitivity. Changed to Standard Scan and it scanned without issue

    Regarding Site 4, i sent the activity log, and diagnostic report and sent an email with the server logs to the wftest@ address.

    Thread Starter gmariani405

    (@gmariani405)

    As a side note, I was working on another client site and saw this in the error log. Same host (nexcess), so this error might be related?

    [18-Sep-2024 09:04:58 UTC] Cron unschedule event error for hook: wordfence_start_scheduled_scan, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":false,"args":[1726370400]}

    Thread Starter gmariani405

    (@gmariani405)

    @wfmargaret

    Site 1: Succeeded, submitted diagnostics report and activity log (thorn…)
    Site 2: Succeeded, submitted diagnostics report and activity log (bade…)
    Site 3: Failed, submitted diagnostics report and activity log (mari…)
    Site 4: Failed, submitted diagnostics report and activity log (mark…)

    Hope this helps!

    Thread Starter gmariani405

    (@gmariani405)

    Tried on another site (Site 4) with 25 cron jobs pending, first scan failed. I manually triggered the cron and cleared out the pending cron jobs and it continued to fail on the second scan.

    Site 3 i tried running it a few more times and it succeeded each time. Again I did nothing to change it since yesterday. One thing to note is the peak memory yesterday was almost 145MB when running. Now it barely cracks 50MB.

    [Sep 10 10:42:19] Wordfence used 32.7 MB of memory for scan. Server peak memory usage was: 50.7 MB
    [Sep 10 10:42:19] Scan Complete. Scanned 20306 files, 21 plugins, 2 themes, 9 posts, 0 comments and 21331 URLs in 7 minutes 27 seconds.

    [Sep 10 11:03:08] Wordfence used 30.06 MB of memory for scan. Server peak memory usage was: 50.06 MB
    [Sep 10 11:03:08] Scan Complete. Scanned 20299 files, 20 plugins, 2 themes, 9 posts, 0 comments and 24719 URLs in 8 minutes 15 seconds.

    [Sep 10 11:31:14] Wordfence used 36.71 MB of memory for scan. Server peak memory usage was: 52.71 MB
    [Sep 10 11:31:14] Scan Complete. Scanned 18071 files, 20 plugins, 2 themes, 32 posts, 0 comments and 13412 URLs in 6 minutes 10 seconds.

    @wfmargaret Do you want me to send an activity log on Site 4 where it’s still failing?

    Thread Starter gmariani405

    (@gmariani405)

    I went to try again on Site 3, and when i looked it only have 6 cron jobcs backed up. I ran the scan and it worked fine. I updated plugins, ran the scan again it worked fine. I looked at the backed up cron jobs and it was empty. I had changed nothing since my tests yesterday. So maybe the backed up cron jobs may be a factor here. I’ll investigate some more.

    Thread Starter gmariani405

    (@gmariani405)

    @wfmargaret So on Site 3 I ran a few different variations and they all failed after that one successful run.

    256M, no IPv4, 600 timeout: worked once, failed second attempt
    256M, only IPv4, 600 timeout: failed
    256M, only IPv4, 60 timeout: failed
    40M, only IPv4, 600 timeout: failed
    40M, only IPv4, 60 timeout: failed
    40M, no IPv4, 600 timeout: failed
    40M, no IPv4, 60 timeout: didn’t test

    I sent an email of the diagnostic data for the last failed run where i had all three suggestions enabled. There are two things I wanted to note though:

    1. There are 46 cron jobs overdue, so maybe this backlog is affecting things?
    2. The crons are handled via cron jobs which are set to run every 5minutes:
      */5 * * * * /usr/sbin/relax php -f /chroot/home/USER/DOMAIN.nxcli.io/html/wp-cron.php (Every 5 Minutes)

    Let me know if any of this helps, thanks!

    Thread Starter gmariani405

    (@gmariani405)

    @wfmargaret So I wanted to test this a bit methodically to see what worked because what you suggested doesn’t make too much sense but I guess that really depends on how Wordfence works (which maybe you can explain). I tried on three sites i knew were failing to run reliably.

    Site 1: Changed it to just use IPv4 only and it worked.
    [Sep 09 14:01:25] Wordfence used 34.71 MB of memory for scan. Server peak memory usage was: 52.71 MB
    [Sep 09 14:01:25] Scan Complete. Scanned 18070 files, 20 plugins, 2 themes, 32 posts, 0 comments and 13404 URLs in 6 minutes 13 seconds.

    Site 2: Changed it to just use IPv4 only and it worked.
    [Sep 09 14:08:16] Wordfence used 32.32 MB of memory for scan. Server peak memory usage was: 138.32 MB
    [Sep 09 14:08:16] Scan Complete. Scanned 19903 files, 17 plugins, 2 themes, 43 posts, 0 comments and 24211 URLs in 5 minutes 39 seconds.

    Site 3: Changed it to just use IPv4 only and it still failed. Bumped up WP_MEMORY_LIMIT to 64M, still failed. Bumped it up to 256M, and it worked.
    [Sep 09 14:31:23] Wordfence used 32.7 MB of memory for scan. Server peak memory usage was: 144.7 MB
    [Sep 09 14:31:23] Scan Complete. Scanned 20305 files, 21 plugins, 2 themes, 9 posts, 0 comments and 21327 URLs in 7 minutes 23 seconds.

    Now, WP_MEMORY_LIMIT is per script, for front-end users. So if many scripts are running at once, they have the possibility to use up more ram than is actually available. So this SHOULD ideally be kept low as it would be cumulative. The WP_MAX_MEMORY_LIMIT constant specifically defines the maximum memory limit available when in the administration back-end. The default is 256M (256 megabytes of memory) or the original memory_limit php.ini value if this is higher.

    So in theory, shouldn’t it have already been running at 256M? The WP_MAX_MEMORY_LIMIT is set to 2048M already. All three sites report Wordfence using less than 40M. On the sites I didn’t increase memory, it used well above 40M which would indicate to me that they weren’t limited to 40M.

    I’m going to test changing the max_execution_time next and see if that’s a factor. Can you explain why WP_MEMORY_LIMIT would be a factor if this is running on the back-end in the meantime?

    Thread Starter gmariani405

    (@gmariani405)

    @wfmargaret I’ve gone ahead and done as you requested. Both emails should have been sent. Let me know what the next steps are (if any). Thanks!

    Was going to report the same issue. But the conflict is due to the fact that Easy Appointments and The Events Calendar Pro both use the di52 library ( https://github.com/lucatume/di52 ). They must be different versions or something. This is the error in question:

    PHP Fatal error: Uncaught TypeError: TEC\Common\lucatume\DI52\ServiceProvider::__construct(): Argument #1 ($container) must be of type TEC\Common\lucatume\DI52\Container, tad_DI52_Container given, called in /chroot/home/USERNAME/WEBSITE/html/wp-content/plugins/easy-appointments/vendor/lucatume/di52/src/tad/DI52/Container.php on line 484 and defined in /chroot/home/USERNAME/WEBSITE/html/wp-content/plugins/the-events-calendar/common/vendor/vendor-prefixed/lucatume/di52/src/ServiceProvider.php:37

    For what it’s worth it looks like it’s been resolved for me.

    gmariani405

    (@gmariani405)

    I’ll know for sure tomorrow. I had a bunch still email me today, which is when i went in and checked them using your CLI commands to confirm. I went through about 15 that still had erroneous settings. After I logged in, about 7 of them corrected themselves automatically. But as I said, I’ll know for sure tomorrow if i get any more emails or not.

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