Last post 25 min ago

Posts last week 81

Average response time last week 44 min

All time posts 70349

All time tickets 10858

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#8615 – sitemap-4seo is throwing a 503 backend fetch failed

Posted in ‘4SEO’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Friday, 25 March 2022 16:11 UTC

deef

sitemap-4seo is throwing a 503 backend fetch failed

https://www.[redacted].be/sitemap-4seo.xml

I did a search on internet thought It can be varnish so I disabled this, but I still get this error.

Can it be site analysis because I asked to do a new analysis (changed the main structure of the website) and this is now at 13%

Friday, 25 March 2022 16:17 UTC

wb_weeblr

sitemap-4seo is throwing a 503 backend fetch failed

This is not an error. 503 means that the sitemap is not yet available, it's being built.

Most likely, the site analysis has not completed yet. A sitemap cannot be built until a full site analysis has been completed.

If you rely only on frontend visits triggering the background analysis, this can take some times, especially if your site has few visitors and/or if you have many pages.

Have you tried to run a manual analysis from the admin? use the "Analyze now" button on the Pages page for that.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

Monday, 25 April 2022 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.