Installing a local version of Apache HTTP Server should have been easy. I had done it a few times before and the process had always been a breeze. Yet, this time I was at the point of despair. Why wouldn't Apache serve me up its default page once I had installed it properly? Apache seemed to run fine, yet troubleshooting my brains out over the intricacies of my firewall had taken me nowhere. In case you too have just installed Apache 2 as a Windows console application and are now perplexed as to why nothing shows up when you type http://localhost into your browser, the answer is mind-numbingly simple: console installations of Apache are set to listen on port 8080, so you need to augment your URL with that port number. Type http://localhost:8080 into your browser. Yes, that's what you just wasted so much time over ;) I know it's a remedial oversight, but it seems that all the Apache documentation glosses over providing an explicit reminder about the port when you goto test your server. Yes, I fear it may just help to provide a tediously explicit set of documentation for people having a brain-fart day like mine.--it's like struggling to sort out a problem with your car's electrical system only to find out that you never properly checked the fuse box. If you don't have any other server installed, just pop into your .conf file and set Apache to listen on port 80. There you go, no port suffix to foul up your future days. By the way, I saw way too much of this unfortunately-named site while troubleshooting. Poor guy, yet I'm surprised some marketing-goob hadn't already planned to take advantage of his redirection trouble.