[SOLVED] Non-displaying Website Data: Javascripts and Images

KZeeSoft · 03-10-2010, 12:02 PM

I have a weird problem I am experiencing with my Apache 2.2 w/ ISPConfig 3 running on Debian 5.0.4. It is not a website html issue.

***PROBLEM***
Images are not beind displayed, javascripts are not being run, however when the site is viewed from a local source as a file(like on a USB Flash Drive) they work fine and display properly.

Here is the website URL:

www.sufuku.net

I have removed a lot of the images and content or changed it in order to troubleshoot it myself, so the site is stripped pretty bare. There is supposed to be a logo inside the "header" <div>, which is set in the CSS file "style.css". There are supposed to be images for navigation, but they show up as red "x"'s. I removed the javascript elements and just trying to work with barebone html/css and can't seem to get it to display properly.

Is this due to privileges on the partition? I have a separate /var/www partition that is mounted nodev, nosuid, noexec, usrquota, grpquota. Could this be the problem?

Thanks in advance!

rweaver · 03-10-2010, 12:50 PM

The server isn't displaying them because it can't find them.

http://www.sufuku.net/images/homebutton.png for example doesn't exist, but it's being referenced by the index page. The same is true of the javascript file you're referencing, the server is returning a 404 error.

I would suggest that you look at your logs, verify permissions, and ensure that things exist where you are referencing them.

What permissions do you have on the directories and files individually?

KZeeSoft · 03-10-2010, 01:38 PM

They exist, I can see them when I pull up an "ls" command in the shell.

UPDATE: Did that, after carefully inspecting the file list, I noticed that I had some files with upper-case characters in the file name, but not in the html code. Same thing with the directories. /facepalm

A word to the wise and newbies like me.... LINUX IS CASE SENSITIVE!!! Even in your HTML code, SO BE CAREFUL!

Thank you for helping me realize this rweaver =)

Hats off to you!

rweaver · 03-10-2010, 02:17 PM

Always watch your logs carefully too! They're paramount if finding the cause of errors like that. Another sneaky one I've seen a few times of late is something like this:

/var <-755 root:root
/var/www <-700 root:www
/var/www/domain.tld <-755 domain:www

Which of course means the apache user can't actually access the domain directory since it doesn't have an execute bit that applies to it. Fixed by chmod 711 /var/www. \