Forum Moderators: phranque
Here is error log details :
[Thu Aug 27 06:15:15 2009] [error] [client 121.245.144.48] File does not exist: /home/mydomain/public_html/404.shtml
[Thu Aug 27 06:15:15 2009] [error] [client 121.245.144.48] File does not exist: /home/mydomain/public_html/favicon.ico
[Thu Aug 27 06:15:13 2009] [error] [client 121.245.144.48] File does not exist: /home/mydomain/public_html/404.shtml
[Thu Aug 27 06:15:13 2009] [error] [client 121.245.144.48] File does not exist: /home/mydomain/public_html/favicon.ico
[Thu Aug 27 06:14:32 2009] [error] [client 121.246.77.177] File does not exist: /home/mydomain/public_html/404.shtml, referer: [mydomain.com...]
[Thu Aug 27 06:14:32 2009] [error] [client 121.246.77.177] File does not exist: /home/mydomain/public_html/mydomain/css/admin/images/back.gif, referer: [mydomain.com...]
--Thanks--
The favicon.ico is being requested automatically by your browser. The fact that it does not exist is not serious -- unlike your missing custom error page above. However, you are losing out on an effective branding opportunity by not having a favicon for your site, and I'd recommend downloading one of the many free favicon-creator programs and making a small, low-resolution version of your site's logo for use as a favicon. The .ico format supports multiple resolution images combined in one .ico file; The best favicon creator programs will create these multi-resolution favicons at 16x16, 32x32, and 48x48 pixels, for use in various applications on the users' computers/devices.
Unfortunately, neither of the above may have anything to do with the 'big' problem of you page not appearing, but your error log gives no indication of a problem serving the *page*. It only reports the two problems above. However, since there's an error on the 404 handling, this 404-handling problem may be 'hiding' the original problem that results in your pages not being served.
I suspect that your pages are dynamically-created and that the script that generates your pages has a problem. Look around for any other script-related error logs on the server, and try (as a test only) replacing one of your dynamic pages with a static HTML file. Then try to view that page and see whether it always works or not. If it does, you can rule out most basic caching problems, reducing the number of possible problems you'll have to investigate.
Finally, check the filepath on the request for 'back.gif' (the last error logged above). Is that filepath entirely correct? If not, then you've got some problem with the URL-to-filepath mapping on the server, caused by errors in configuration, errors in rewriting (e.g. mod_dir, mod_rewrite, etc.), errors in #include and #require statements in your scripts, or errors in the links on your pages -- for example, I find it suspicious that your back.gif file seems to be located in your css directory tree according to the path shown in that error log entry.
Jim