Comments on: Windows Tip

By: Quickie: Apache and Skype » Otto on WordPress

Quickie: Apache and Skype » Otto on WordPress — Wed, 09 Jun 2010 16:03:17 +0000

[...] morning and couldn’t get it to start. Turned out Skype was the problem. Matt apparently encountered this years ago, but I neve rreally started using Skype until [...]

By: Ben Nadel

Ben Nadel — Wed, 28 Apr 2010 23:48:43 +0000

Dude! This just solved my problem! Been an IIS user forever; just installed Apache for the first time and it couldn’t bind to port 80. Thank you kindly.

By: Dr.Arun Kumae Sinha

Dr.Arun Kumae Sinha — Wed, 24 Mar 2010 12:08:52 +0000

Google also uses this port very frequently if you are using chrome

By: How to Kill Process that is Running on Certain Port in Windows? | Grady Laksmono

Wed, 02 Dec 2009 09:02:04 +0000

[...] Reference: http://ma.tt/2006/10/windows-tip/ [...]

By: Daniel

Daniel — Fri, 11 Jul 2008 04:38:44 +0000

You are not only a genius with WP, but this was great information. I did find that under Skype’s setup, under the Advanced area, there is a checkbox that tells it to use ports 80 and 443 as alternates. I unchecked that, and my conflict was gone.

By: Roshan Bhattarai

Roshan Bhattarai — Mon, 19 May 2008 17:11:11 +0000

Thanks a lot for this tips , I was using skype and then tried to start apache it didn’t work.I even re-installed apache once …

Thanks for your tips…

By: Damn, why the hell skype is blocking port 80? « The Storyteller

Damn, why the hell skype is blocking port 80? « The Storyteller — Wed, 27 Jun 2007 18:37:22 +0000

[...] I followed the steps Matt suggested in his blog post – I applied the following command at [...]

By: < The Fire Within Me > » Blog Archive » Skype en el puerto 80

< The Fire Within Me > » Blog Archive » Skype en el puerto 80 — Mon, 28 May 2007 04:45:19 +0000

[...] Google, encontrÃ© que Matthew Mullenweg en su sitio hacÃa referencia al mismo problema en su post Windows Tip y que lo habÃa diagnosticado Ãºnicamente con herramientas de Windows XP y me mas pareciÃ³ [...]

By: Ramas. » links for 2006-10-15

Ramas. » links for 2006-10-15 — Sun, 15 Oct 2006 15:19:13 +0000

[...] Photo Matt Â» Windows Tip Un tip de Windows bastante mono. El uso de la command line para averiguar que pasa con tu mÃ¡quina. Esto es Ãºtil si se me atora la conexiÃ³n de internet. (tags: windows tips aplicaciones puertos) [...]

By: Ken McGuire

Ken McGuire — Sat, 14 Oct 2006 13:12:56 +0000

Its a handy tip to know. Discovered it a while back having installed apache after skype though my method was a little bit more like “lets end this, see if that fixes it” while going down through taskman.

By: Les

Les — Sat, 14 Oct 2006 08:56:36 +0000

For those unimpressed with the Windows command line[1], you might like to see its future incarnation, called Powershell. It's taken a lot of inspiration from Unix and other sources. Even has built in documentation more like man pages than the usual MS help. [1] Though for those of us who worked through from early versions of DOS, it's a powerful tool...

By: Diego

Diego — Sat, 14 Oct 2006 04:56:47 +0000

Google talk uses port 80 too, but i think you can change that in some option around there…

By: Shahab

Shahab — Sat, 14 Oct 2006 02:22:32 +0000

Or you may use Process Explorer from Sysinternals. On the TCP IP tab it will show what connections a process is using and you can kill it from there.

By: Olivier

Olivier — Fri, 13 Oct 2006 19:47:49 +0000

I got ethe same problem… I know that Skype is using the port 80 to perform firewall traversal however, I was wandering if it is possible to enforce skype not to listen all interface (0.0.0.0:80) but only the web connected interface (leaving free 127.0.0.1:80).

