This is a discussion on Installation: "Failed to Connect" to localhost within the Apache Web Server forums, part of the Web Server and Related Forums category; Hi, I'm an user with some experience with the Apache webserver. I installed it previosly on a Win95 and ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hi,
I'm an user with some experience with the Apache webserver. I installed it previosly on a Win95 and Win98 system without a problem. I think I even had it on a WinXP laptop. Now I try to install it again on my desktop to develop my own website, and stumble on a problem. I get the following error in my SeaMonkey window: Failed to Connect The connection was refused when attempting to contact localhost. Why is my system not working? Some information on my system: AMD Athlon XP 2600+, 2.09 GHz, 512 MB Ram WinXP Home, version 2002, SP2 McAfee Security Center, without firewall protection ZoneLabs free firewall Apace 2.2.3, installed using the Win32 Binary (MSI Installer) The only possible problem I now have is with McAfee. After last mondays XP upgrade I have problems with it starting up and connecting to McAfee. So I had a period without any virus protection. I deinstalled, and re-installed twice, and as it now is, it seems to work. Can anyone help me? I have Apache installations without problems before, so this is a head scratcher for me. TIA, Abel |
|
|||
|
Abel wrote: > Hi, > > I'm an user with some experience with the Apache webserver. I installed > it previosly on a Win95 and Win98 system without a problem. I think I > even had it on a WinXP laptop. Now I try to install it again on my > desktop to develop my own website, and stumble on a problem. > > I get the following error in my SeaMonkey window: > Failed to Connect > The connection was refused when attempting to contact localhost. > > Why is my system not working? > > Some information on my system: > AMD Athlon XP 2600+, 2.09 GHz, 512 MB Ram > WinXP Home, version 2002, SP2 > McAfee Security Center, without firewall protection > ZoneLabs free firewall > Apace 2.2.3, installed using the Win32 Binary (MSI Installer) > > The only possible problem I now have is with McAfee. After last mondays > XP upgrade I have problems with it starting up and connecting to McAfee. > So I had a period without any virus protection. I deinstalled, and > re-installed twice, and as it now is, it seems to work. > > Can anyone help me? I have Apache installations without problems before, > so this is a head scratcher for me. what does the apache error.log say, is windows firewall turned on as well as zone alarm, have you configured zonealarm not to block the apache process, or port 80. Try turning off all firewalls, includeing windows built in and connecting then, and check error.log for answers. |
|
|||
|
shimmyshack wrote:
> > what does the apache error.log say, is windows firewall turned on as > well as zone alarm, have you configured zonealarm not to block the > apache process, or port 80. > > Try turning off all firewalls, includeing windows built in and > connecting then, and check error.log for answers. > This is the last contents of my log: [Thu Jan 11 13:24:41 2007] [notice] Apache/2.2.3 (Win32) configured -- resuming normal operations [Thu Jan 11 13:24:41 2007] [notice] Server built: Jul 27 2006 16:49:49 [Thu Jan 11 13:24:41 2007] [notice] Parent: Created child process 2260 [Thu Jan 11 13:24:41 2007] [notice] Child 2260: Child process is running [Thu Jan 11 13:24:41 2007] [notice] Child 2260: Acquired the start mutex. [Thu Jan 11 13:24:41 2007] [notice] Child 2260: Starting 250 worker threads. [Thu Jan 11 13:24:41 2007] [notice] Child 2260: Starting thread to listen on port 8080. [Thu Jan 11 13:26:44 2007] [notice] Parent: Received shutdown signal -- Shutting down the server. When I started Apache after shutting down ZoneAlarm, I got this message in the dos-box: (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:8080 no listening sockets available, shutting down Unable to open logs Note the errors or messages above, and press the <ESC> key to exit. 12... I have no Windows firewall running. Abel |