Hello Rhys,
Thanks for reaching out regarding your sitemap.
I can confirm that the page sitemap throws an HTTP 500 error. Can you try increasing the PHP memory limit, as sometimes this could be a memory issue? You can refer to the common errors here for more information.
If you don’t know where to configure or do not have the privileges to do so, please contact your web hosting provider. They’ll be able to provide the related error and/or investigate why the server is responding with a 500 error.
Thread Starter
Rhys
(@rjdusk)
Thanks @maybellyne,
I’ve gone back to my hosting provider (Kinsta) and they temporarily bumped up the memory from 256M to 512M, which allowed this file to render. However that was only a temporary fix.
As the page-sitemap.xml file contains over 500 pages, I wonder if there is an upper limit for these types of files? Using your tool “Yoast Test Helper” to limit the maximum entries per XML sitemap to 250 seems to fix the problem on this file. Would that be a possible solution? Using this tool to limit the amount of entries?
Thanks!
Hello Rhys,
By default, the maximum number of entries per XML sitemap is 1000. And yes, you can set the limit at your discretion using the Yoast Test Helper plugin.
However, I still get an HTTP 500 error when I visit https://www.scandit.com/page-sitemap.xml. Since 5xx errors are server-related, can you ask your web hosting provider for the error log to troubleshoot what may be the root cause?
Thread Starter
Rhys
(@rjdusk)
Hi @maybellyne
I’ve looked through our error logs, I’ve found this line:
2022/08/05 03:55:48 [error] 58659#58659: *16732839 FastCGI sent in stderr: "PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4194312 bytes) in /www/xucobuce_886/public/wp-includes/wp-db.php on line 2136" while reading response header from upstream, client: 193.56.253.58, server: www.scandit.com, request: "GET /page-sitemap.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7.4-fpm-xucobuce.sock:", host: "www.scandit.com:64972"
Any ideas? It seems pretty general to me.
@rjdusk Thanks for your reply.
Unfortunately, the out of memory error you received isn’t specific as to the exact cause of the memory issue. If you have already increased the memory allotment on the site and continue to receive this error, we’d next recommend performing a conflict check in order to see whether another plugin or theme is causing the issue.
The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like TwentyTwentyOne.
Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.
If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.
This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.