In that case, it does not remove the firewall traversal feature of skype (which we all agree is great) and allows you to have a local webserver to experiment your blog for example on the localhost…

I asked on a Skype board but didn’t get any answer so far…

By: Lloyd D Budd

Lloyd D Budd — Fri, 13 Oct 2006 17:57:24 +0000

You almost make it seem easy Very tools for my box of tricks.

By: Erica Douglass

Erica Douglass — Fri, 13 Oct 2006 17:35:24 +0000

Skype was listening on port 80 because it is a P2P application. That is, your computer serves data for other Skype users as long as you leave the client open. (That's why it wants to start when you start up your computer.) This is why some places, like San Jose State, want to ban Skype. One of the reasons eBay felt that Skype was worth so much money because despite carrying millions of calls, its own servers carry very little traffic. They depend on folks who leave the app open to carry calls for everyone. Thus, their monthly outgoing cash flow is fairly reasonable (unlike YouTube, which spends millions of dollars every month on bandwidth!)

By: Deepu Sudhakar

Deepu Sudhakar — Fri, 13 Oct 2006 16:55:07 +0000

By default, Skype listens to port 80 and 443 as alternative incoming ports. So when viewing your localhost, the request gets intercepted by Skype.

Solution: Go to the “Connections” tab in the Skype options, and uncheck “Use port 80 and 443 as alternative incoming connections”.

By: jarv

jarv — Fri, 13 Oct 2006 16:11:56 +0000

as for skype – tools/options/connection (i hope I get it right, cause I’m using polish version of skype…) – there is a checkbox which sets skype to use ports 80 & 443 as an alternative to incoming connections.

just turn it off – and your local webserver will rock.

had the same problem once – I used TcpView from SysInternals which propably doeas the same what calling netstat doeas.

By: Scott Johnston

Scott Johnston — Fri, 13 Oct 2006 14:52:47 +0000

This surprised me as well. But I figured out how to turn it off.

http://www.happyinwater.com/life/archives/2006/03/08/skype-desktop-sharing-port-80/

By: Hoboken411

Hoboken411 — Fri, 13 Oct 2006 14:41:42 +0000

This is so ironic that you mentioned Skype. I wonder if they’re having problems. Mine just locked up, and Skype had indicated they were having trouble connecting to their communications server. I rebooted, and things are now fine. Perhaps there’s a security leak in their client?

By: Marcus

Marcus — Fri, 13 Oct 2006 13:03:00 +0000

You can disable that in the Skype options (connection)
Port 80 is somehow supposed to prevent NAT-problems, or so, i honestly don’t know.

By: Michael Buckbee

Michael Buckbee — Fri, 13 Oct 2006 12:30:13 +0000

Matt,

I had the same problem with Skype. Apparently it uses ports 80 and 443 as “alternatives for incoming connections”. I’m thinking this makes it easier to slip their traffic through firewalls.

There’s a checkbox to disable this under Options > Connections.

Thanks.

By: Stephen Pierzchala

Stephen Pierzchala — Fri, 13 Oct 2006 11:24:39 +0000

Matt:

If Skype can’t establish a connection though its designated ports (whatever those are), the fallback position is to use ports 80 and 443. Says so right in the configuration/preferences.

smp

By: Johan

Johan — Fri, 13 Oct 2006 11:05:30 +0000

It might have something to do with the ‘Allow my status to be shown on the web’ option (you can find this under options – privacy).

You could try to change this setting to see if this resolves your problem?

By: drac

drac — Fri, 13 Oct 2006 10:40:42 +0000

Or you could use TCPView. The Sysinternals tools are worth installing on a notebook, even if this way works just as well. Skype does listen to 80 and occasionally 443 as well. I theorize this is to allow someone behind a firewall to use you as a relay (did I mean supernode?). I unchecked the tickbox in Skype options that allows it to grab port 80 though - that lets me run XAMPP on the notebook while still having Skype on.