cjlim

Thx Kowsar. For clarity, after i de-activated and re-activated the plug-in, the issue of high load went away, which I can 100% attribute to apache not attempting to load a specific image that (I believe) didn’t exist prior to the re-activation.

Kowsar, i prefer not. you can let me know what you need to check and I can check for you?

Here’s my setup. 1 thing to clarify. I think /wp-content/uploads/wpo/ didn’t exist until I deactivate and re-activate the plugin. After re-activation, the directory wpo gets created.

• Server architecture: Linux 5.10.0-18-cloud-amd64 x86_64
• Web server: Apache
• PHP version: 8.1.10 (Supports 64bit values)
• PHP SAPI: fpm-fcgi
• PHP max input variables: 1000
• PHP time limit: 30
• PHP memory limit: 512M
• Max input time: 60
• Upload max filesize: 80M
• PHP post max size: 80M
• cURL version: 7.74.0 OpenSSL/1.1.1n

something is wrong with 3.2.17. After updating, my server went crazy high on load and on scrutiny, i see tons of GET requests from my own server but all with 404 status.

MYSERVERIP - - [10/Aug/2023:01:54:09 +0000] "GET /wp-content/uploads/wpo/images/XXXXX.png HTTP/1.1" 404 24197

Yet directory wpo does exist and the image it’s trying to fetch does exist as well.

a restart of apache didn’t resolve the issue, but apparently a deactivation, followed by reactivation of the plugin does. Hopefully it works for you as well.

again, Bitnami has documentation around how htaccess should be configured.

follow the instructions there. if you are not familiar with these server stuff, maybe get your webmaster to help?

what version of akismet plugin are you using?

yes and no.
yes: akismet did have an update where a new file (akismet-frontend.js) was introduced. prior, i think there’s only this file (akismet.js). and akismet did include this new file in the default htaccess file.

no: it really depends on how you setup bitnami htaccess. if you had setup pointing to the default akismet htaccess file, then you shouldn’t experience above issue (since the new file is automatically granted access).

But if you had copied and pasted the content in default htaccess file into bitnami’s htaccess file, then you will have 403 error with the new akismet plugin since the new file isn’t granted permission.

@nonasun
this has nothing to do with Akismet. it’s just the way bitnami is setup as far as htaccess config is concerned.

Bitnami has documentation around how htaccess should be configured.

@gurhansahin
I refer to bitnami documenation.

The .htaccess location for bitnami is
/opt/bitnami/apps/APPNAME/htdocs/.htaccess

for wordpress, APPNAME is likely wordpress.

however, I noticed if I enabled mod_pagespeed, i’ll still get a 403 error. not sure why and not sure how to configure for mod_pagespeed

Yes, i do see this.

<FilesMatch "^(form\.js|akismet\.js|akismet-frontend\.js|akismet\.css)$">
        <IfModule !mod_authz_core.c>
                Allow from all
        </IfModule>

        <IfModule mod_authz_core.c>
                Require all granted
        </IfModule>
</FilesMatch>

But i’m using Bitnami, so I think they do not honor .htaccess files in plugins directory. after adding akismet-frontend\.js to the correct .htaccess file, it’s now working. thx
i thi

Workaround works for me. Thanks.

Same here. Had downgraded to last version (2.16.0) and that solves the issue for now. when will this issue be fixed?

Hi, i’m not sure if this issue exists if permalinks disabled. I prefer not to touch anything on permalinks settings as it’s live site.

yes, that works! please include this change in your next release.

yes, it does now.
all because of the theme I was using.