sitemap-post generates error 500

  • Resolved barbccfl

    (@barbccfl)


    6 months, 3 weeks ago

    Google Search Console returned an error for my sitemap-post XML page generated by Yoast plugin (the free version). Going directly to the URL generates a 500 error. All the other XML indexes are working fine, including one for a custom taxonomy. I have tried the suggested troubleshooting, but nothing has worked. I use the Divi theme and builder, both up to date. I disabled all plug-ins, including Wordfence, and got the same result. I ran an XML validation check and got this result, “Incorrect http header content-type: “text/html; charset=UTF-8” (expected: “application/xml”)” Are there other steps I can take?

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Suwash

    (@suascat_wp)

    @barbccfl

    We acknowledged that the post-sitemap.xml is returning 500 Internal server error. While we are in attempt to gather some more information about the cause of this error, would you be able to provide the error log information from your server? We want to see if there are any PHP errors recorded in the error log which might help us narrow down the cause. You may need to contact your hosting provider for this information.

    Thread Starter barbccfl

    (@barbccfl)

    I have the log file, how do I attach it here or send it to you? It is .gz compressed file. I could place in Dropbox…

    Thread Starter barbccfl

    (@barbccfl)

    I sorted through the log file and pulled some representative lines that show both myself and others trying to load the post-sitemap page. I am 71.1.237.0, you can see I accessed the sitemap index in the morning and just the posts page failed. I have not included the many times throughout the day where I was testing the post-sitemap, but I did include below where I tried loading the .xsl version. The other examples look to be bots and the validators that were visiting the page.

    71.1.237.0 – – [05/May/2024:09:47:57 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
    71.1.237.0 – – [05/May/2024:09:48:02 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
    71.1.237.0 – – [05/May/2024:09:48:05 -0400] “GET /page-sitemap.xml HTTP/1.1” 200 1802 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
    71.1.237.0 – – [05/May/2024:09:48:33 -0400] “GET /category-sitemap.xml HTTP/1.1” 200 5695 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“

    5.255.231.0 – – [05/May/2024:11:36:53 -0400] “GET /robots.txt HTTP/1.1” 200 262 barblafara.com “-” “Mozilla/5.0 (compatible; YandexBot/3.0; +https://yandex.com/bots)” “-“
    5.255.231.0 – – [05/May/2024:11:36:55 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 (compatible; YandexBot/3.0; +https://yandex.com/bots)” “-“

    52.167.144.0 – – [05/May/2024:11:37:39 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +https://www.bing.com/bingbot.htm) Chrome/116.0.1938.76 Safari/537.36” “-“
    52.167.144.0 – – [05/May/2024:11:37:59 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +https://www.bing.com/bingbot.htm) Chrome/116.0.1938.76 Safari/537.36” “-“

    2600:1f18:7d00:: – – [05/May/2024:13:58:03 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “W3C_Validator/1.3 libwww-perl/6.68” “-“

    85.92.66.0 – – [05/May/2024:13:59:26 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 (compatible; XML Sitemaps Generator; https://www.xml-sitemaps.com) Gecko XML-Sitemaps/1.0” “-“

    71.1.237.0 – – [05/May/2024:14:55:49 -0400] “GET /post-sitemap.xsl HTTP/1.1” 200 – barblafara.com “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
    71.1.237.0 – – [05/May/2024:14:55:50 -0400] “GET /favicon.ico HTTP/1.1” 302 – barblafara.com “https://barblafara.com/post-sitemap.xsl” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“

    85.208.98.0 – – [05/May/2024:16:03:51 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 169 barblafara.com “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25 (compatible; SiteAuditBot/0.97; +https://www.semrush.com/bot.html)” “-“

    Thread Starter barbccfl

    (@barbccfl)

    Further troubleshooting, I installed a different plug-in that makes XML sitemaps called ‘XML Sitemap Generator for Google 4.1.19’. It successfully made a post list, https://barblafara.com/post-sitemap.xml So, why isn’t Yoast able to make one?

    BTW, I have other WP sites on this hosted server and they also use Yoast and all of their post XML pages are working. None have exactly the same plug-ins installed, so it could be some sort of conflict, but I disabled all the plug-ins yesterday, including Wordfence, and still had the issue. AND, if it is a conflict, wouldn’t the other XML sitemap pages fail?

    Plugin Support Maybellyne

    (@maybellyne)

    I will first recommend ensuring that the PHP settings for both?max_execution_time?and?memory_limit?are set to a high enough value in the PHP environment. This setting is typically controlled by editing the values in a php.ini file, such as in the following example: max_execution_time = 300 memory_limit = 256M

    If you aren’t sure how to change these settings in php.ini, we would recommend contacting your hosting provider for additional assistance.

    Plugin Support Jose Varghese

    (@josevarghese)

    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.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘sitemap-post generates error 500’ is closed to new replies.