Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

This problem has be stumped beyond belief. I have a website, hosted on CentOS, served from Apache. It has an SSL certificate installed, but the behavior exists for the SSL as well as the non-SSL side (i cleared out my .htaccess file to make sure it wasn't causing the issue).

When someone tries to access the site from outside our network (where we host our own DNS servers), they get a connection timed out error. If I upload a file (changed or not) to the site, it will become visible to the outside for a short period of time, about 5 minutes or so. I can see the site fine from inside our own network at any time, and using our own DNS servers. I can also see it from our own network using Google's DNS servers (8.8.8.8 and 8.8.4.4). The access_log and error_log files don't show the requests that fail, only the requests that are successful.

I have no idea what could be causing this, or where else to look for clues. I know I haven't given much information (configs, etc), but I don't know what information would be relevant. Any ideas? I'm hesitant to link to the site as it is an unlaunched client's site, but if it is necessary, I can either PM it or post it.

UPDATE: I also realized that when the site is timing out, I can't ping the server IP.

share|improve this question

1 Answer 1

This sounds like a network issue. You are able to access this site from the internal network - where the site is sitting, yes? - with its public IP address. It sounds like the issue is either in your firewall or in your internal networking. Verify if the firewall sees the traffic that the access_log and error_log files is missing - that should isolate if the failure is occurring on firewall or the internal network.

If it is the internal network the traffic is likely not being routed correctly for some reason. Is the server hosting this site multihomed by any chance? I've seen similar behavior when traffic is coming back with a different MAC address which bunges the routing.

share|improve this answer
    
Thanks, I'll delve into the firewall and see what is showing up there. Also, yes, I can access it all the time from the internal network with the public IP (which is resolving correctly via DNS). –  Brett F. Nov 7 '11 at 20:52

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.