• 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.

>nevermind, got it<

F

flippinfleck

Golden Member
Port 80 has been blocked by Verizon. All incoming requests for that port will be ignored. No eta for the re-opening of that port, only time will tell.
 
Well, the thing that sucks is that I am not having any trouble accessing it. Should I try using my other computer (with a dial up modem) to check it? Or would that still come in as being on the same lan...

Either way, ^bump^

I looked through the access logs and error logs, but didn't see anything out of the ordinary.
 
Who is providing your dsl? Where do the traceroutes stop when they try to get to your site? What happend when the router is taken out of the picture?

EDIT: the url you gave us resolves to 63.64.164.91. That ip is running IIS 5.0.
 
DSL is provided through Verizon.

Total of 15 hops on the tracert and last stop is 63.64.164.91 which is deerfield communications. That's dns2go.

But this is all pretty moot right now. I changed the port that apache should listen to, and now it works. The settings for the router were also changed to match what Apache is doing.

Could it be that they blocked port 80 on me?
 
Ok, update. Verizon has blocked ALL incoming requests for port80 for ALL of it's users. I am guessing that this is in response to C.R.

Oh well, I can live without for now. I will just have dns2go forward all requests to a dif port.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top