I have a working WAMP server with no problems on a Windows 8.1 Pro platform but i need to implement WAMP on several other machines all running a version of Windows (classroom environment). Some machines work perfectly fine, but others not so much. We are trying to reinstall WAMP but nothing seems to be working. The issue is
1.) every time i want to use WAMP i have to install all services before they can run. Then when i attempt to open a file on localhost i get an error that says service not found. Files are all in the right location (\www)
I have read that port 80 might be an issue but when we execute the port 80 test, no traffic issues. To be safe, we changed the port to 8080 and the same issues arrise.
Anybody have an issue like this or anything similar.
The soluton above will probably aslo do the job. When I was dealing with the same issue with Wamp on Win 10. All resolved by following steps:
open command line under as an administrator
make sure it is process with PID 4 listening to port 80:
netstat -o -n -a | findstr 0.0:80
change http process to use another port (i.e. 8000):
netsh http add iplisten ipaddress=0.0.0.0:8000
restart http service
net stop http
net start http
restart Xamp processes
i faced the same problem earlier, and the solution is
It should solve your problem.
Thanks
Related
I spent a long time trying to figure out how to fix my Apache server on MAMP local host. I kept getting an error message saying that 'Apache couldn't start, because port 80 was in use by httpd'. Everyone seemed to think that another program was blocking port 80 (e.g. IIS, Skype, etc.). I tried finding these programs and removing them, but every time I did, the only program that was using port 80 was called System and I didn't think I could safely turn that off. I tried changing my port for Apache. Nothing worked until I found a solution saying that you could just change your php version in MAMP. I did this, and instantly Apache started working again.
My question is why would this happen? Why did changing my version of php fix Apache, and is there a way that port 80 could be blocked without another program being the reason.
I got some trouble with my xampp on Win 10, as so many have had before me...
It's the same old port problem with skype and IIS.
I used to quit skype and stop the world wide web publishing service, but am sick of having to go through the whole ordial every time I start xampp.
so yesterday I changed the ports for my apache server and ecerything worked fine.
started up today and boom...localhost couldn't find my pages.
So I checked for port problems in xampp...there were none! apache was up and running(as were mysql server and filezilla). no error messages, nothing.
I resetted the ports to 80 and 443. killed of skype and the iis and everything worked fine again. Now whenever I change the ports, it will not run.
I did everything according to here:
How to change XAMPP apache server port?
(I changed the ports in httpd.conf, httpd-ssl.conf and in service and port settings )
I just don't get it. why it won't run with changed ports(and yes I checked the ports for being empty).
atm I have changed the port 80 -> 8024
and port 443 -> 1337 (no matter what I change this port to it always throws bad request)
8024 works fine. I can get to the dashboard via localhost:8024
but localhost:1337 gives me a bad request.
any suggestions, or similar encounters?
For now will have to continue using standart ports and kill of the 2 processes, but I really wanna skip that in the future.
I used port 80->8024
and port 443->448 yesterday and it worked fine...really weird...
Ok so that means your system has Microsoft IIS installed or one of the other bits of MS technology that reports that signature, they are doing that on later versions of Windows for some reason.
If you are not intending to use it you can uninstall it, it is not an integral part of windows so its being uninstalled wont effect normal operations of windows, and if you need to install it again later, it comes as part of the standard OS so you wont need to do anything perticularly clever.
So go to Start -> Control Panel -> Programs and Features
Click the 'Turn windows features on and off' link in the left hand menu.
Wait for the list to load and then find 'Internet Information Services'
Un check the check boxes for the following items ( you may not see all of them ), and there may be others I done know about. You may have all of these or just some of these.
IIS
Web Deploy 2.0 (Web Deployment Agent Service)
MS Sql Server Reporting service.
BranchCache ( Windows 8.1 )
SQL Server VSS Writer
List of possible service names not sure how up to date this is.
Tutorial on how to find what ports are in use on your system and what app is using them
Windows will then have a think for a while and then remove those applications, you will probably be asked to reboot to complete the uninstalls.
Reboot anyway when the uninstalls are complete.
Then try XAMPP again
I am new to php and I would like to run a local testing server using easy php at home to work on school projects but when I try to start the easy php server, this error message pops up: Apache port (80) is already used by another application ! Close this application and try to run again the server It then gives me some instructions on how to close the application (by killing processes of selected ports), but when I right on the selected ports, the kill processes option is faded and not clickable. Maybe there something else I need to check or do on my computer to run this local host? Thanks for all help!
Just a shot in the dark but maybe try to close Skype, if you have that running, and then start the server? If I remember correctly Skype listens on port 80 by default. If that's indeed the issue then you can configure Skype not to listen on port 80 in its settings...
That might be related to Skype or the IIS server using port 80. You can configure Skype to use different ports in the preferences. You might try going to "localhost" in your browser and see what comes up as well. If it shows a Microsoft IIS server page then you know that the server is running. Disabling that or turning that off depends upon your operating system. You can probably just look that up on the internet if that is the issue.
So I installed XAMPP and it worked fine at first (At least I think so. I typed in localhost and got the XAMPP page).
I have the files for the site I'm working on in my Dropbox folder so they stay up to date across my computers. I was looking for a way to point XAMPP to my working folder so I didn't have to work in htdocs and then move it back to Dropbox.
I found this thread:
Make XAMPP/Apache serve file outside of htdocs
And I followed cmcculloh's answer on how to set up a virtual host.
As the last step in his instructions said, I restarted Apache.
Except it won't start.
I click Start in the control panel and it says 'Starting apache service...'
....and it sits there
After Googling about it I saw tips like disable make sure port 80 is clear and disable anti-virus. And use 'netstat -nab' in a cmd prompt to check if something is using port 80
Well AvastSVC.exe is using port 80. What I don't get is why it worked fine after I installed it, with Avast running.... But it wasn't until I tried to restart that suddenly Avast is getting in the way.... So I'm not so sure that that's the problem.
Maybe it's something I did when I was trying to set up the virtual host?
I just want to test php without uploading to a web server D=
Edit:
Oh and btw, I closed Avast and made sure the process was gone but it still shows up under 'netstat -nab'. I looked under Services and there is still an Avast service but it won't let me stop it =S
If this is just for testing/learning/development purposes, perhaps you could try using EasyPHP and set an alias to the Dropbox folder with the HTML files within. Also, I recommend you use port 8080 for development, not port 80.
I am new to Windows IIS and I need to run a php/mysql application on it. For local php development on windows, I have found WAMP to be the easiest.
But can WAMP be used in this case instead of installing php and mysql separately ?
This needs to be done on an ec2 Windows 2003 instance. So far, I have already tried installing WAMP and setting up apache to listen on port 8080 instead of 80. From inside the remote desktop, both IIS and WAMP work properly in parallel on their respective ports.
However, when I try to connect from another computer using the ip address http://184.**.***.***, IIS works fine serving the default web page but cannot connect to apache on http://184.**.***.***:8080.
Is it possible to use WAMP at all for this purpose and if yes, would there be any disadvantages in using it instead of installing php/mysql seperately ?
Edit :
I dont know if this is a problem of blocked 8080 port. To verify this I stopped IIS and configured apache to listen to 80. Even then http://184.**.***.*** doent show the WAMP homepage. IS anything needed to be configured in IIS ?
RESOLVED :
Added the port 80 in Windows Firewall Exceptions and it started working.
Also, its necessary to select "Put Online" in the WAMP tray otherwise it gives a forbidden response as suggested by some answers.
Thanks
I haven't used EC2 in this way before, but broadly speaking, I'd encourage you to use the same server for development and production environments if at all possible - the installation effort can be a bit of a pain, but it's nothing compared to developing an app locally and then finding an IIS configuration issue causes it to break on production.
This approach also lets you keep your PHP configurations in source code control - php.ini and any modules you're using - and automatically deploy them alongside your application; again, forgetting to deploy the correct PHP.ini usually makes your application do crazy things...
So, your choices appear to be:
- switch off IIS and have WAMP listen to port 80. Not sure WAMP is designed for production level traffic, but in the past, I've run low-traffic public websites in this way.
- work out why port 8080 is blocked, and if it can be unblocked. This would still require you to run your website on an unusual port, which makes for ugly and hard-to-communicate URLs.
- install PHP on your IIS instance. One benefit of having installed WAMP is that MySQL should already be up and running, and the basic PHP installation should also be there; getting PHP to run on IIS is no longer a dark art ([http://php.iis.net][1])
For my money, I'd go for the latter option...IIS is a production quality server, and it's clearly what Amazon want you to use in this instance.
Of course, running IIS on your development environment may be a problem.
Have you put the server online? Think it is offline by default, meaning it's only accessible from your local machine. It's an option in the systray menu to put it online.
If I remember well, there is an option "go public" (or "put online") on the system traya icon of wamp.
This option modifies the httpd.conf to authorize public access.
You should give a try.
On a side note, you can make php work with IIS. This is another option to help you manage your server. (Mysql and Php have to be installed separatly but, this is very easy to do as far as I remember :) )