Home/ Questions/Q 4053478
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T14:27:08+00:00

I am new to Windows IIS and I need to run a php/mysql application

  • 0

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

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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.

    • 0