Forum Moderators: phranque

Message Too Old, No Replies

apache monitor says 'on' but browsers says '404'

         

vegeta01

10:24 pm on Aug 5, 2004 (gmt 0)

10+ Year Member



I suddenly can't connect to my localhost. My browsers (IE/MZ/opera) keep on loading when I want to load [localhost...] or [127.0.0.1...] ... The apache monitor on the other hand is indicating that the server has started.
I really can't get it to work.
I thought it maybe was caused by IIS which I than uninstalled, but the problem remained.
I also got another internet connection (DSL replacing modem) for which I ran an install script. I thought maybe it had changed some ports or so, but I can't find something.

Any ideas?

many thanks

willybfriendly

10:31 pm on Aug 5, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Do you have a software firewall running? If so, check it's settings. I know that both ZoneAlarm and Norton will block access to Apache if not set up right.

WBF

drbrain

10:56 pm on Aug 5, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If the browser gives a 404 message, then Apache is working and you simply have no content.

If you get a 'cannot connect to server' or similar message, then there is something (like a firewall) preventing you from connecting to Apache.

vegeta01

2:07 pm on Aug 6, 2004 (gmt 0)

10+ Year Member



willybfriendly,

No I have no firewall. The XP firewall option is turned off too...

drbrain,

As long as I have my apache server started, the browser keeps on loading. I left it loading for several minutes, but no page got loaded. It should load the default apache page saying that the server is running... When I stop the server, the browser immediatly shows a "The page cannot be displayed" page.

So I'm just not having consequent behaviour in my opinion. Monitor says 'on' but browser keeps on loading. On the other hand, the browser does react like it should when i stop the server => the browser stops loading and says that the page cannot be displayed (Cannot find server or DNS Error)

encyclo

2:10 pm on Aug 6, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Welcome to WebmasterWorld, vegeta01.

First things first - what does the error log say? That should give us some clues.

vegeta01

3:13 pm on Aug 6, 2004 (gmt 0)

10+ Year Member



The log for starting the server and than trying to load localhost is

[Fri Aug 06 17:09:20 2004] [notice] Parent: Created child process 3424
[Fri Aug 06 17:09:20 2004] [notice] Child 3424: Child process is running
[Fri Aug 06 17:09:21 2004] [notice] Child 3424: Acquired the start mutex.
[Fri Aug 06 17:09:21 2004] [notice] Child 3424: Starting 250 worker threads.

I can't make anything up out of this...

If there's any way of seeing if the server gets a request I might see what's wrong.

kalos

6:57 pm on Aug 6, 2004 (gmt 0)

10+ Year Member


Check to make sure that your HOSTS file isn't corrupt or not pointing localhost to 127.0.0.1 . With XP it should be located in the following directory: C:\WINDOWS\SYSTEM32\DRIVERS\ETC

(If you're running Ad-Aware you may have trouble resetting the file as this is a file that some spyware apps like to dork with). The first line of your HOSTS file, minus the one's beginning with a pound sign which are comments, should be:

localhost 127.0.0.1

I used 5 spaces here but typically there's a tab between the host name and IP address. Think of this file as a primative DNS for your computer. I use mine to block out certain ad servers as well as remapping my hostname while testing configurations.

If that isn't it then check your document root and make sure that it exists and has some form of content (index.htm¦index.html).

Also, if you are offline that may be your problem as I have yet to get IE to respond to localhost or 127.0.0.1 requests without a live connection, however Mozilla/Firefox works beautifully.

vegeta01

9:59 pm on Aug 6, 2004 (gmt 0)

10+ Year Member



damn nothing works.

HOSTS file is oke.
documentroot is fine too.

The strange thing is that IE or MZ and Opera just load and load. No timeout, no 404. They only stop when I stop the server and than I get a "The page cannot be displayed" (same as 404 isn't it?) page.

jdMorgan

2:11 am on Aug 7, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



vegeta01,

Welcome to WebmasterWorld [webmasterworld.com]!

> I also got another internet connection (DSL replacing modem) for which I ran an install script.

I'm wondering if the DSL modem requires a connection to a client on your computer, and has attached to port 80. If this is the case, you might want to try telling Apache to LISTEN on a different port, such as post 8080.

Jim

vegeta01

4:07 pm on Aug 24, 2004 (gmt 0)

10+ Year Member



damn, I thought I replied several days ago but no post seems to be placed then.

Anyway, I said something like this:

I installed apache with the option to listen to 8080 and another time to listen to 80, neither of them worked.

The port seems to be listening:

C:\>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP -me-:http -me-:0 LISTENING
...

vegeta01

4:44 pm on Aug 24, 2004 (gmt 0)

10+ Year Member



YEAAAAAAAH

finally it works
Not that I know what the problem was, but after installing [easyphp.org...] it works.

But still curious what could have been the problem ...

Thx for the help