Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CurrPorts Question #43

Closed
tachyon99dwa15 opened this Issue Apr 11, 2019 · 6 comments

Comments

Projects
None yet
3 participants
@tachyon99dwa15
Copy link

tachyon99dwa15 commented Apr 11, 2019

Hi Guys,

Long story short. My desktop crashed. It's in the computer shop and the guy still hasn't found a fix for it. So I have to reinstall everything on my laptop. argh! Anyhow. I finally figured how to reinstall composer and redirect it to the right version of php. Yay.

Then I when I tried to start XAMPP. it doesn't because the port is block. I downloaded currPort as suggested by the Professor Susan Buck. It shows that Port 80 is being used. I can't kill it because apparently it has a "Remote Host Name" of an old employer. They gave me the laptop. But does this mean everything I do is logged back to the old employer? I tried to close and kill the proces and run currPort as an Administrator. No luck.

I feel seriously behind. I've been catching up with the lectures and trying to do Project 3 then my desktop crashed. Do any of you guys know how to reclaim this and block the "Remote HostName" of the old employer? haha. Much appreciation!

@tachyon99dwa15

This comment has been minimized.

Copy link
Author

tachyon99dwa15 commented Apr 11, 2019

image

@susanBuck

This comment has been minimized.

Copy link
Owner

susanBuck commented Apr 11, 2019

What if you tried to use an alternative port?

@tachyon99dwa15

This comment has been minimized.

Copy link
Author

tachyon99dwa15 commented Apr 12, 2019

hi @susanBuck : Thanks for the suggestions! I changed the config file(httpd.conf) in XAMPP
#Listen 80 #I commented this out
Listen 8888

Then I restarted XAMPP and I got the following error messages:

However, when I typed in http://localhost:8888/dashboard/ it shows the dashboard correctly.

6:59:25 PM [main] Initializing Control Panel
6:59:25 PM [main] Windows Version: Enterprise 64-bit
6:59:25 PM [main] XAMPP Version: 7.3.1
6:59:25 PM [main] Control Panel Version: 3.2.2 [ Compiled: Nov 12th 2015 ]
6:59:25 PM [main] You are not running with administrator rights! This will work for
6:59:25 PM [main] most application stuff but whenever you do something with services
6:59:25 PM [main] there will be a security dialogue or things will break! So think
6:59:25 PM [main] about running this application with administrator rights!
6:59:25 PM [main] XAMPP Installation Directory: "c:\xampp"
6:59:25 PM [main] Checking for prerequisites
6:59:25 PM [main] All prerequisites found
6:59:25 PM [main] Initializing Modules
6:59:25 PM [Apache] Problem detected!
6:59:25 PM [Apache] Port 80 in use by "Unable to open process" with PID 4!
6:59:25 PM [Apache] Apache WILL NOT start without the configured ports free!
6:59:25 PM [Apache] You need to uninstall/disable/reconfigure the blocking application
6:59:25 PM [Apache] or reconfigure Apache and the Control Panel to listen on a different port
6:59:25 PM [Apache] XAMPP Apache is already running on port 443
6:59:25 PM [mysql] XAMPP MySQL is already running on port 3306
6:59:25 PM [main] The FileZilla module is disabled
6:59:25 PM [main] The Mercury module is disabled
6:59:25 PM [main] The Tomcat module is disabled
6:59:25 PM [main] Starting Check-Timer
6:59:25 PM [main] Control Panel Ready

However, when I type in http://foobooks.loc:8888 it doesn't work

Then when I run XAMPP as administrator it said:
7:03:45 PM [main] Initializing Control Panel
7:03:45 PM [main] Windows Version: Enterprise 64-bit
7:03:45 PM [main] XAMPP Version: 7.3.1
7:03:45 PM [main] Control Panel Version: 3.2.2 [ Compiled: Nov 12th 2015 ]
7:03:45 PM [main] Running with Administrator rights - good!
7:03:45 PM [main] XAMPP Installation Directory: "c:\xampp"
7:03:45 PM [main] Checking for prerequisites
7:03:45 PM [main] All prerequisites found
7:03:45 PM [main] Initializing Modules
7:03:45 PM [Apache] Problem detected!
7:03:45 PM [Apache] Port 80 in use by "Unable to open process" with PID 4!
7:03:45 PM [Apache] Apache WILL NOT start without the configured ports free!
7:03:45 PM [Apache] You need to uninstall/disable/reconfigure the blocking application
7:03:45 PM [Apache] or reconfigure Apache and the Control Panel to listen on a different port
7:03:45 PM [Apache] XAMPP Apache is already running on port 443
7:03:45 PM [mysql] XAMPP MySQL is already running on port 3306
7:03:45 PM [main] The FileZilla module is disabled
7:03:45 PM [main] The Mercury module is disabled
7:03:45 PM [main] The Tomcat module is disabled
7:03:45 PM [main] Starting Check-Timer
7:03:45 PM [main] Control Panel Ready

@susanBuck

This comment has been minimized.

Copy link
Owner

susanBuck commented Apr 12, 2019

To get http://foobooks.loc:8888 working, make sure your VirtualHost block for that domain specifies the correct port; in the notes I show the example using the default port (80) so you'll want to update that to 8888:

<VirtualHost *:80>
    ServerName foobooks.loc
    DocumentRoot C:/xampp/htdocs/foobooks
    <Directory C:/xampp/htdocs/foobooks>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride All
        Order allow,deny
        allow from all
    </Directory>
</VirtualHost>
@liataun

This comment has been minimized.

Copy link

liataun commented Apr 14, 2019

I had a similar issue where System process with PID 4 was using Port 80. In my case only one instance of it in currPort. I disabled IIS and uninstalled all MS SQL Server versions, which seemed to work. This might not be an option in your case, but I thought I would mention it. Susan's instructions for resolving a different port are probably easier.

@susanBuck

This comment has been minimized.

Copy link
Owner

susanBuck commented Apr 17, 2019

I believe Peter has had his original desktop repaired and I don't think this is an issue anymore, so I'm closing this thread out. Feel free to open a new thread if the issue is still pending!

@susanBuck susanBuck closed this Apr 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.