Member Avatar for ikitshop

Hi,

When i submit my sitemap.xml in googlewebmaster tool they give me error of

"Network unreachable: Network unreachable
We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit."

what is problem that i don't understand then i check the url in that sitemap.xml file is not block with the robots.txt so what is prob. with that.

i check the si0temap.xml in google validator it give me document in valid"

my sitemap : theautopartsshop.com/sitemap.xml

  • 3 Contributors
  • 3 Replies
  • 120 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by ikitshop

Dani AI

Generated

Follow-up for (and for anyone who sees this thread later): when a sitemap fetch fails because the server appears unreachable, it is usually a network or server configuration problem rather than an XML syntax issue. Thanks to and for their earlier suggestions — below is a concise, practical checklist that isolates the usual causes and how to test them.

Quick checks to run from a shell (replace yourdomain.com):

dig +short A yourdomain.com
dig +short AAAA yourdomain.com

curl -4 -I https://yourdomain.com/sitemap.xml
curl -6 -I https://yourdomain.com/sitemap.xml
curl -I -L https://yourdomain.com/sitemap.xml

curl -A "Googlebot/2.1 (+http://www.google.com/bot.html)" -I https://yourdomain.com/sitemap.xml

openssl s_client -connect yourdomain.com:443 -servername yourdomain.com

How to interpret the results: an AAAA record that exists while curl -6 fails points to an IPv6 routing/configuration problem (Google may try IPv6 first). Different responses between -4 and -6 show that. curl -I -L reveals HTTP status and redirects; 4xx/5xx responses mean the server is rejecting the fetch. The Googlebot-simulated curl -A checks for user-agent blocking. openssl s_client shows TLS handshake and certificate chain issues that can stop HTTPS fetches.

Additional steps: check web server access/error logs around the Search Console fetch time for entries mentioning sitemap.xml; look for connection errors or 403/503 responses. Verify firewall or host-level filters are not dropping requests from common crawler ranges. Confirm the sitemap is served with an XML content-type and within the size/URL limits specified by Google (see Sitemaps - Google Search Central).

Collecting these outputs will usually reveal whether the problem is DNS, IPv6, firewall, TLS, or a transient hosting/network outage — each has a distinct fix path, so the checks above are the best way to identify the root cause.

Recommended Answers

All 3 Replies

Member Avatar for manomanjudotcom

Submit again after few hours.

Member Avatar for canadafred

Submit again after few hours.

... and maybe try another generator, I briefly glanced at your XML and something just didn't look right although it looks OK. I'm not much of a scripter so I can't say for sure but why don't you just try another like this one http://www.xml-sitemaps.com/ or an equivalent free generator and resubmit.

Member Avatar for ikitshop

Submit again after few hours.

Hi,

Thanks for sharing nice information !! but now my problem get solved..

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.