I installed Apache 2.2 on my pc and open my web browser then go http://localhost/ ,but nothing occurs.
can anyone help me in this problem?
I installed Apache 2.2 on my pc and open my web browser then go http://localhost/ ,but nothing occurs.
can anyone help me in this problem?
in the bottom left corner it says "waiting for localhost...".
Apache isn't responding. Make sure it is running, and try restarting it.
JasonLester wrote:in the bottom left corner it says "waiting for localhost...".
Apache isn't responding. Make sure it is running, and try restarting it.
I uninstalled it and delete the apache file,restart my pc and try http://localhost/ ,but nothing happen ,same as the pictue above , again .
Why not try using Xampp its great you get php and mysql and has a https pages if you need them and you can use perl with it if you get the addon. handy little program.
This is an issue with th service itself, rather then PHP. I would suggest looking in apaches log folder and post back what you find, and if you don't find something obvious I would suggest another package like Smackie. I use Phperl (php+perl) when I'm on Windows. Comes with PHP5, perl, apache 2, mysql, smtp/pop server, ftp, myphpadmin, and a good control panel for service administration such as apache virtual hosts. It free. If you like the package you already I might be able to fix your problem with the log entries.
Smackie wrote:Why not try using Xampp its great you get php and mysql and has a https pages if you need them and you can use perl with it if you get the addon. handy little program.
Tried and failed.In addition , I uninstalled and delete it,then I installed WAMP but the same thing repeated again . So, in the end, I uninstalled it and delete WAMP.Then tried again and it still showing the same thing.
again and again.
might check the html page and the php page to see if its blank?
Smackie wrote:might check the html page and the php page to see if its blank?
where should I check£¿
ÎÞÁÄÈË wrote:where should I check£¿
Thats not it. If that was the case it would say "Done" in the bottom right corner with a blank page.
Look inside the apache2 directory and you will have a folder named 'logs'. look in there and it will likely tell you whats going on.
JasonLester wrote:Thats not it. If that was the case it would say "Done" in the bottom right corner with a blank page.
Look inside the apache2 directory and you will have a folder named 'logs'. look in there and it will likely tell you whats going on.
But I uninstalled and deleted it already,and my web browser still the same.
Thats weird... I guess a lot of this can be effected by the settings in firefox or even your PC settings in general (firewall settings, etc) but it SHOULD be giving you a unknown host error if you don't have a service running on localhost port 80. Check the error message in the attachment, thats what happens when I shut apache down on my localhost, it should be the same thing with apache not installed. Long story short, if nothing is running on port 80 then nothing should happen, and that 'should' cause an error. Your not getting the results that you want, but with it hanging like that something is happening to keep firefox from failing. any type of connection at all, even if it hangs rather then giving you a page, is something when there should be nothing. Sorry, I can see where that might sound confusing :queasy:
try typing "telnet localhost 80" in a windows com box. It should absolutly come back saying:
Connecting To localhost...Could not open connection to the host, on port 80: Connect failed
If not you have something running on HTTP's port.
There are programs that will open on port 80 for various reasons, including many types of trojans. Start with trying to telnet it, and with that out of the way we can work from there.
I can deduce your problem this far (somebody correct me if im wrong please):
1) First, if nothing is running on port 80 then it shouldn't be stalling
2) If it was a firewall issue then the connection would be refused, which should have the same result as #1, it should be failing rather then stalling
3) If the page simply wasn't there you would get a 404 error. Thats a mute point if you have already uninstalled apache, but at the same time we shouldn't see it as an option.
4) apache should have been responding in some way when it was installed, even if that response was en error message rather then the page you were hoping for. with it behaving the same way without apache as it did when apache was running, I'm questioning if the request ever made it to apache. You should have been getting a page with apache, or at least a 404 or 500 error, and now you should be getting a 'Server not found' error in apache.
I think that your problem lies in number 4, but the fact that it wasn't failing is suspicious, and is even more so now that nothing should be on port 80 with apache is uninstalled.
Jason
JasonLester wrote:Thats weird... I guess a lot of this can be effected by the settings in firefox or even your PC settings in general (firewall settings, etc) but it SHOULD be giving you a unknown host error if you don't have a service running on localhost port 80. Check the error message in the attachment, thats what happens when I shut apache down on my localhost, it should be the same thing with apache not installed. Long story short, if nothing is running on port 80 then nothing should happen, and that 'should' cause an error. Your not getting the results that you want, but with it hanging like that something is happening to keep firefox from failing. any type of connection at all, even if it hangs rather then giving you a page, is something when there should be nothing. Sorry, I can see where that might sound confusing :queasy:
try typing "telnet localhost 80" in a windows com box. It should absolutly come back saying:
Connecting To localhost...Could not open connection to the host, on port 80: Connect failed
If not you have something running on HTTP's port.
There are programs that will open on port 80 for various reasons, including many types of trojans. Start with trying to telnet it, and with that out of the way we can work from there.
I can deduce your problem this far (somebody correct me if im wrong please):
1) First, if nothing is running on port 80 then it shouldn't be stalling
2) If it was a firewall issue then the connection would be refused, which should have the same result as #1, it should be failing rather then stalling
3) If the page simply wasn't there you would get a 404 error. Thats a mute point if you have already uninstalled apache, but at the same time we shouldn't see it as an option.
4) apache should have been responding in some way when it was installed, even if that response was en error message rather then the page you were hoping for. with it behaving the same way without apache as it did when apache was running, I'm questioning if the request ever made it to apache. You should have been getting a page with apache, or at least a 404 or 500 error, and now you should be getting a 'Server not found' error in apache.I think that your problem lies in number 4, but the fact that it wasn't failing is suspicious, and is even more so now that nothing should be on port 80 with apache is uninstalled.
Jason
When I type telnet localhost 80, something weird happened.
In addition,I tried apache before and succeed with "It works",then I proceed to test some .php,everthing was fine but when I changed some content inside the .php file , I ran into the situation above.Ruined .:mad:
Then , there goes install and uninstall nightmare.
ÎÞÁÄÈË wrote:When I type telnet localhost 80, something weird happened.
In addition,I tried apache before and succeed with "It works",then I proceed to test some .php,everthing was fine but when I changed some content inside the .php file , I ran into the situation above.Ruined .:mad:
Then , there goes install and uninstall nightmare.
The response that you got in telnet is typical when it connects to a service. Windows telnet sucks so you wont see anything you type. This shows that you have something running on port 80 which is reserved for HTTP.
telnet into localhost 80 again and type (or copy/paste)
GET / HTTP/1.1
Don't worry when you dont see the characters. when done hit enter twice.
Here is what my system returns
HTTP/1.1 400 Bad Request.
Date: Sat, 17 May 2008 10:18:07 GMT
Server: Apache/2.0.50 (Win32) PHP/5.2.5
Content-Length: 312
Connection: close
Content-Type: text/html; charset=iso-8859-1 I'm not sure what you will get, by what you have already explained it might not respond at all. Thats basically what is happening in Firefox, its sending 'GET http://localhost/index.html HTTP/1.1' and not getting a response, so its just waiting, thinking that the page will eventually come. If your lucky you will get a similar response that will clue you in on what service is on port 80.
First thing you want to do if it doesn't respond is hit ctrl+alt+del and check the 'Processes' tab in the task manager to make sure that the Apache service isn't still running (I know, it shouldn't be... but at this point nothing should be on port 80). Its listed as Apache.exe on my system. My bet is that Apache isn't completely uninstalled. If its listed try restarting your computer to see if its still there.
If its not listed you need to run a good anti-spy tool.
Post back if you still need help
Have you check task manager to see if apache is running, or ever was?
JasonLester wrote:The response that you got in telnet is typical when it connects to a service. Windows telnet sucks so you wont see anything you type. This shows that you have something running on port 80 which is reserved for HTTP.
telnet into localhost 80 again and type (or copy/paste)
GET / HTTP/1.1
Don't worry when you dont see the characters. when done hit enter twice.
Here is what my system returns
HTTP/1.1 400 Bad Request. Date: Sat, 17 May 2008 10:18:07 GMT Server: Apache/2.0.50 (Win32) PHP/5.2.5 Content-Length: 312 Connection: close Content-Type: text/html; charset=iso-8859-1I'm not sure what you will get, by what you have already explained it might not respond at all. Thats basically what is happening in Firefox, its sending 'GET http://localhost/index.html HTTP/1.1' and not getting a response, so its just waiting, thinking that the page will eventually come. If your lucky you will get a similar response that will clue you in on what service is on port 80.
First thing you want to do if it doesn't respond is hit ctrl+alt+del and check the 'Processes' tab in the task manager to make sure that the Apache service isn't still running (I know, it shouldn't be... but at this point nothing should be on port 80). Its listed as Apache.exe on my system. My bet is that Apache isn't completely uninstalled. If its listed try restarting your computer to see if its still there.
If its not listed you need to run a good anti-spy tool.
Post back if you still need help
Firstly,there isn't any response.
:mad:
Unfortunately,its not listed on my system.
Attached files is the list that window task manager shown.
Any suggestion?
I'm curious to what webthunder is but I googled it and didn't find anything that jumped out saying that it was a trojan or something. everything else looks OK, but thats typical with spy-ware... their not likely to run as hack.exe
Download ad-aware or any other good anti-spy tool and do a spy-ware sweep on your system.
JasonLester wrote:I'm curious to what webthunder is but I googled it and didn't find anything that jumped out saying that it was a trojan or something. everything else looks OK, but thats typical with spy-ware... their not likely to run as hack.exe
Download ad-aware or any other good anti-spy tool and do a spy-ware sweep on your system.
I downloaded ad-aware and did a spy-ware sweep on my system and try localhost ,no response again .Then, I tried to restore system back to the date before I install apache ,but the outcome is still the same.The same problem repeat and repeat.
Attached file is what I saw when I start Apache.
ÎÞÁÄÈË wrote:I downloaded ad-aware and did a spy-ware sweep on my system and try localhost ,no response again .Then, I tried to restore system back to the date before I install apache ,but the outcome is still the same.The same problem repeat and repeat.
Attached file is what I saw when I start Apache.
There are three messages in that prompt, one is a waring saying that apache cant determine your host name and that they will use your IP to fix (this is typical and OK since your not on a dedicated server), the second is a fatal error saying that it cant start apache because it is unable to bind to port 80 (already in use, "only one usage of each socket is permitted"), the third is a warning about not being able to open the log (this is weird, but probably not a big problem or anything related to the main issue)
You still have something else running on port 80. at this point you can say that it possibly isn't spy-ware, but that makes me question why it isn't responding... from the beginning I saw thats a sign that a) its a legitimate service that is broken, or b) an evasive service that is trying not to be found. So at this point if we assume that it is a legitimate service we need to ask what it might be. The few of the common answers are:
1) file sharing programs - some p2p programs like Shareaza have a built in webserver for sharing files via WWW
2) game - some games have a built in webserver for showing off stats
3) email / ftp server - some services provide a web frontend for administration and HTTP access for users.
To make matters more confusing, I googled services running on your system and none are services that should occupy port 80, which points even more to this being spy-ware. Either the service is embedded into a legitimate service, such as rundll32.exe, or it is masquerading as another service. Do you have bittorent installed? some spy-ware is known to install itself as btdna.exe to keep from getting caught. btdna.exe is a bittorrent service, so if you don't have bittorrent this is very possibly the problem.
Sorry I can't give you any more specific help. at first I was assuming that you installed a game or something that took over port 80 without knowing that it would, but that would show up in the task manager, and it would likely respond. At this point I'm guessing that your dealing with some particularly evasive spy-ware.
Something on your computer is already listening on port 80, so Apache can't get exclusive access to that port.
To find out what application is using that port, go to Start, click Run, and type in cmd. In the command prompt window, do these commands:
cd desktop
netstat -a -b -p TCP >port_list.txtWait until the command completes and then open the .txt file that is now on your desktop.
What you're looking for is "<YourComputerName>:http" under Local Address, with "LISTENING" under the State column. Directly under that line should be a filename. I, for example, see "Apache.exe" as my computer is running Apache2 at the moment. Report back here with the filename that you find is listening on port 80.
EDIT: Note that this post was aimed at users running Windows XP (possibly Windows 2000, though the netstat command is a bit different on Win2k) - NOT Windows Vista.
bradgrafelman wrote:Something on your computer is already listening on port 80, so Apache can't get exclusive access to that port.
To find out what application is using that port, go to Start, click Run, and type in cmd. In the command prompt window, do these commands:
cd desktop netstat -a -b -p TCP >port_list.txtWait until the command completes and then open the .txt file that is now on your desktop.
What you're looking for is "<YourComputerName>:http" under Local Address, with "LISTENING" under the State column. Directly under that line should be a filename. I, for example, see "Apache.exe" as my computer is running Apache2 at the moment. Report back here with the filename that you find is listening on port 80.
EDIT: Note that this post was aimed at users running Windows XP (possibly Windows 2000, though the netstat command is a bit different on Win2k) - NOT Windows Vista.
Thanks bradgrafelman, I'll have to remember that one