Daan Kortenbach

@deliciousbrains thank you for providing a possible solution. I’ll put it in a file in mu-plugins so I can remove it easily later when the issue is fixed in a plugin update.

And I noticed the warnings as I viewed server error.log in realtime with tail -f /path/to/error.log on a pre-production server with 40 active users. WP_DEBUG_DISPLAY is already false but I do keep a log running at all times for security reasons. Especially in this stage. Please don’t assume unknowledgeble users.

@dbisupport, come on… you’re dealing with experienced developers here.

@abitp, I’m not sure if support is from Delicious Brains or new owner WP Engine. Support are probably not engineers. Either way, advisement to disable visibility of problems is a problem of itself, I agree.

Warnings that point towards something trying to get credentials outside docroot get special attention. Doesn’t matter if it’s just a warning.

I appreciate the effort but given the topic the debug explanation may be a bit out of touch. Thanks though, all I needed to know is that your team is on it.

 * - use_aws_shared_config_files: (bool, default=bool(true)) Set to false to
 *   disable checking for shared config file in '~/.aws/config' and
 *   '~/.aws/credentials'.  This will override the AWS_CONFIG_FILE
 *   environment variable.

Additional log:

2023/07/20 13:27:56 [error] 1126249#1126249: *4843 FastCGI sent in stderr: “PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/home/{user}/.aws/config) is not within the allowed path(s): (/home/{user}/.composer:/home/{user}/web/{domain}/public_html:/home/{user}/web/{domain}/private:/home/{user}/web/{domain}/public_shtml:/home/{user}/tmp:/tmp:/var/www/html:/bin:/usr/bin:/usr/local/bin:/usr/share:/opt) in /home/{user}/web/{domain}/public_html/wp-content/plugins/wp-ses/vendor/Aws3/Aws/DefaultsMode/ConfigurationProvider.php on line 126” while reading response header from upstream, client: {ip}, server: {domain}, request: “POST /wp-admin/admin-ajax.php HTTP/1.1”, upstream: “fastcgi://unix:/run/php/php8.1-fpm-{domain}.sock:”, host: “{domain}”

Same problem. But I do not agree to allowing read capabilities outside the document root. The open_basedir restriction is doing what it is supposed to do.

The issue is with a vendor library that takes a bit too much freedoms. The offender is:

/wp-ses/vendor/Aws3/Aws/DefaultsMode/ConfigurationProvider.php on line 126″

Please fix.

That is unfortunate but thank you for clarifying.

This can happen when another redirect is already in place. Please check.

Thank you for picking this up.

The filter is expecting a boolean.

Hi Carasmo,

Are you using it in combination with Ultimate Member? That could be the cause of the redirect loop.
My plugin is not meant to be used with other plugins and is mainly aimed at developers or websites that need to be shut off from the general public (like sites in development / staging sites).

I’d be happy to help, contact me through my website to get my email address.

My debugging tools appreciate your update ??