Upgrade & Secure Your Future with DevOps, SRE, DevSecOps, MLOps!

We spend hours scrolling social media and waste money on things we forget, but won’t spend 30 minutes a day earning certifications that can change our lives.
Master in DevOps, SRE, DevSecOps & MLOps by DevOps School!

Learn from Guru Rajesh Kumar and double your salary in just one year.


Get Started Now!

XAMPP – Port 80 in use by “Unable to open process” with PID 4

To resolve a port conflict in XAMPP, follow these steps:

Open CMD as administrator, run “net stop was /y” command.

Open the Run dialog (Win+R), type “services.msc” to access the Services management console. Locate and stop the “World Wide Web Publishing Service” and “Web Deployment Agent Service”, and disable them to prevent future conflicts.

Finally, start Apache in XAMPP for uninterrupted web development.

About this Issue :

XAMPP is a popular software package that provides a local development environment for web applications. However, one common issue that users encounter when running XAMPP is a port conflict on port 80. This conflict prevents the Apache web server from starting and displays an error message similar to “Unable to open process” with PID 4

  1. Understanding the Port Conflict: When XAMPP’s Apache web server starts, it attempts to bind to port 80, which is the default port for HTTP traffic. However, if another process is already using port 80, such as the Windows operating system process with PID 4 (System), a conflict occurs. As a result, XAMPP cannot open the necessary port, and the Apache service fails to start.
  2. Identifying the Process with PID 4: To resolve the port conflict, it is crucial to identify the process that is using PID 4. Here’s how you can do it: a. Open the Command Prompt with administrative privileges. b. Execute the following command: netstat -ano | findstr :80 c. Look for the entry with the local address 0.0.0.0:80 and note the corresponding PID in the last column.

Resolving the Port Conflict: Once you have identified the process with PID 4, you can take one of the following approaches to resolve the port conflict:

a. Stop the Conflicting Process:

  • Open the Task Manager by pressing Ctrl + Shift + Esc.
  • Switch to the “Processes” tab.
  • Locate the process with the PID noted earlier.
  • Right-click on the process and select “End Task” or “End Process Tree”.
  • Confirm the action if prompted.
  • Restart XAMPP and check if the port conflict is resolved.

Change Apache’s Port:

  • Navigate to the XAMPP installation directory (typically C:\xampp on Windows).
  • Open the httpd.conf file located in the apache\conf directory.
  • Search for the line containing Listen 80.
  • Replace 80 with an alternative port number (e.g., 8080).
  • Save the file and restart the Apache service in XAMPP.
  • Access your web application using the new port number (e.g., http://localhost:8080).

Related Posts

Understanding and Fixing the “Unable to Read Key from File” Error in Laravel Passport

Laravel Passport is a powerful package for handling OAuth2 authentication in Laravel applications. It allows you to authenticate API requests with secure access tokens. However, like any…

How to Generate a GitHub OAuth Token with Read/Write Permissions for Private Repositories

When working with GitHub, you may need to interact with private repositories. For that, GitHub uses OAuth tokens to authenticate and authorize your access to these repositories….

Laravel Error: Target class [DatabaseSeeder] does not exist – Solved for Laravel 10+

If you’re working with Laravel 10+ and run into the frustrating error: …you’re not alone. This is a common issue developers face, especially when upgrading from older…

JWT (JSON Web Token) vs OAuth 2.0

Both JWT and OAuth 2.0 are used for managing authentication and authorization, but they serve different purposes and work in distinct ways. 1. Purpose: 2. Role: 3….

Exploring and Creating a Proof of Concept (POC) to Upload APK Directly from GitHub Package

Automating the process of uploading an APK (or AAB) to the Google Play Store from GitHub can significantly speed up your CI/CD pipeline. By integrating Google Play’s…

A Detailed Guide to CI/CD with GitHub Actions

Continuous Integration (CI) and Continuous Deployment (CD) are modern software development practices that automate the process of integrating code changes, running tests, and deploying applications. With the…

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x