wamp server 2.4 x64 not working on my windows 8 x64 - apache

I have a windows 8 x64.
I installed apache 2.4 x64 and the installation was smooth and the service is up and running and also the icon is also green.
the problem is that it stops working in the middle of nowhere although the icon is still showing up green and the status saying online.
I have to refresh the localhost page over and over again to get it working again.
I added some line in c:\windows\system32\driver\etc\hosts file
127.0.0.1 localhost
I also modified the C:\wamp\bin\apache\Apache2.4.4\conf\httpd.conf file.
here is the line which I added.
Listen 0.0.0.0:80
I even removed my Skype since I heard that it conflicts with apache
when I test my http 80 port using the apache tool. sometimes it get me no result. it only shows me
Your port 80 is actually used by :
it doesn't give me the rest of the information but sometimes it shows me that my apache 2.4 is running
I removed IIS server which comes together with windows 8.
I also tried installing apache again but the problem is still there.
Any help from you guys would be much more appreciated.
Thanks.

Related

Wamp is not working after Windows 10 upgrade

WampServer worked fine on my computer running Windows 8.1. I've upgraded to Windows 10, and now Wamp is not working. The WAMP icon is red. I've looked into the Internet Information Services and found that World Wide Web Services folder was unchecked. I went to services.msc and the World Wide Web Publishing Service is missing from the list. Took off skype from port80. I've tried changing the port address in httpd.conf to 8090 and 9080. I tested port80 through WAMP - Apache interface and found out that "Your port 80 is not actually used". I'm not very good at using the command prompt. I don't know how to ensure that Apache uses port 80. I'm asking if this the problem and how to fix it. Or at least how to get WAMP working again. Thanks!
If you had WAMPServer installed before you upgraded to Windows 10 then the solution is simple. The problem is that the W10 upgrade does not know about the Apache and MYSQL (wampmysqld and wampapache) services, and therefore does not re-register them.
All you have to do is this using the wampmanager menus
wampmanager -> MYSQL -> Service -> Install Service
wampmanager -> Apache -> Service -> Install Service
Its probably a good idea to the exit WAMPServer and then restart it, but not usually necessary.
I tried several ways to make it run but it didn't. Suddenly, I selected a different version of PHP from WAMP tray and it did the trick. May be it will help many out there facing this issue.

Wamp Server Working But Still Orange

No, this is not a duplicate question!
Wamp Server doesn't start on system boot up.
When I turn it on, it is in Orange but it works just fine and Test Port 80 says that it is used by Server: Apache and PHP.
I have to Ctrl+Alt+Del < Task Manager < (2) Apache Httpd Servers
Then end both tasks.
Then Restart All Services and Wamp will be green!
My questions are
1. if it works then why is it in orange?
2. can I make it start on system start?
Note: MySQL Server is working properly at all time.
I don't have Skype installed and I don't think the problem is with the ports...
I have already tried uninstalling then re-installing but that didn't fix the problem.
EDIT:
According to the solution #RiggsFolly suggested, I can see that Apache is not starting properly; however, weirdly the web app can be run normally...
you can also change the port as well. yes you can start wamp service on system start by setting in start up program MSConfig can be used to configure several things other than just startup programs.

Can't access to wamp/xampp apache localhost:80 WINDOWS 10

I recently upgrade my Windows 7 to Windows 10 (9). I need to use Apache server for web development. But for some reason I can't access it via web browser.
First I tried to look in the firewall and antivirus settings. It looks fine. I've tried reinstall xampp then I tried Wamp. Nothing working. I'tried 3 web browsers Edge, Opera, Chrome. Then I tried to find if some application is blocking port 80. So I disabled Skype, IIS. Then I tried different ports 8080,9080,123. Still can't access it via browser, but ping works.
Then I disable preference of Ipv6 and I prefer IPV4 now. I've changed HOSTS file so only 127.0.0.1 localhost is uncommented.
Only problem occurs when I try run wamp my internet access became unavailible and a have to restart computer to access internet again.
Has anyone here have same problem, because according to everything I ve done it seems apache server and network settings is correct.
Maybe problem is somewhere else?
Thank you for your help.
Solved with clean Windows 10 installation.

MAMP error: couldn't be started

I've installed MAMP (windows) and I can't start it. When I first opened it, i got the usual error of port 80 already used. But after i changed it to another port, 8888, i got a diferent error:
Could not wait for starting of Apache child. Apache parent process id is: 6208
I'm always getting this error, even though i've reinstalled MAMP and tried diferent ports as well, like 2222, and I keep getting the error. Besides, the process id in the error is always diferent every time i try to start MAMP.
Any suggestions?
First of all, "MAMP for Windows" IS for Windows! I do prefer it to a WAMP due to simplicity.
After getting a "Could not wait for starting of Apache child. Apache parent process id is"
I have disabled a Windows firewall.
Then, I have uninstalled the .NET, C++, and then the MAMP.
Then, I have installed the MAMP again, with all the .Net and C++ files that come with it.
Then, enabled the firewall back.
It now works.
First of all MAMP is not for windows it stands for Mac Apache Mysql Php so you need to install WAMP(Windows Apache Mysql Php) than if you have installed Wamp, change the port to 80 again. the error(port 80 already in use) comes from one of the following problems:
Skype: Make sure that you have stopped skype or unistall it.
SQL Server Reporting System: if you have installed sql server so please stop the process of SQL server reporting system.
After this tips restart your server and the problem is solved. If still the problem is not solved comment back.

Apache Tomcat not working in every web browser installed in Windows7 32Bit

I'm working on a web application in JSP and my web container is Apache Tomcat 7.0.2 (Its portable cross-platform version). As I've made extensive use of HTML5-CSS3 and my target browser is Google Chrome, I'm able to run the the Apache server only in Opera web browser, neither of the remaining installed browser run it.
Here's the steps I have followed to start the server in my Windows 7 machine.
-Installed the Apache Tomcat service in Windows from apache-tomcat-7.0.2/bin/service.bat
-Started the service with tomcat7w.exe
-As my default port is 8080, I open 'http://localhost:8080/' in various web browsers, and I could see Apache Server Homepage with same address only in Opera Web Browser (11.01), neither of other browsers installed can open it (Chrome 9, Firefox 4 Beta 11 or IE8) and show standard page not found message.
-I also tried other port numbers, but none of them worked.
What can I do to make Apache run in every browser installed in my computer?
I have my computer dual boot with Windows 7 and Ubuntu 10.10, and in Ubuntu, every web browser installed can run Apache once I start it, but same is not working in Windows.
Update:
I have also tried apache's windows-only installer of version 7.0.8 and changed the port number during installation, but still I can't run it on any other browser expect for Opera...
Any help will be appreciated............
Thanks.
Check your hosts file under C:\Windows\system32\drivers\etc\hosts to make sure that the entry for
127.0.0.1 localhost
is intact. Also see that if you are behind a proxy server, the settings allow for localhost to be bypassed.
Congo!! finally got it done, instead of localhost, it works with 127.0.0.1 (which is localhost anyway)
So those who are facing similar issues, as suggested by adarshr, go through your hosts file to see if localhost is correctly addressed to 127.0.0.1, or if you don't want to edit that file, you can still get it done by simply using http://127.0.0.1:8080/ instead of http://localhost:8080/. Please be sure about port number you are using, in my case it was 8080, it might vary depending on how you've configured.