If you come across this error when trying to view your XML sitemap using your browser don’t fret. Mainly it appears the error is with the Google XML Sitemaps plugin. Here is the error:
Error loading stylesheet: An unknown error has occurred (805303f4)
Solution for this XML sitemap error:
This one’s a quick fix, if you can call it that. I don’t think it’s really an actual error that would harm anything, however when comparing the browser input URL with the URL in the erorr, you can see it has something to do with the www or non-www in front of the URL.
All I needed to do was enter the URL without the “www” in front and it loaded the sitemap fine. Now I can view it through the browser to verify there were no errors with the sitemap before Google Webmaster submission!
13 Responses to “Fix For Error loading stylesheet: An unknown error has occurred (805303f4)”
Drew
Thanks your advice worked like a charm.
Naren Chopra
Yo ! It just saved hell of my time. No coding , no function stuff. But, is there any problem if sitemap on www works perfectly and doesn’t work on non-www . In my case when I followed your article, my sitemap is loading with http://www.mydomain. com but it gives the same error on http://mydomain. com
Alan
Oh man, saved me from more wasted time. Thanks for the fix. Wonder if there’s a way to have it dynamically recognize www vs. non-www.
Avtar Singh
im getting same error and my sitemap not processed by webmaster yet…what i should for that ?
Shuvo Shuvo
I tried, but it is not working for me……….
AB SAM
Where do you enter the URL without the www?
Brent Parkinson
If you are using WordPress then follow this guide below
Login into wordpress admin
once you have logged in Look on the left hand site You will see Settings
Click Settings and then click General You will see WordPress Address (URL)
change from the www Your sitemap will be fine
WeLoveWP
Yes, this can be a solution, but if you don’t want to change your actual WordPress URL, this method is not a good option. It’s best not to change your main WordPress URL as it can harm your SEO rankings because it’s a URL change!
HrvojeG
Yap, that worked. The server name must be the same in XML and XSL paths. Thanks a lot.
WeLoveWP
Glad it worked for you!
Alexis Wilke
Ah! Yes. This is a security feature. Both files have to come from the same source. There are ways around it, but it’s not easy to handle that just for one or two files. It has been like that for a while now, but I still get caught once in a while. The worst part for Firefox in this case is that it’s not telling you that’s a security issue. Just a random number that most of us can’t read. That being said, if you have debug console opened, it tells you. Most would probably not think of opening it though…
Lennart
Had this problem on a site using http:// and the xslx file tried to load from https://.
Solved it by adding the following lines at the top of .htaccess
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www.(.*)$ [NC]
RewriteRule ^(.*)$ //%1/$1 [R=301,L]
WeLoveWP
Nice, thanks for the tip Lennart!