• Resolved juancruz0033

    (@juancruz0033)


    Hi, we’ve been facing an issue at least from July, some of our sitemaps are inaccessible most of the time. The 502 error we’ve been told by our hosting is due to the request taking longer than 60 seconds to load. We tried reducing the number of results per page and it is still happening.

    https://www.hstpathways.com/sitemap_index.xml

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @juancruz0033,

    Thanks for using the Yoast SEO plugin. I experienced the 502 errors on some of the sitemaps. Can you ask that the WordPress memory limit be increased? You can configure this in your wp-config.php.

    define(‘WP_MEMORY_LIMIT’, ‘256M’);

    In your PHP.ini, you can increase the server memory to:

    memory_limit = 512M

    Thread Starter juancruz0033

    (@juancruz0033)

    Hi @maybellyne I asked the hosting support to help with this and they changed both settings but we’re still facing the same issue.

    Plugin Support Maybellyne

    (@maybellyne)

    Thank you for the feedback, @juancruz0033.

    The server error logs usually provide more details about the issue. If you have access to your server error log, note the date and time before generating the error again. Then, immediately check your server error log for any errors during that period. If you don’t have access to your server error log, please ask your hosting provider to look for you.

    If you or your web host cannot pinpoint the cause, please provide us with a copy of the server error log for further investigation. As server logs can cover a significant amount of time, please limit the error log to a few minutes before and after the behavior was reproduced.

    If the server error log does not contain any errors at the time of the issue, please enable advanced WordPress debugging with the code here. This code requires that you change line 84 to point to a path on your server. Your web host can provide you with a secure path to save the error.log file.

    Thread Starter juancruz0033

    (@juancruz0033)

    Hi @maybellyne I wanted to give my latest update on the issue: it appears that it was resolved. The web host support identified the cache settings as the possible root cause for the 502 errors. Apparently, it was disabled or it was being refreshed too often. They changed these settings and now it’s working correctly.

    Thanks for your support!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘502 Errors while trying to access the sitemaps’ is closed to new replies.