Bobcares

How to fix Port 80 Conflict for WAMP like an expert

by | Jan 11, 2022

How to fix Port 80 Conflict for WAMP with a little help from our in-house experts.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped a customer by fixing Port 80 Conflict for WAMP.

How to fix Port 80 Conflict for WAMP

Is your WAMP icon orange in color and not giving you access to localhost/phpMyAdmin in the browser? According to our Support Techs, this is a clear indication that another service is utilizing the same port the Apache needs to function. Additionally, Apache listens on port 80 by default.

Fortunately, we can resolve the port 80 conflicts by changing the port number rather than removing or disabling any service. Before we get on with that, here are a few Window services that listen on port 80:

  • Internet Information Server (IIS)
  • Web Deployment Agent Service
  • Microsoft HTTPAPI/2.0
  • World Wide Web Publishing Service
  • SQL Server Reporting Services

These steps by our Support Team will help you change the port number in a breeze:

  1. First, we will right-click the WAMP icon present in the system tray and then click Tool.
  2. Then, we have to change the port number for MySQL and Apache.
  3. Next, we will select Test Port 80 for Apache.
  4. After that, we will check which program is using the port by examining the command prompt that opens after the previous step.
  5. Then, we will again right-click the WAMP icon in the system tray, click Tools, and then select Use a port other than 80.
  6. Next, we have to enter the new port number for Apache in the small window that opens up.
  7. After that, we can verify Apache is listening on the new port, ensuring the process was successful.

How to fix Port 80 Conflict for WAMP

Another way to change the Apache port is by editing the httpd.conf file. We can find the file in the C:\wamp64\bin\apache\apache\conf directory. Our Support Techs recommend searching for 0.0.0.0 to find these lines:

Listen 0.0.0.0:80
Listen [::0]:80

Then, all we need to do is replace the port number with any number between 80 to 8080 and save the file as shown below:

Listen 0.0.0.0:8080
Listen [::0]:8080

Once we restart the WAMPServer, the icon color will not be orange any longer.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To conclude, the skilled Support Engineers at Bobcares demonstrated how to fix Port 80 Conflict for WAMP.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF