(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443

Skaperen · 03-30-2010, 10:58 AM

You should start your own thread instead of leeching one that is 6+ years old.

javahaxxor · 03-31-2010, 02:49 AM

so apache is trying to bind port 443 and that port is already in use.

do a "sudo lsof | grep TCP" and see which application is keeping that port open. It can be a torrent program, skype, or a number of applications which work over http

cby016 · 03-08-2011, 12:29 PM

Quote:

Originally Posted by pcKILLER

i am running rh9
i had exactly the same problem
....
the solution was that the tux service was running
tux is a web server

stop that service and it will work!!!!

it worked for me!

Thanks pcKILLER this fixed it for me.

dontreplay1AtHtmilDotCom · 07-09-2011, 07:45 PM

GUYS... i got the best ide of solving it.. its maybe skype.. download "Wamp" and go to (RightClick On Wamp Icon Down>Apache>Servise>Test Port 80) it will tell u if its used or not.. try my way.. it may help and if did help. subscribe to me if you want by going to Youtube.com/FinshFlash ^^ GoodLuck

Shm00nix · 11-30-2011, 03:08 PM

In my case, I had thoughtlessly installed the 'nginx' server on my Ubuntu system -- which then grabbed the 127.0.0.1:80 port from apache2.

When I changed /etc/apache2/ports.conf values of
NameVirtualHost *:80
Listen 80

to

NameVirtualHost *:8080
Listen 8080

and got apache2 started, both servers were then up: nginx at 127.0.0.1:80 and apache2 at 127.0.0.1:8080

So I simply uninstalled nginx (also nginx-full and nginx-common) -- and set /etc/apache2/ports.conf port values back to default. Apache is now at 127.0.0.1:80. Knock on wood.