Wamp Server 5 Download !FREE!
Clemencia Branski
At first, I use Struts 2 to develop a website in Java web technology. So I installed Apache Tomcat as the localhost server and MYSQL as the database (MYSQL here is the full application from mysql.com, not the packages like XAMPP or WAMP...)
The best alternative here would be to install one of the servers inside a virtual machine with network configured as "host-only-adapter" so that from the base machine you could access XAMPP/WAMP installed on the virtual machine by just pointing the ip-address of the virtual machine through a web-browser.
If you want to run both XAMPP and WAMP together on the same machine but access only one of the servers at a time then you could go ahead installing both of them one after another. But, keep in mind that before installing the other server you have to completely stop all the services running from the XAMPP or WAMP control panel then quit the application. After this step you can go ahead installing the other server without changing any configurations or port numbers. This is because in this case we assumed that only one of the servers would be accessed at a time. Hence, before launching the other server one has to completely quit the application that is running currently by stopping all of it's services. If skype is installed then one has to change the default incoming connection ports to other than port 80 and 443.
Like mentioned above, if at all the intention is to access both servers up and running concurrently then taking advantage of a virtual machine would be the best to avoid conflicts and a long-term troubleshoots eventually.
I got the same problem and found that it is not the SQL server which is conflicting, but the SQL server Reporting service. I went to services.msc and stopped SQL server Reporting service. I also chagned it to manual so that it does not start automatically on a reboot. Now I restarted WAMP server and it turned green.
Change the port number from 80 to something like 8888 (in the thousands) - to change the port number you must click on the wamp or mamp and then click on apache then click on httpd.conf and then searchfor listen. Change the port number to 4444 or 8888 or something in the thousands.
I got the same problem and found that it is not the SQL server which is conflicting, but the SQL server Reporting service. It seems it is using same port 3306 which is being used by MYSql. I went to services.msc and stopped SQL server Reporting service. I also chagned it to manual so that it does not start automatically on a reboot. Now I restarted WAMP server and it turned green.
Presently I am not using SQL server Reporting services, hence I can keep the service stopped. I have no idea how I can change the port for this service so that they don't conflict. If any one really wants to use SQL server Reporting services, he or she may dig deeper into this service to somehow change the port.
I am using windows 7 and wamp server 2.2, I have installed the wamp server and i have already installed IIS server now when i access localhost always IIS server is loading but i want to use wamp server instead of IIS server.
Thanks for writing in! To validate your localhost, you need to generate an api key using pjtest.com as your domain name. The generated key will work as long as you access your local server using /localhost/ will not work and will return invalid URL.
I'm using windows 8. recently i've installed wampserver3_x86_apache2.4.17_mysql5.7.9_php5.6.15. but the put online/offlline option is missing. I did wamp manager->wamp settings->menus item online/offline. it doesn't work also. there is no green the green mark beside this option.
I have tried restarting wamp.I have tried checking the php version and they are the same.I have tried uncommenting certain PHP handlers (but they were already uncommented).I have tried adding handlers, no avail.I have tried editing the .htaccess file. Nothing.
As this is pointing Apache to the wrong place for the php.ini file. In WAMPServer, the php.ini file that Apache should be using is automatically copied into \wamp\bin\apache\apacheversion\bin by the WAMPServer software. Well since WAMPServer 2.5 it actually creates SYMLINKS in that folder to the correct file in the active PHP version folder.
I am installing the Wamp Server on another computer to run a mid-sized database and UI. I have been successful in blocking IIS and routing the server to Localhost:8080. But whenever I try to access on of my projects from the localhost homepage, in the www file; I get redirected to a Page not found error.
Now you must restart the DNS Cache. You can do this from the wampmanager menus like this right click wampmanager->Tools->Restart DNS. The DNS Cache will be restarted and then Apache will also be stopped and restarted. When the wampmanager icon goes green again all is completed.
This made life easy for the complete beginner, and was perfectly acceptable for example for those following tutorials to learn PHP coding.However it was never intended for use when developing a real web site that you would later want to copy to your live hosted server.In fact if you did use this mechanism it often caused problems as the live sites configuration would not match your development configuration.
regardless of what your subfolder was called.This ment that often used PHP code that queried the structure or your site received different information when running on your development WampServer to what it would receive when running on a live hosted server, where the DocumentRoot configuration points to the folder at the top of the website file hierarchy.This kind of code exists in many frameworks and CMS's for example WordPress and Joomla etc.
Now this difference may seem trivial at first but if you were to use a framework like WordPress or one of the CMS's like Joomla for example, this can and does cause problems when you move your site to a live server.
There are actually 2 new menu items on the wampmanager menu system. One called 'My Projects' which is turned on by default.And a second one, called 'My Virtual Hosts', which is not activated by default.
'My Projects' will list any sub directory of the \wamp\www directory and provide a link to launch the site in that sub directory.As I said earlier, it launches 'project1` and not 'localhost/project1' so to make the link work we must create a Virtual Host definition to make this link actually launch that site in your browser, without the Virtual Host definition it's likely to launch a web search for the site name as a keyword or just return a site not found condition.
The 'My Virtual Hosts' menu item is a little different. It searches the file that is used to define Virtual Hosts ( we will get to that in a minute ) and creates menu links for each ServerName parameter it finds and creates a menu item for each one.This may seem a little confusing as once we create a Virtual Host definition for the sub directories of the \wamp\www folder some items will appear on both of the 'My Projects' menu and the 'My Virtual Hosts' menu's.
ALSO:See that I have allowed this site to be accessed from the internet from within the VHOST definitions, this change will apply to only this site and no other. Very useful for allowing a client to view your changes for an hour or so without having to copy them to the live server.This does mean that we have to edit this file manually to turn this access on and off rather than use the Put Online/Offline menu item on wampmanager.
Find your Apache icons directory! Typically it will be located here: "c:/wamp/bin/apache/apache2.4.9/icons". However your mileage may vary depending on your installation and if your Apache version is different, then your path will be different as well.\
Open up httpd-autoindex.conf in your favorite editor. This file can usually be found here: "C:\wamp\bin\apache\apache2.4.9\conf\extra\httpd-autoindex.conf". Again, if your Apache version is different, then so will this path.
Re: Wampserver LocalHost links not working correctly
This is as of June 2014 with Wampserver2.5 (maybe they'll fix this in later builds).
Note: to use LocalHost:8080 instead of LocalHost just make the appropriate changes in the edits mentioned below.
There are 2 aspects of this issue -
The first is to be able to access items under "Your Projects" from the Wamp localhost homepage.
The second is to be able to correctly access items listed in the Wampserver Icon Taskbar's "My Projects" list.
Navigate to your www directory (if you are using wamp server) htdocs (if on XAMPP). Open your admin.php and search on project contents/ or just go directly to line number 339 and change the link, inserting 'local host to the link .
When you are sitting at a different computer that is NOT on the same IP subnet (not connected to the same router and/or switch) and you put the EXTERNAL IP address in the browser, you don't see the web server.
Have you forwarded port 80 in the router to the internal IP address of that computer? Does your ISP allow inbound access/traffic on port 80? How would you test this? Well, first, make sure your router doesn't have a firewall blocking inbound port 80 traffic. Make sure you properly forwarded port 80. Make sure your internal IP address is static (in the DHCP table). If you have done these things... then it might be an issue with port 80. You can test it by going into WAMP and changing the port used to... whatever... 8080. This is just for testing purposes anyway. Then, go back into the router, and everywhere you dealt with port 80, change it to 8080. Then try accessing the server.
This is how I solved the problem, and it is obvious if you think about. In Wampserver 3.2 there is a wizard to create your virtual host. However, it only used the name of the virtual host folder as the name of the virtual host server. When you access the server remotely you use the fully qualified domain name, but there is no configuration for that yet in Wampserver httpd-Vhost.conf file. Get to this file from the Wampserver->Apache menu. Copy the current vhost you want to access and paste that config into the file. Change the servername to the fully qualified domain name of the vhost. This also assumes you have a DNS CNAME entry for your vhost.
31c5a71286