IP Port 80

[Bruce Marshall]

On Thursday 18 May 2006 05:42 pm, Net Llama! wrote:
> On Thu, 18 May 2006, Rick Sivernell wrote:
> >    Yes, it has gotten complicated, far too much so. I have a DLink 624
> > FIOS Router, not much different than a regular one, set Web Derver HTTP
> > to public 443 private 80 & enabled all the time. Reset #WebServer to
> > port 80, verified by netsta -an | grep 80. Used a net tool to verify
> > port open, http://www.canyouseeme.org/ and get:
> >
> > Error: I could not see your service on 71.252.218.20 on port (443)
> > Reason: Connection refused
>
> Rick, that's not what Brad was suggesting.  I'm still not at all clear on
> what a webserver on a router has to do with any of this.
>

If he has a router in place, he would need a forwarding entry in the router to 
forward incoming  request (port 80 or other) to the machine on his LAN that 
is to handle the request.



> 0) Disable all port forwarding on your router, domain hosting server, and
> anywhere else.
> 1) Force apache to listen on port 8080
> 2) Try to connect to your website on port 8080
>
> If you can't get that working then either your ISP is blocking port 8080,
> or something else is broken in your environment.
>
> > This looks like my ISP has all blocked and lets in based on some rule.
> >
> > I may be wrong.
>
> I thought that was already established (by you)?