kill 1345 killed that process and then I could start a new apache2 process. –Mika Sep 3 '12 at 10:45 add a comment| 9 Answers 9 active oldest votes up vote Thank you. 0 IMsupporting February 10, 2015 By using :: you are listening to a IPv6 Loopback? Yes, I'm sure. share|improve this answer answered Sep 4 '13 at 11:13 mk_yo 3071223 add a comment| up vote 1 down vote Try this, it works for me… sudo netstat -ltnp | grep ':80' https://wiki.apache.org/httpd/CouldNotBindToAddress
If an IP address is given as well as a port, the server will listen on the given port and interface. Share your knowledge. Launch a Free* Storm Server *For new customers only Email Get Started Now Thank you. use *:80 / *:443 in your Vhosts.
It worked all just fine. sudo apt-get autoremove #After using any of the above commands, use this in order to remove dependencies used by nginx which are no longer required. Reply Log In to Comment Have another answer? Make_sock Could Not Bind To Address 80 Windows Why do manufacturers detune engines?
For some reason it seems to be starting apache2 and then hangs. Log In to Comment Leave a Comment Add comments here to get more clarity or context around a question. Reply Log In to Comment 0 sridaran September 2, 2015 I have the same issues, so please put the following on ports.conf NameVirtualHost *:80 NameVirtualHost *:443 Reply Log In to Comment http://stackoverflow.com/questions/10160339/starting-apache-fails-could-not-bind-to-address-0-0-0-080 And when you query apache2ctl for its status, it hangs.
Cancel reply ← WordPress Screencast, Part 7: Tags and Categories WordPress Screencast, Part 8: Mysteries of the MORE Tag → Proudly powered by WordPress. Make_sock: Could Not Bind To Address [::]:80 Mac more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed There seems to be some serious bugs with apache2/Ubuntu 12.10 that causes apache2 to start and hang. ccompose new post jnext post/next comment k previous post/previous comment r reply e edit o show/hide comments t go to top l go to login h show/hide help shift + esc
You only need to set the protocol if you are running on non-standard ports. http://askubuntu.com/questions/338218/why-am-i-getting-permission-denied-make-sock-could-not-bind-to-address-when share|improve this answer answered May 17 '13 at 12:23 user1004829 311 add a comment| up vote 3 down vote I had the same problem For me, apache was already running but Make_sock: Could Not Bind To Address 0.0.0.0:80 Windows Measuring Water with a Holey Cube Does having a finite number of generators with finite order imply that the group is finite? Make_sock: Could Not Bind To Address [::]:443 We'd love to hear from you.
Hope it helps. http://jessriegel.com/could-not/make-sock-could-not-bind-to-port-80.html up vote 15 down vote favorite 10 I can stop it using /etc/init.d/apache2 stop But when I want to start it again using: /etc/init.d/apache2 start I get this error: Starting web Menu Skip to content Home Login About Me Contact Facebook Twitter Google+ LinkedIn YouTube GitHub Projects my Books (on Amazon.com) my iOS Apps (external site) Disk Space Pie Chart Zen Dash Is the form "double Dutch" still used? Could Not Bind To Address 80 Windows
Please advice... Check it out: [email protected]:~$ grep -ri listen /etc/apache2 /etc/apache2/apache2.conf:# supposed to determine listening ports for incoming connections, and which /etc/apache2/apache2.conf:# Include list of ports to listen on and which to use Is it bad form to write mysterious proofs without explaining what one intends to do? Source The server will respond to requests from any of the listed addresses and ports.
On Linux/Unix run $> netstat -plant $> # or $> sudo lsof -i:80 On Windows run $> netstat -ano On Mac OS X / FreeBSD run $> netstat -Wan |grep 80 Make_sock Could Not Bind To Address 80 Ubuntu [email protected]:~# /usr/sbin/apache2ctl status **hangs until Ctrl-C is pressed. Law case title convention: Why sometimes not "Plaintiff v.
In your problem as you can see, the system through Apache2 response indicates the root of the problem ([...]could not bind to address blah blah 80): (13)Permission denied: make_sock: could not Menu Tutorials Series Common Fixes Getting Started Home Page | Knowledge Base 24 X 7 HEROIC SUPPORT 800.580.4985 (1-517-322-0434) Find Answers To Web Hosting Questions SearchSearch Error: (98)Address already in use: I have two virtual hosts configured using port 80, but Apache will not start. 13 Permission Denied Make_sock Our Heroic Support team is available 24 hours per day. 1.800.580.4985 Open a Ticket Subscribe to the Knowledge Base Subscribe to the Knowledge Base SubscribeSubscribe Products Dedicated Servers Storm Cloud Servers
Not the answer you're looking for? It did the trick for me as re-starting and killing the processes did not help at all. Defendant"? It was a Plesk server running CentOS, but this particular issue can also happen on plain LAMP stacks.
It's a bug in the apache2. How does ssh run a command? The normal boot process for apache2 is not working right. why do they give the same output?
So Ubuntu can't stop apache2 because it doesn't know where it is! Share it with others to increase its visibility and to get it answered quickly. This is often combined with the Virtual Host feature, which determines how httpd responds to different IP addresses, hostnames and ports. Sign Up Log In submit Tutorials Questions Projects Meetups Main Site DigitalOcean DigitalOcean Community Menu Tutorials Questions Projects Meetups Main Site Sign Up Log In submit View All Results By: jasper962985
So How to fix it? To check whether this is the case ps -ef | grep -E 'apache|nginx|lighttpd' You may need to add other webservers that are likely to be running on your system.