PHP error protocol error, got ‘E’ as reply-type byte

[AbZu2]

Am receiving an endless stream of of the same PHP error:  protocol error, got ‘E’ as reply-type byte

When I click on the Reset Last Modified Time in the PHP error log, the alert window does not disappear.

[AITpro Admin]

If you are using Redis Caching see this GitHub topic for possible solutions > https://github.com/phpredis/phpredis/issues/369

If you have the RankMath plugin see this RankMath help topic > https://support.rankmath.com/ticket/protocol-error-got-e-as-reply-type-byte/

If you have the LiteSpeed Cache plugin (aka LSCache) see this help topic > https://managingwp.io/2023/04/14/dealing-with-protocol-error-got-e-as-reply-type-byte-and-lscache-plugin-object-cache/

[AbZu2]

Thanks for the reply. Using LiteSpeed Cache. There was an error in the Object Cache port setting that was configured to 11211  (Memcached) instead of 6379 (Redis), using the latter. That eliminated the PHP error protocol error, got ‘E’ as reply-type byte, and was replaced by Connection refused. Decided to turn OFF Object Cache. Still, getting Connection refused ¿?

[AITpro Admin]

I’m not real familiar with the LiteSpeed Cache plugin or Redis so you should post a forum topic on the LiteSpeed Cache plugin wordpress.org support forum area.  I’m sure they are have come across this issue before and can give you a working solution.

[AbZu2]

Thanks, will do that.

[AbZu2]

Adding the following code to the theme’s functions.php, solved the problem

add_filter( "litespeed_media_ignore_remote_missing_sizes", "__return_true" );

[AITpro Admin]

Nice!

[Jose]

Hi,

I had some personal problems and for quite some time I did not update the plugin. I just upgraded from version 14.0 to the new version 17.4.
My website is still running on WordPress 4.9 and PHP 7.1, but, after updating BPS I find this PHP Error Log:

[26-Jul-2024 20:34:57 UTC] PHP Warning: preg_match(): Unknown modifier '5' in /homepages/38/dxxxxxxx64/htdocs/wordpress/wp-content/plugins/bulletproof-security/403.php on line 159

What should I do?

[AITpro Admin]

You have a User Agent|Bot name saved in the Security Log > Add User Agents|Bots to Ignore|Not Log option setting that is using an invalid code character.  Click the Remove|Allow button and remove the invalid User Agent|Bot name.

[Jose]

I did it and it worked perfectly well. Thank you.

[Author]

Posts