Apache not responding to external ONLY on one VPS, even acro

[raistlinhunted]

To sum it up, I have one of my VPSs that will not respond to 80 traffic, even after a fresh OS. It has been online for months then today, boom. My 2nd new VPS today works fine.

This is a brainteaser! Details:


Sun, Nov 10 2013 8:07pm
I just rebuilt my main server hosted with you guys because I could not figure out this strange Apache issue I'm experiencing. After the rebuild, I'm having the same issue. It appeared randomly and no config changes were made prior to it appearing.

Symptoms:
1) Apache NOT responding to external request. Loading then timeout when attempting to browse FQDN associated with my VPS or direct public IP (192.223.24.79)
2) Apache IS responding to requests from localhost. Installed Lynx and executing either "lynx localhost" or "lynx 192.223.24.79" returned my website (prior to rebuild it was an actual site, now it's the "it works" page.

Troubleshooting:
1) No firewalls, ufw status = inactive. iptables - list = no rules, nothing implemented in nfoservers fw pane.

2) Other services I was hosting responded fine on the same public IP/FQDN (a game server and a TS server)

3) Numerous fixes tries including complete data backup and format of VPS. Problem still persists after fresh OS.

Exact steps taken so you know I didn't muck it up:
1) Initial install of Ubuntu 12.04LTS from your control panel.
2) Logged in, passwd to change root pw
3) apt-get update && apt-get -y upgrade
4) apt-get install apache2
5) Tested from external source to VPS FQDN and public IP - no response either
6) apt-get install lynx
7) (from vps commandline) lynx localhost = "it works", lynx 192.223.24.79 = "it works"
Had multiple personnel test from different parts of the globe - same issue no response

So what I thought was gremlins now exists outside my VPS and affects everyone, not just my personal desktop.

Since I'm testing direct IP, that rules out DNS issues.

Again, only an issue with web traffic. My other two services were working fine.

Help?

Sun, Nov 10 2013 8:17pm - answered by TimeX
In all honesty, you have covered everything I can think of and then some, though I must admit that this is not my strong area. Since this is an unmanaged VDS, software issues are better asked on our forums; there are many systems admins in the community that like to help out, and will likely be able to help you troubleshoot this problem further.


Sun, Nov 10 2013 8:37pm
This is a problem that exists with my particular VPS that does not go away with an OS wipe/install. This problem is only in THIS VPS, not Ubuntu or all your VPSs.

1) I took my 2nd VPS (the new one) and follow the exact steps above and was able to get the apache default site.

2) I once again wiped my big VPS (the old one with issues) and ONLY did "apt-get update && apt-get install apache2", and NO WEBSITE.

What could be persisting across OS wipes in this particular VPS?
Sun, Nov 10 2013 8:40pm
If you can't find anything please blow the entire VPS away from your side and reprovision me from scratch at your level.

[raistlinhunted]

Sun, Nov 10 2013 9:04pm - answered by Bill
A reinstall of the OS is the closest thing we have to a full re-provision. One thing we could try is to have you reinstall the OS, and then move you to a different machine which will reconstruct the server with your data and IPs. As TimeX said you covered your bases extremely well already, so I'm stumped as well. Please let us know how you would like to proceed.

As a completely unrelated side note, I love your email address.
Sun, Nov 10 2013 9:08pm
I've got one more thing to try that might give you more info.
Sun, Nov 10 2013 9:11pm - answered by Cody
Sounds like a plan.

Just keep us posted.
Sun, Nov 10 2013 9:16pm
Ok guys here it is: Something changed in your infrastructure in the last 12 hours that is now denying only port 80 to my IP range (at least) 192.223.24.77-80

I changed apache to port 81 and bingo! See? http://192.223.24.79:81/

Could you please provision me all new IP addresses in a completely different range until your engineers can resolve that issue?

[raistlinhunted]

For full details, see my other writeup:

http://www.nfoservers.com/forums/viewto ... 478#p51478

[kraze]

There shouldn't be anything on our end blocking it. If we were blocking it you should see a post in the events log in your control panel about it or we would of contacted you separately.

You can sure change IPs, though if you wish. Start by assigning all of the IP's you want to keep an rDNS entry and then do a change order an add a new IP. Once that is done assign an rDNS entry to the new IP and do another change order to remove the new IP. Our system will remove only the IP that doesn't have an rDNS entry.

[soja]

Is minecraftomega your site? Typing that IP in my address bar connects to http://minecraftomega.com/ and displays the forum there.


EDIT: I didn't finish reading your post, so I do see it is your site. I can connect from :80 using your old IP.

[Edge100x]

This turned out to be a glitch in the system that had caused another customer's firewall rules to be applied to raistlinhunted's virtual network adapter. The other customer had just been moved to the machine on the 10th.

The bug is fixed now, so customers should not see this happen in the future.

[raistlinhunted]

Yes sorry to follow up here. I made this post during troubleshooting before Edge100x got involved and found the gremlin.

Everything is cleared up and working great. I needed a good Linux reinstall anyways. Turns out a FW rule was being applied to my IP range from another customer and blocking only port 80 incoming.

Thanks to Edge100x and his team for a very quick and complete response to a very obscure issue at the oddest of hours. Good guys and great hosting.