Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter evilned

    (@evilned)

    My hosting company increased the resources. I activated the plugin and it is loading now.

    Thread Starter evilned

    (@evilned)

    I have put in the request. I don’t know if they can or will do this, but if they do, I’ll try activating Jetpack again and see what happens. I’ll update this once I have more information.

    Thread Starter evilned

    (@evilned)

    I tried updating the plugin, (Successful), and then enabled it. Initially, all it showed was a 503 error. (I am way to familiar with those and their causes).

    I looked for the error logs and found that debug was set to false. After I restored the site, (Renaming the jetpack folder), and confirming it was disabled, I went into the config file and activated debug. Then I tried enabling jetpack again. This is the error that came up.

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /home/removed4security/public_html/blog2/wp-includes/functions.php on line 655

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 110592 bytes) in /home/removed4security/public_html/blog2/wp-includes/class-wpdb.php on line 2353

    I am not a developer and wouldn’t know what I was looking at in those locations in the two files.

    Thread Starter evilned

    (@evilned)

    I’m on a shared server and I don’t have as much access as I like. Here is what information I have available to me:

    Physical Memory Usage

    77.05 MB / 2 GB (3.76%)

    Number of Processes

    2 / 100 (2%)

    CPU Usage

    1 / 100 (1%)

    While I was troubleshooting, I recall the CPU was pegged at 100%

    Regarding the wp error log you mentioned, I don’t see it in the file structure. There is an error log but it doesn’t have any references in it to an out of memory error message in it.

    I do have an update to Jetpack, (It’s currently still installed but disabled), available, however, reading the notes, it’s not marked as tested with the current version.

    16.1.2 – 2026-08-20 Bug fixes

    • Newsletter: Fix a fatal error on the settings page caused by Gutenberg removing a private API that DataViews toggle and radio fields relied on.

    Should I try updating and activating the plugin and see what happens?

    • This reply was modified 5 days, 5 hours ago by evilned.
Viewing 4 replies - 1 through 4 (of 4 total)