Make_sock Error
Contents |
have one accepted answer. Are you sure you want to replace the current answer with this one? Yes, I'm sure. Changed your mind? You previously marked this answer as accepted. Are you sure you want
Make_sock: Could Not Bind To Address [::]:80
to unaccept it? Yes, I'm sure. Sign Up Log In submit Tutorials Questions Projects make_sock: could not bind to address 0.0.0.0:80 windows Meetups Main Site logo-horizontal DigitalOcean Community Menu Tutorials Questions Projects Meetups Main Site Sign Up Log In submit View All Results By:
Make_sock Could Not Bind To Address No Listening Sockets Available Shutting Down
jasper962985 Subscribe Subscribed Share 1 (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 - error February 10, 2015 42.1k views Hello, Being a novice on configuring Apache servers I managed to get ah00072: make_sock: could not bind to address [::]:443 + windows my droplet up and running and have two domains pointing to it. Made my own virtual host files using the given tutorials, DNS all figured out...great! It worked all just fine. But now I cannot reach my two domain anymore and when I restart Apache using terminal (sudo service apache2 restart) I get this error: Restarting web server apache2 AH00548: NameVirtualHost has no effect and will be removed in the next release make_sock: could not bind to address [::]:80 ubuntu /etc/apache2/sites-enabled/huizenmeteenverhaal.nl.conf:5 (98)Address already in use: AH00072: makesock: could not bind to address [::]:80 (98)Address already in use: AH00072: makesock: could not bind to address [::]:80 I googled a fair bit but got lost in all these different solutions that make my novice head spin. Any help on this...? Just can't get my head around the fact that it was al working just fine, and just stopped. 6 comments 0 jasper962985 February 10, 2015 Ok, actually got it back working by changing the .conf files in /sites-available and /sites-enabled to .config and back to .conf again. (WHY? HOW?) Really don't get that either.... If somebody is able to shed some light it would be highly appreciated. Thank you. 0 IMsupporting February 10, 2015 By using :: you are listening to a IPv6 Loopback? Anyway.. In your virtualhost, Use * and not the IP. Also, .conf is default for apache, so keep your stuff as .conf and not .config. Also at the top, listen by port and not ip and port.. use *:80 / *:443 in your Vhosts. Listen 12.34.56.78:80 Listen 80
Spelling Like Pages Local Site Map ------------------------ Rename Page Copy Page Delete Page ------------------------ My Pages Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow make_sock: could not
Fuser -k -n Tcp 80
bind to address 0.0.0.0:80 no listening sockets available There are three common ah00015: unable to open logs causes for this error message. Address is already in use Something else is already using the port
Ah00072 Make_sock Could Not Bind To Address 80 Windows
in question. Run one of the following commands to check if a running process is holding the port needed by apache open. On Linux/Unix run $> netstat -plant https://www.digitalocean.com/community/questions/98-address-already-in-use-ah00072-make_sock-could-not-bind-to-address-80-error $> # or $> sudo lsof -i:80 On Windows run $> netstat -ano On Mac OS X / FreeBSD run $> netstat -Wan |grep 80 $> # or, to get the pid $> sudo lsof -i:80Once you see these results, you can choose to kill the program in question, or change the port that Apache uses. http://wiki.apache.org/httpd/CouldNotBindToAddress If Apache (httpd, apache2, etc) is the application listening on these ports, but you can't stop it using your normal procedure, someone may have deleted the servers PidFile. The PidFile records the process ID of the parent process and is how most scripts test to see if Apache is running. You can manually stop the server by determining the PID of the parent process and sending it a SIGTERM. http://httpd.apache.org/docs/2.2/stopping.html Note for Windows users, Skype is known to use port 80. Also, make sure Windows IIS Web Server is not running. Conflicting Listen directives A configuration like this: Listen *:80 Listen 1.2.3.4:80will incur the same error message. Apache binds to *:80, and then tries to also bind on 1.2.3.4:80, which fails because it is already bound by the first line. If you're binding on *:PORT, you do not need to also bind on a specific IP. Trying to listen an IP not bound to an active interface on the server When trying to bind to an IP and
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 answers to any questions you might have Meta Discuss the workings and policies http://askubuntu.com/questions/277162/apache-fails-to-start-address-already-in-use-but-not-really of this site About Us Learn more about Stack Overflow the company Business https://kb.plesk.com/en/1507 Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question could not Anybody can answer The best answers are voted up and rise to the top Apache fails to start, Address already in use (but not really) up vote 23 down vote favorite 7 I'm trying to set up a VM running Ubuntu 12.04. I have two virtual hosts configured using port 80, but Apache will not start. I get this error: (98) Address already in use: could not bind make_sock: could not bind to address 0.0.0.0:80 The output of netstat -tulpn shows that nothing is using port 80. What could possibly be causing this? 12.04 apache2 vm share|improve this question asked Apr 2 '13 at 14:59 Gunner Barnes 124117 are you starting it as root? By default only root can open ports below 1024. –onse Apr 2 '13 at 15:02 Yes, I am. It was running at one point when I had just one virtual host configured, so I've since removed the other virtual host to try to remedy the issue, but no luck with that either. –Gunner Barnes Apr 2 '13 at 15:15 Does you host have something running on port 80 and you're in bridged mode for the guest? I don't know that it would do that, but it seems probable –RobotHumans Apr 2 '13 at 15:41 Have you tried the suggestions from Starting apache fails (could not bind to address 0.0.0.0:80)? And please also include the output of grep -ri listen /etc/apache and sudo netstat -ntlp | grep 80. –gertvdijk Apr 2 '13 at 19:57 1 grep
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base Documentation Downloads Plesk University Release notes Blog Become a Partner Russian German French Spanish Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any Search Apache cannot be started with the error "(98)Address already in use: make_sock: could not bind to address [::]:443 no listening sockets available, shutting down. Article ID: 1507, created on Oct 6, 2008, last review on Jun 15, 2014 Applies to: Plesk for Linux/Unix Synopsis All the domains stopped working. When trying to start Apache Web server, you get the following error in the console and in error_log: "(98)Address already in use: make_sock: could not bind to address [::]:443 no listening sockets available, shutting down" (It is also possible that the error discusses the 80 port.) Cause This error means that some other process already uses 443 (80) port and Apache cannot bind to it. Resolution First of all make sure that the "Listen" directive is specified only once in the Apache configuration for one port. Check the httpd.conf and conf.d/* files in order to find it (on some OS'es, SUSE Linux and /etc/apache2/* should be checked). Next, try to determine which process uses the port with the following command: /usr/sbin/lsof -i | grep http httpd 24717 apache 4u IPv6 9672930 TCP *:https (LISTEN) The above command shows that the "TCP *:https" port is used by "httpd" process with PID 24717. Look into contents of this file to find the command with which the process was started.: cat /proc/24717/cmdline /usr/sbin/httpd-kgraceful (24717 is the process' PID). If it is really an Apache (httpd) binary, then such a problem may have occurred if Apache failed to stop properly. You need to kill this process and start Apache again. If you see that some other program uses the 443/80 port, you need to find from where it was started and determine what it is, because it could be a malicious script. Here is an example where such a script was disguised: # ls -l /proc/24717/exe lrwxrwxrwx 1 apache apache 0 May 13 10:16 /proc/24717/exe -> /tmp/.www/httpd If you found a malicious script on your server it is important to find out where it came from. Unfortunately this topic is too long and is out of this article's and Parallels support scope. Search Words (98)Address already in use: make_sock: could not bind to address [::]:80 no listenin