I too am having trouble getting my site to validate. I've been using the coop for a while and everything has been great, but for some reason it isn't validating. Says there are no ads found on www.mables.com I updated back in the beginning of April and it has been working fine. Now that it isn't validating I updated to the April 5th version and it still isn't validating. I've flushed my txt file to see if that would do anything. Nothing, but the new text file is populating itself correctly. I also see some errors in my error log. I see that the blink.digitalpont is looking for my 403.shtml This is exactly what is says in my logs ... [Sat Apr 23 12:12:07 2005] [error] [client 216.9.35.51] File does not exist: /home/mables/public_html/403.shtml So this makes me think that the 216.9.35.51 is getting a Forbidden error and can't see my main page. But I can, and we are still getting traffic to other pages and the ads sho up correctly. Please help if you can. Thanks.
Your server gives this to the validator: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <HTML><HEAD> <TITLE>403 Forbidden</TITLE> </HEAD><BODY> <H1>Forbidden</H1> You don't have permission to access / on this server.<P> <P>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. <HR> <ADDRESS>Apache/1.3.33 Server at www.mables.com Port 80</ADDRESS> </BODY></HTML> Code (markup):
Have you seen this before? Does it mean anything to you? Either way I am contacting my host to see what's going on. Thanks.
Well I figured that much. Checking through my stats it's looks like its mainly your server. But I'm not sure. Not to mean its your fault. I know its something on our end because another domain we have with them (my blog) is giving 403 errors for the php includes all of the sudden and I didn't recently change the code. So I think they are related.
OK I got word back from our host and it looks like they tightened up security on the servers due to a hack attempt made earlier in the week. This security update is what was causing this 403 error and has now been fixed. Thanks for the quick feedback Shawn.