500 Error and site totally down - suddenly!
Hi,
Just out of nowhere my development site went totally down with 500 Internal Server Error. The server log gives the following:
[2023-03-16 13:21:10.593059] [vhost: lets-customize.com] [core:error] [pid: 43049] [client: 88.196.157.242:49324] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
How can this happen all of a sudden without changing any plugins etc? Debug mode of Wordpress gives these errors when in the Back-End:
Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/class-wp-user.php on line 212
Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Cookie/Jar.php on line 63
Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Cookie/Jar.php on line 73
Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Cookie/Jar.php on line 89
Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Cookie/Jar.php on line 102
Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Cookie/Jar.php on line 111
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82
Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Warning: Cannot modify header information - headers already sent by (output started at /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/class-wp-user.php:212) in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/pluggable.php on line 1416
Warning: Cannot modify header information - headers already sent by (output started at /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/class-wp-user.php:212) in /data03/virt117972/domeenid/www.lets-customize.com/htdocs/wp-includes/pluggable.php on line 1419
Comments
Hi,
Did you contact your hosting provider regarding this? If not, please, do that.
Also, please, check the following video tutorial:
https://support.muffingroup.com/video-tutorials/wordpress-6-1-update-issue/
See if the problem persists if you disable Betheme via FTP.
Thanks
Hi,
Yes it does :( Even when disabling it and switching to other default theme. Wordpress version is latest. The only slight cue I have maybe got is that when I disable WPML the home page starts to show mostly properly but whenever clicking on a link still a 500 error comes.
Do you think this is a WPML thing...? Weird that just all of a sudden with no changes.
Seems like the issue is interconnected to the issue I have in the other support thread: https://forum.muffingroup.com/betheme/discussion/comment/231662#Comment_231662
Sorry, but the problem is not BeTheme related, so our help will be limited.
Please go into your FTP and rename your 'plugins' folder to other and create empty directory with the 'plugins' so all of them will be disabled.
If it will not work, please ask your hosting provider and ask him about logs on his side, maybe it will enlight the source the problem.
Thhanks