Aral Balkan

Up until recently, I had no trouble running Apache on my development machine. Then, one day, seemingly out-of-the-blue, Apache started complaining that it could not bind to port 80. This one almost drove me crazy until I found out Skype was grabbing the port and being very stingy with it. In case you have Skype running and Apache won't start, exit Skype, run Apache and then run Skype. (If Apache already has port 80, Skype doesn't complain.)

Comments

• I also found Skype doing this and after a bit of googling found out it has been a bit of an issue with any web server people run locally. My question is however why does skype bind to port 80 (or other ports?) and what hidden security risks could this pose? After all block certain IP ranges and skype's functionality starts to vanish even for IP ranges allowed by you, with multiple connections to various places I'm starting to feel a little uncomfortable with the whole "skype" idea.

  by Etienne on 2007-01-27 16:43:04

• uyhyhxkj kll l; ,;ckxdlxxmxwmjdfskuifdfgg

  by bilal on 2008-08-07 19:02:55