LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Fedora Core 4 Webserver problems (https://www.linuxquestions.org/questions/linux-newbie-8/fedora-core-4-webserver-problems-405028/)

mpeck 01-18-2006 02:32 PM

Fedora Core 4 Webserver problems
 
I have read some of the other post about this and it just made me more confussed. My goal is to have a dedicated local testing web server for back up and QC before I upload tothe main site. I had a friend help me set up my webserver over AIM client last night. Everything seems to be set up right according to him.

We created to vIP's and made two sub domains beta.domain.com and prod.domain.com. Well I thought all was ok, whenI typed inthe url and the apache testing screen came on. After this I edited the /etc/httpd/conf.d/welcome.conf. to get rid of the test page. Well the test page is gone, but all i get is a blank white page. I have my site dir in /var/www/html? Does anyone know what could be the problem?

Again, I am just using this for the local acces for testing.

-Matt

First post :study:

scott_R 01-18-2006 03:11 PM

Do you have an index.html, index.htm, index.php, or other similar file, or is your server configured to direct users to another file? Example, which should be in your main config file:

DirectoryIndex index.html index.cgi index.pl index.php index.xhtm

Apache defaults to looking for index.html and a couple other files, and if there isn't one it's looking for, it'll either give you an error or a blank page (usually it will error, but not always). Another likelihood is that (especially if you're using a php or alternative file format, that either a module isn't set up correctly, or there is an error in the page coding, leaving the web server displaying nothing at all. Also, though not directly related, is that your server's error handling isn't set up correctly, so instead of giving you an error, it's just leaving you with a blank page to stare at.

Obviously, start testing on your server (localhost, through a browser on that machine, lynx is good for a non-gui server), to see if you can access the files from there, and work your way outwards. If you're using something like PHP, you might even want to test the pages for errors using php's console-based program (which you might have to install separately).


All times are GMT -5. The time now is 06:51 AM.