Apache 2.2 Problems

  • CithosSypht
  • Newbie
  • Newbie
  • User avatar
  • Posts: 7

Post 3+ Months Ago

Hello.

I am trying to get Apache 2.2 running, and for some reason unbeknownst (no this word is not obsolete!) to me it is not working.
I followed the posts located here:

mswindows-forum/apache-error-cound-not-bind-address-t31963.html

and edited my httpd.conf file such that it reads:

Listen: <ip address>:80
ServerName: <ip address>:80

The Apache2.2 service is running, according to the Apache Service Monitor. However, when I type in the URL http://localhost/ or http://127.0.0.1, I just get a big blank page instead of the Apache default welcome page. I've tried all combinations of {ip address, localhost} as values for Listen and ServerName, and it still gives me nothing. I have an AVG firewall installed and is currently allowing httpd.exe and ApacheMonitor.exe through.

I don't know if I missed something really obvious, as I'm new to the whole webserver thing. Any help would be greatly appreciated.
  • grinch2171
  • Moderator
  • Genius
  • User avatar
  • Posts: 6810
  • Loc: Martinsburg, WV

Post 3+ Months Ago

Did you follow this as well

http://httpd.apache.org/docs/2.1/platform/windows.html

Your httpd.conf file should read:
Code: [ Select ]
Listen: localhost:80
ServerName: localhost:80
  1. Listen: localhost:80
  2. ServerName: localhost:80
  • CithosSypht
  • Newbie
  • Newbie
  • User avatar
  • Posts: 7

Post 3+ Months Ago

I followed the installation instructions on the site, yes. I am unsure as to what to do about this statement, however:

Warning: The server configuration file is reread when a new child process is started. If you have modified httpd.conf, the new child may not start or you may receive unexpected results.

I uninstalled Apache, deleted the files, and reinstalled it:

Network Domain: blahblah.blah
Server Name: MyPCName-PC.blahblah.blah
Email Address: myemail@blahblah.blah
Installation Type: Typical
Path Name: (Default)

As it installed the Apache2.2 service, I got the error "Could not bind to addresss 0.0.0.:80," which as I understand results from a
Listen: 80 statement
that is the default value in httpd.conf.

I ended the service, edited the Listen to be localhost:80, restarted the service, and that's how I got Apache2.2 running in the first place. It results in a blank page.

I stopped the service, edited the Servername to be localhost:80 in addition to the above. I started the service. It results in a blank page.

Looking through the guide, I don't see anything regarding this situation, though I may have missed it.
  • Bigwebmaster
  • Site Admin
  • Site Admin
  • User avatar
  • Posts: 9092
  • Loc: Seattle, WA & Phoenix, AZ

Post 3+ Months Ago

When you say blank page, is it literally just a white page that was served? Meaning it wasn't a 404 error, or 501 error, 403 error, etc? If that is the case it sounds like something is working, just not pointing to any files to be served maybe. Did you check the DocumentRoot path to make sure something actually exists there?

If it is timing out though than that is a different story and would sound like Apache is not listening on the port yet.
  • CithosSypht
  • Newbie
  • Newbie
  • User avatar
  • Posts: 7

Post 3+ Months Ago

It is a white page, yes, not a 404 error, which is why I'm confused.
The DocumentRoot is the following:

C:/Program Files/Apache Software Foundation/Apache2.2/htdocs

This does indeed contain the index.html file:
file:///C:/Program%20Files/Apache%20Software%20Foundation/Apache2.2/htdocs/index.html

In it's simple HTML source code:
<html><body><h1>It works!</h1></body></html>

Except, of course, that it doesn't. >_<
  • SpooF
  • ٩๏̯͡๏۶
  • Bronze Member
  • User avatar
  • Posts: 3422
  • Loc: Richland, WA

Post 3+ Months Ago

Have you checked your apache logs?
  • CithosSypht
  • Newbie
  • Newbie
  • User avatar
  • Posts: 7

Post 3+ Months Ago

