如何停止本地Kentico项目占用localhost:8080端口？

Hey there, let's work through this port issue step by step—sounds like Kentico's got a persistent hold on port 8080, and the usual quick fixes aren't doing the trick. Here are targeted solutions to free up that port and get it back to its default state:

1. Pinpoint & Terminate the Exact Process Holding Port 8080 #

Sometimes the first pass at checking processes misses background services. Let's get precise:

• Open Command Prompt as Administrator and run:

  netstat -ano | findstr ":8080"
  

  This will spit out a PID (the number at the end of the line) for the process clinging to the port.
• Open Task Manager, switch to the Details tab, find the PID from the command above, right-click it, and select End Task.
  • Don't just hunt for obvious Kentico processes—keep an eye out for iisexpress.exe, dotnet.exe, or even a stray Visual Studio process that might be keeping the Kentico site running in the background.

2. Disable Kentico's Auto-Starting Background Services #

Kentico runs several background services that might launch on boot and lock the port without you noticing:

• Press Win + R, type services.msc, and hit Enter.
• Look for services with "Kentico" in the name (like Kentico Event Log Service or Kentico Scheduling Service).
• For each matching service, right-click > Stop, then set the Startup Type to Manual so it doesn't auto-launch next time you boot your machine.

3. Reset IIS/IIS Express Configuration #

If you're using IIS or IIS Express with Kentico, leftover site bindings might still be tying up port 8080:

• For full IIS: Open Command Prompt as Admin and run:

  iisreset
  

• For IIS Express:
  1. Close all instances of Visual Studio.
  2. Navigate to C:\Users\[YourUsername]\Documents\IISExpress\config and open applicationhost.config.
  3. Search for <site> entries where bindingInformation includes :8080:localhost, then delete those entire site blocks.
  4. Save the file and restart your machine to clear any cached settings.

4. Verify Port Status & Test #

After completing the steps above, run the netstat command again to confirm no processes are using 8080. Then try accessing localhost:8080—you should see the "can't reach this page" error you're aiming for.

If all else fails, a quick system restart might clear up any stuck background processes that aren't showing up in Task Manager.

内容的提问来源于stack exchange，提问作者Ebrahem Luhar