Apache :: The requested operation has failed!

pikay2k · Joined: 22 Feb 2010 Posts: 4

I have this annoying problem. Apache works fine if I put it on port 80 or 8080. The problem? It seems that my router has problems opening those ports. In fact, it seems to have a lot of problems with opening a number of ports. I found that port 443 works pretty well.

The problem is, Apache doesn't start if I set it to listen to this port. I don't know why. I've even turned my firewall off.

This shows up in my error log:

(OS 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:443
no listening sockets available, shutting down
Unable to open logs
[Mon Feb 22 02:38:42 2010] [warn] (OS 995)The I/O operation has been aborted because of either a thread exit or an application request. : winnt_accept: Asynchronous AcceptEx failed.
[Mon Feb 22 02:38:43 2010] [notice] Child 5912: Released the start mutex
[Mon Feb 22 02:38:44 2010] [notice] Child 5912: All worker threads have exited.
[Mon Feb 22 02:38:44 2010] [notice] Child 5912: Child process is exiting

James Blond

pikay2k · Joined: 22 Feb 2010 Posts: 4

Okay, thanks for that. I used a port that wasn't in use, but it seems I've run into another problem. Despite the fact that my port is open, my firewall is down (temporarily to see if that was the problem), and the port it's listening in does indeed match with the one I forwarded, my server does not appear online.

It works just fine on my local network, but it doesn't work at all when trying to get online with it.

My log:

httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.132 for ServerName
[Mon Feb 22 23:19:04 2010] [notice] Child 5732: Child process is running
[Mon Feb 22 23:19:04 2010] [notice] Child 5732: Acquired the start mutex.
[Mon Feb 22 23:19:04 2010] [notice] Child 5732: Starting 64 worker threads.
[Mon Feb 22 23:19:04 2010] [notice] Child 5732: Starting thread to listen on port 53427.

Edit - Ugh, what? I didn't chenge anything in my router settings, but for some reason when I put my IP address (not my local one) into the address bar, I get my router's control page instead of my server. Before I was able to get my server's page locally within my own network, now I'm only getting my router's control panel.

James Blond

pikay2k · Joined: 22 Feb 2010 Posts: 4

I'm using a Netgear WNDR3300, running on DD-WRT v24-sp2.

James Blond

I found a tutorial on the net for utorrent.

Check if you made the portforwarding as in the tutorial. Of couse with your port in most cases port 80.

Try if you port is open http://www.yougetsignal.com/tools/open-ports/

pikay2k · Joined: 22 Feb 2010 Posts: 4

My port was forwarded correctly, I'm not sure why it started messing up like that out of nowhere. In any case, I've decided to use my other router, since that one was slowly dying anyway.

I set it up fine, was even able to use a different port (it's on 8095 now).

Using this site, it tells me the port works fine and can see that I have Apache listening on it.

However, the problem is that my server cannot be viewed outside of my own network. If I hop onto any computer within my network, I can see my server just fine, but when I run my site on downforeveryoneorjustme.com it tells me that it's down. I double checked using a proxy, and my server is indeed down for everyone but me.

Any suggestions? My firewall and port forwarding is all configured correctly, I've even torn my firewall down temporarily to see if that was the issue.