[Thu Jul 01 12:21:57 2010] [notice] Apache/2.2.15 (Win32) configured -- resuming normal operations
[Thu Jul 01 12:21:57 2010] [notice] Server built: Mar 4 2010 11:27:46
[Thu Jul 01 12:21:57 2010] [notice] Parent: Created child process 3912
[Thu Jul 01 12:21:57 2010] [notice] Child 3912: Child process is running
[Thu Jul 01 12:21:57 2010] [notice] Child 3912: Acquired the start mutex.
[Thu Jul 01 12:21:57 2010] [notice] Child 3912: Starting 64 worker threads.
[Thu Jul 01 12:21:57 2010] [notice] Child 3912: Starting thread to listen on port 80.
[Thu Jul 01 12:32:15 2010] [error] [client 127.0.0.1] File does not exist: C:/Program Files/Apache Software Foundation/Apache2.2/htdocs/favicon.ico

I did, but I had missed that error before.

Access Log:
127.0.0.1 - - [01/Jul/2010:12:32:15 -0400] "GET /favicon.ico HTTP/1.1" 404 209

I'm afraid I have no idea what favicon.ico is, nor why its tying to find it.
  • grinch2171
  • Moderator
  • Genius
  • User avatar
  • Posts: 6810
  • Loc: Martinsburg, WV

Post 3+ Months Ago

All a favicon is, is the little graphic that appears in your web browser address bar, it isn't a big deal that it can't find it.
  • CithosSypht
  • Newbie
  • Newbie
  • User avatar
  • Posts: 7

Post 3+ Months Ago

Ah, well, so much for that solving the problem. Nice to know though.
  • joebert
  • Fart Bubbles
  • Genius
  • User avatar
  • Posts: 13504
  • Loc: Florida

Post 3+ Months Ago

Is there anything other than the request for favicon.ico in your access log ?
  • CithosSypht
  • Newbie
  • Newbie
  • User avatar
  • Posts: 7

Post 3+ Months Ago

No, that's the entire log. Or at least it was.

Tried it again, and "It Works!"

I have absolutely no idea why, as I haven't done anything since, but it's working just fine now.

Thanks for the advice everyone. I'm glad I learned some new things, and I'm sure I'll see you all around.
  • SpooF
  • ٩๏̯͡๏۶
  • Bronze Member
  • User avatar
  • Posts: 3422
  • Loc: Richland, WA

Post 3+ Months Ago

You might of forgot to restart/reload the config file after you changed something.
  • joebert
  • Fart Bubbles
  • Genius
  • User avatar
  • Posts: 13504
  • Loc: Florida

Post 3+ Months Ago

I'm dumbfounded by the request for favicon.ico being the only thing in the access log. That's one of the oddest things I've heard of in awhile.
  • SpooF
  • ٩๏̯͡๏۶
  • Bronze Member
  • User avatar
  • Posts: 3422
  • Loc: Richland, WA

Post 3+ Months Ago

If apache is configured a certain way it wont display directory listings, so if the default file isnt set correctly I would think it would just display a blank page, no errors and only the favicon would be requested.

I might have to test this out tonight.
  • Bigwebmaster
  • Site Admin
  • Site Admin
  • User avatar
  • Posts: 9092
  • Loc: Seattle, WA & Phoenix, AZ

Post 3+ Months Ago

It could also be that the blank page was stored in the cache of the browser so that when CithosSypht went back there all it did was load the favicon.ico. If they would have cleared the cache that might have been all that was needed to fix the problem at that point. That to me makes sense to why it all of a sudden randomly started working. The fact is was it was working except the browser was pulling it from the cache that was outdated in the browser.
  • joebert
  • Fart Bubbles
  • Genius
  • User avatar
  • Posts: 13504
  • Loc: Florida

Post 3+ Months Ago

Quote:
If apache is configured a certain way it wont display directory listings, so if the default file isnt set correctly I would think it would just display a blank page, no errors and only the favicon would be requested.

I might have to test this out tonight.


Sounds plausible.

It would be interesting to see what happens if mod_autoindex is left out entirely. I can't remember ever having directory indexes being unavailable in a way that didn't return a 403 Forbidden error for me.

Post Information

  • Total Posts in this topic: 16 posts
  • Users browsing this forum: No registered users and 51 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum
 
 

© 1998-2014. Ozzu® is a registered trademark of Unmelted, LLC.