• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Home Server problem

x04d DaY

Senior member
I assume this is the right place, even though it's apache.

Well, I'm running the latest version of Apache on my system. The other night, my server was runnign just fine on my ip address, then the morning after, it wouldn't connect. I could still connect on localhost and 127.0.0.1, and no changes were made to my firewall/router. I assumed there was a problem with apache itself, so I re-installed, to no avail. The problem persists, and now I'm left with a relatively useless server.

My question is : What could have done this? Could my ISP have blocked my post 80?

Thanks for whatever help you can give me, it's appreciated.
 
what OS, What version of apache. Any changes made to the machine recently (OS Updates, S/W updates, etc). What firewall, ISP, router.
 
Windows XP Home, Apache2Triad 1.5.2. No changes made to the machine at all. Router : - DLink 604. ISP : - Cogeco Cable. No firewall aside from that on router.
 
if 127.0.0.1 doesn't work in a web browser then it's not an ISP issue, it's configuration on your end. S/W Firewall? XP likes to turn the F/W on for some connections randomly. netstat show you listening on port 80? Apache service is running? (the feather in the systray doesn't mean it's running)
 
I suppose my original post wasn't clear.
I can still access it via 127.0.0.1 and localhost, but not via my ip address.
When Apache isn't running, I can listen on port 80.
 
locally, you should be able to still see the server from you IP. Try changing your config to bind to port 8080 or 81 or another nonstandard port, see if that fixes it.
 
Back
Top