 | 
June 5th, 2007, 01:48 PM
| | Newbie | | Join Date: Jun 2007
Posts: 5
| |  Apache with vista
hey guys, i'm currently using the newest version of apache with vista business. after finishing installing, it pops up an error msg saying that i must change my httpd config before using the service. it also prompts a small error msg box.
when i try to manually start the apache service, it says <0S 10048> Only one usage of each socket address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down.
when i try to click on Monitor Apache Servers, it juz prompts the same small error msg box.
but when i tried going http://localhost/, it actually works.
and everytime when i turn on my com, the same small error msg box appears.
can anyone help?
|
June 5th, 2007, 03:53 PM
|  | Site Moderator | | Join Date: Jan 2007 Location: Maine, USA Age: 25
Posts: 2,896
| |
It sounds like Apache is trying to start twice. I am not sure why this would happen, the only way I could think of getting this to happen is to enable it as a service AND put a shortcut in the Startup/Registry Run. In XP you could check for multiple occurrences of Apache with msconfig, but I am not sure with Vista.
|
June 6th, 2007, 02:50 AM
| | Newbie | | Join Date: Jun 2007
Posts: 5
| |
isit because IIS is running?
|
June 6th, 2007, 02:51 AM
| | Site Moderator | | Join Date: Jan 2007 Location: Maine, USA Age: 25
Posts: 2,896
| |
Quote: |
Originally Posted by ljudgementl isit because IIS is running? | Good question! I completely missed that option when I was thinking about this.
|
June 6th, 2007, 06:40 AM
| | Administrator | | Join Date: Sep 2006
Posts: 11,312
| |
Quote: |
Originally Posted by ljudgementl hey guys, i'm currently using the newest version of apache with vista business. after finishing installing, it pops up an error msg saying that i must change my httpd config before using the service. it also prompts a small error msg box.
when i try to manually start the apache service, it says <0S 10048> Only one usage of each socket address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down.
when i try to click on Monitor Apache Servers, it juz prompts the same small error msg box.
but when i tried going http://localhost/, it actually works.
and everytime when i turn on my com, the same small error msg box appears.
can anyone help? | Maybe if you change the port ...
|
June 10th, 2007, 01:23 PM
| | Newbie | | Join Date: Jun 2007
Posts: 5
| |
how do u change the port? sorry trying to learn here =)
|
June 10th, 2007, 10:36 PM
| | Site Moderator | | Join Date: Jan 2007 Location: Maine, USA Age: 25
Posts: 2,896
| |
Quote: |
Originally Posted by ljudgementl how do u change the port? sorry trying to learn here =) | You will not want to change the port until you determine that there is another web server already running on your machine.
|
June 12th, 2007, 07:34 AM
| | Administrator | | Join Date: Sep 2006
Posts: 11,312
| |
Quote: |
Originally Posted by ljudgementl how do u change the port? sorry trying to learn here =) | I just installed on vista and got the same message. IIS is running alright. I changed the port to 8081 by changing the Listen line in the httpd.conf file.
|
June 13th, 2007, 02:49 PM
| | Newbie | | Join Date: Jun 2007
Posts: 5
| |
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80 <---- this line? or
Listen 80 <---- this?
|
June 13th, 2007, 02:59 PM
| | Administrator | | Join Date: Sep 2006
Posts: 11,312
| |
Quote: |
Originally Posted by ljudgementl # Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80 <---- this line? or
Listen 80 <---- this? | The second line. The first line is an example, that's why it's commented out with the # .
|
June 15th, 2007, 03:14 PM
| | Newbie | | Join Date: Jun 2007
Posts: 5
| |
yea, it works after changing the port to 8081. but problems start arising one after another. arghh! everytime i boot up my laptop, there is this small pop up error box whenever apache starts automatically i think.
Also, the testing of localhost works when i was having the error of manually starting apache. after changing to 8081, localhost doesnt work anymore =(
|
June 15th, 2007, 03:24 PM
| | Site Moderator | | Join Date: Jan 2007 Location: Maine, USA Age: 25
Posts: 2,896
| |
Quote: |
Originally Posted by ljudgementl yea, it works after changing the port to 8081. but problems start arising one after another. arghh! everytime i boot up my laptop, there is this small pop up error box whenever apache starts automatically i think.
Also, the testing of localhost works when i was having the error of manually starting apache. after changing to 8081, localhost doesnt work anymore =( | Rather than change your Apache port, why not disable IIS (if this is what you have concluded was taking up port 80)?
|
June 15th, 2007, 03:29 PM
| | Administrator | | Join Date: Sep 2006
Posts: 11,312
| |
Quote: |
Originally Posted by Motoma Rather than change your Apache port, why not disable IIS (if this is what you have concluded was taking up port 80)? | Also I don't recommend installing Apache as a service that starts automatically, but then that's just me ...
|
June 15th, 2007, 03:35 PM
| | Site Moderator | | Join Date: Jan 2007 Location: Maine, USA Age: 25
Posts: 2,896
| |
Quote: |
Originally Posted by r035198x Also I don't recommend installing Apache as a service that starts automatically, but then that's just me ... | Oh? Why do you recommend against this?
|
June 15th, 2007, 03:53 PM
| | Administrator | | Join Date: Sep 2006
Posts: 11,312
| |
Quote: |
Originally Posted by Motoma Oh? Why do you recommend against this? | Generally I want to manually open ports as much as possible not have some programs open ports for themselves "behind my back". From their installation instructions
"
Select for All Users, on Port 80, as a Service - Recommended if you'd like your new Apache to listen at port 80 for incoming traffic. It will run as a service (that is, Apache will run even if no one is logged in on the server at the moment) Select only for the Current User, on Port 8080, when started Manually if you'd like to install Apache for your personal experimenting or if you already have another WWW server running on port 80."
You don't want to have a port open that you are not using.
My bet is that it is possible for this open port to be manipulated by ...
|
June 15th, 2007, 03:59 PM
| | Site Moderator | | Join Date: Jan 2007 Location: Maine, USA Age: 25
Posts: 2,896
| |
Quote: |
Originally Posted by r035198x Generally I want to manually open ports as much as possible not have some programs open ports for themselves "behind my back". From their installation instructions
"
Select for All Users, on Port 80, as a Service - Recommended if you'd like your new Apache to listen at port 80 for incoming traffic. It will run as a service (that is, Apache will run even if no one is logged in on the server at the moment) Select only for the Current User, on Port 8080, when started Manually if you'd like to install Apache for your personal experimenting or if you already have another WWW server running on port 80."
You don't want to have a port open that you are not using.
My bet is that it is possible for this open port to be manipulated by ... | Completely understandable. If I were to paraphrase, your position would be, "Only install as a service if you intend your machine to be a web server; running Apache as a service on your desktop places both an unnecessary risk, and additional computation on your personal computer."
 |
June 16th, 2007, 07:13 AM
| | Administrator | | Join Date: Sep 2006
Posts: 11,312
| |
Quote: |
Originally Posted by Motoma Completely understandable. If I were to paraphrase, your position would be, "Only install as a service if you intend your machine to be a web server; running Apache as a service on your desktop places both an unnecessary risk, and additional computation on your personal computer." |
I'm not good at paraphrasing so I'll accept that.
|
September 13th, 2007, 09:24 AM
| | Newbie | | Join Date: Jul 2006
Posts: 3
| |
Hello,
I've managed to get Apache running under Vista. If I type in http://localhost, I get the "It works!" page fine.
My problem is that PHP files aren't being executed - if I type in test.php, it will just dump the source code of the file into the browser.
Any idea what I'm doing wrong?
|
September 13th, 2007, 09:28 AM
| | Newbie | | Join Date: Jul 2006
Posts: 3
| |
Quote: |
Originally Posted by wildthing4ever Hello,
I've managed to get Apache running under Vista. If I type in http://localhost, I get the "It works!" page fine.
My problem is that PHP files aren't being executed - if I type in test.php, it will just dump the source code of the file into the browser.
Any idea what I'm doing wrong? | How silly of me! Apache's just the web server - I need to install the PHP module!
In fact, I'll just install PHP and use it with IIS 7!
|
December 11th, 2007, 05:00 PM
| | Newbie | | Join Date: Dec 2007
Posts: 2
| |
My new OS is Vista Business. I had IIS on XPpro and it worked fine. On Vista, IIS wouldn't work. I downloaded the latest Apache .msi and installed it. My problem is that my web site is visible when Windows Firewall is turned off, but is invisible when turned on. I can't seem to find the way to get past the firewall. Thanks, Don
|
December 11th, 2007, 05:13 PM
| | Newbie | | Join Date: Dec 2007
Posts: 2
| |
To install Apache, I downloaded the latest .msi file. I double clicked it and it installed without any problem. I didn't have to go through the command line.
Don
|
January 4th, 2008, 06:09 PM
| | Newbie | | Join Date: Jan 2008
Posts: 1
| |
Quote: |
On Vista, IIS wouldn't work.
| I encountered the same problem a while ago with my IIS6 (Vista). I did what's on this site and it worked. http://www.howtogeek.com/howto/windo...windows-vista/
Hope this help,
Matt
|
February 1st, 2008, 06:18 PM
| | Newbie | | Join Date: Feb 2008
Posts: 1
| |
Does anyone know how to disable IIS on Vista so it doesn't listen on port 80???
|
February 2nd, 2008, 11:13 PM
| | Newbie | | Join Date: Feb 2008 Location: cali
Posts: 1
| |
Quote: |
Originally Posted by Emms Does anyone know how to disable IIS on Vista so it doesn't listen on port 80??? | Just "upgraded" to vista since a zune update and intel wirless driver update from windows update corrupted my laptop.
Anyways, you can either uninstall iis, reverse steps from the link above your request, or "edit bindings" in iis to listen on a different port. Comp management->Services-> IIS -> default web site (or whatever you named your web site) -> right click and select edit bindings. Change the port IIS uses (80 for web by default).
This is useful for the initial install of apache to make life easier using the msi. Then you can change apaches ports (Listen: port), and move iis back if you want.
if you tell apache to install as a service, you can later edit the service startup to manual, or start automatically. Then the apache monitor can start it with a simple right click of the task bar apache monitor icon. otherwise, you will have to start apache manually and have a command window open as the daemon runs (Apache service, in *nix everything is a daemon instead of a service).
Just what I find easier. Then I know what is running, and get the ease of use of point and click.
|
July 6th, 2008, 01:30 PM
| | Newbie | | Join Date: Jul 2008 Location: Scotland
Posts: 1
| |
Have had no end of problems running Apache (within WAMP-Server 2) - on my laptop (Vista).
Could not run PHPMyAdmin - 404 errors.
Eventually found out about the PORT 80 thingy - changed Apache to listen on 8080 - and presto Apache worked - but not "PMA"
So back again - this morning I just by chance hit the combination 'ii' when I was searching for a competely diffferent set of files and Hey Presto at the top of the list of programs up pops "Internet Information Manager IIS" opened it up and there found a Default Database "Binding 80" changed that to 8080 and the rest is History.
All working fine - now all I have to do is learn how to develop a web served database using WAMP Server 2 (which comes with II7 anyway) see you all in about ten years.
BachStrad
| |
Posting Rules
| You may not post new threads You may not post replies You may not post attachments You may not edit your posts
HTML code is Off | | |
| | | What is Bytes?
We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights.
Get the best answers to your questions from over network members.
|
