<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Deepika</title>
    <description>The latest articles on DEV Community by Deepika (@buggedbuthappy).</description>
    <link>https://dev.to/buggedbuthappy</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3085650%2Fc988c116-ed13-4c0d-b709-10c7d6858f24.png</url>
      <title>DEV Community: Deepika</title>
      <link>https://dev.to/buggedbuthappy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/buggedbuthappy"/>
    <language>en</language>
    <item>
      <title>🚀 Debugging the World: How I Fixed Port 8080</title>
      <dc:creator>Deepika</dc:creator>
      <pubDate>Thu, 24 Apr 2025 20:02:53 +0000</pubDate>
      <link>https://dev.to/buggedbuthappy/debugging-the-world-how-i-fixed-port-8080-24pl</link>
      <guid>https://dev.to/buggedbuthappy/debugging-the-world-how-i-fixed-port-8080-24pl</guid>
      <description>&lt;p&gt;&lt;strong&gt;Ever had a day where you’re just minding your own business, coding away, and suddenly — BAM! — your web server refuses to start? 😱&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Me: Alright, time to start my web server!&lt;br&gt;
Terminal: lol no.&lt;br&gt;
Terminal again: &lt;br&gt;
&lt;code&gt;Port 8080 is already in use&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Me: &lt;em&gt;Excuse me? By whom??&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🕵🏾‍♀️ The Investigation (Windows)
&lt;/h2&gt;

&lt;p&gt;Like a true tech detective (read: someone who panicked and Googled), I did:&lt;br&gt;
&lt;strong&gt;Step 1:&lt;/strong&gt;Opened  &lt;strong&gt;Command Prompt&lt;/strong&gt; (or terminal) and get ready for battle.&lt;br&gt;
&lt;strong&gt;Step 2:&lt;/strong&gt; Ran the command to locate the rogue process: &lt;br&gt;
&lt;code&gt;netstat -ano | findstr :8080&lt;/code&gt; &lt;br&gt;
(This showed me which sneaky process is holding onto that port.)&lt;br&gt;
&lt;code&gt;TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 12345&lt;/code&gt;&lt;br&gt;
&lt;strong&gt;Step 3:&lt;/strong&gt; Now for the fun part — terminate that process!&lt;br&gt;
&lt;code&gt;taskkill /PID 12345 /F&lt;/code&gt;&lt;br&gt;
(Don’t worry, it’s not as brutal as it sounds. Just a gentle nudge for the process to move along.)&lt;br&gt;
&lt;code&gt;taskkill /PID 12345 /F&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;✨ &lt;strong&gt;Port conquered. Server awakened.&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Victory: achieved. Confidence: restored. 🚀&lt;/p&gt;




&lt;h2&gt;
  
  
  💻 Not on Windows?
&lt;/h2&gt;

&lt;p&gt;Don’t worry, Linux and macOS users — you’ve got your own spell:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Run &lt;code&gt;lsof -i :8080&lt;/code&gt; to see what’s using the port.&lt;/li&gt;
&lt;li&gt;You’ll get a result like:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;COMMAND   PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME&lt;/code&gt;&lt;br&gt;
&lt;code&gt;node     12345  user   22u  IPv6  0x...  0t0     TCP *:http-alt (LISTEN)&lt;/code&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Terminate&lt;/strong&gt; it with:
&lt;code&gt;kill -9 12345&lt;/code&gt;
&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  🎉 The Mini-Lesson?
&lt;/h2&gt;

&lt;p&gt;Ports are sneaky.&lt;br&gt;
Background processes? Also sneaky.&lt;br&gt;&lt;br&gt;
Always check who’s squatting on your ports.&lt;/p&gt;

&lt;p&gt;💬 Let me know if you’ve been personally victimized by &lt;strong&gt;port 8080&lt;/strong&gt;, or any other port — I’m here for the struggles.&lt;/p&gt;




&lt;p&gt;&lt;code&gt;#buggedbuthappy&lt;/code&gt; &lt;code&gt;#devlife&lt;/code&gt; &lt;code&gt;#webdev&lt;/code&gt; &lt;code&gt;#debugging&lt;/code&gt; &lt;code&gt;#developerhumor&lt;/code&gt; &lt;code&gt;#tinyrantsbiglessons&lt;/code&gt; &lt;code&gt;#programming&lt;/code&gt; &lt;code&gt;#learning&lt;/code&gt; &lt;code&gt;#windows&lt;/code&gt; &lt;code&gt;#linux&lt;/code&gt; &lt;code&gt;#macos&lt;/code&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
