AIOS – blocks Cron on WordPress

  • Resolved Artem

    (@danchik83)


    1 year, 6 months ago

    I faced the problem that Cron stopped working normally, or did not work at all.
    By method of exception, turned off plugins, and as it turned out with AIOS plugin turned off, Cron on WordPress began to work adequately.

    Question, how to add to the exceptions, the work of Cron from WordPress?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @danchik83

    What is error in PHP error log file?

    define( ‘WP_DEBUG’, true ); in wp-config.php ( have to change from false to true) and you can enable the error log. you can find the error_log file in the root of the wordpress or some hosting provider shows recent error logs in cpanel.

    Regards

    Thread Starter Artem

    (@danchik83)

    Hi @hjogiupdraftplus

    define( ‘WP_DEBUG’, true ); – I had it enabled, downloaded it for research…, but there are no records in the current month.

    error_log – I also downloaded a file on the most recent records… and there are lines:

    [27-Apr-2023 04:34:50 America/New_York] AIOS firewall error: Unable to determine the current context.
    [27-Apr-2023 08:34:50 UTC] Connection refused
    [14-May-2023 08:33:18 UTC] Connection refused
    [15-May-2023 04:35:33 America/New_York] AIOS firewall error: Unable to determine the current context.
    [16-May-2023 04:35:51 America/New_York] AIOS firewall error: Unable to determine the current context.

    What is interesting, this file had a volume of about 600 Mb!
    As I found out, there are a lot of duplicate strings of names:

    “Connection refused“

    I do not understand anything about it, if you need files for research, please specify your details for sending)

    P.S. By the way, got mail notifications from WordPress today (if it matters…) :
    Error Details

    An error of type E_ERROR was caused in line 294 of the file /***/***/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-filesystem-menu.php.
    Error message: Allowed memory size of 805306368 bytes exhausted (tried to allocate 33554440 bytes)

    • This reply was modified 1 year, 6 months ago by Artem.
    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @danchik83

    “Unable to determine the current context” is identified issue. Below copy of the plugin may resolve your issue.

    Please upload the zip as Add new plugin and replace it with existing AIOS plugin.

    https://gofile.io/d/m3tBPT

    This fix is going to be in the next release soon

    Thread Starter Artem

    (@danchik83)

    Hi @hjogiupdraftplus

    I replaced the plugin with your archive.
    But, unfortunately, the problem is not solved(

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @danchik83

    Means still the cronjob do not run ? Please cross check it is properly replaced with new zip code. you may try check the readme.txt at /wp-content/plugins/all-in-one-wp-security-and-firewall/readme.txt

    An error of type E_ERROR was caused in line 294 of the file

    public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/admin/wp-security-filesystem-menu.php.
    Error message: Allowed memory size of 805306368 bytes exhausted (tried to allocate 33554440 bytes

    Above seems memory issue Please increase memory limit

    It is for WP Security > Scanner > File change detection, If possible reduce scan time intervals so not large list of file change created.

    Regards

    Thread Starter Artem

    (@danchik83)

    Hi @hjogiupdraftplus,

    Yeah, that’s how cronjob doesn’t work(

    I did not understand what I was supposed to see there in the file “readme.txt”…
    I already had the latest version 5.1.8 installed. In your archive a similar version. I overwrote the current version to WP.
    That is, I updated the installation date of the plugin.

    Regarding the memory limit, the thing is that I have a limit on my hosting =1000 mb, and the average daily load of about 350mb
    Still, according to your recommendations changed in the scanner settings:
    It was, week 4.
    Now it’s 1 week

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @danchik83

    The readme.txt have in change log “FIX: Fix context class checks to support cli” that should be cross checked, If it is then you have updated with copy.

    /wp-content/plugins/all-in-one-wp-security-and-firewall/readme.txt

    https://snipboard.io/uvQsWO.jpg

    Ok, Please keep checking if still memory related error then you should ignore certain file changes. “wp-content/plugins” “wp-content/themes”and let me know if still the still the context error is logged in error_log.

    The cronjob not running might be issue other than these two also.

    Regards

    Thread Starter Artem

    (@danchik83)

    Hi?@hjogiupdraftplus,

    The problem was solved. Only by switching to another hosting.
    Apparently, there was still a problem with my hosting, earlier they said that from their side no problems.

    Thank you for your help.
    Have a nice day!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘AIOS – blocks Cron on WordPress’ is closed to new replies.

Tags