Browsers usually think port 80 is for http, port 8080 is alternate http and port 127 is typically a LOCUS connection server port (per IANA.org). To get browsers to feed http over a weird port, go to iana.org and pick an un-spoken-for port.

Normally if apache has no idea what to feed and is set up to grok and use an unusualy port which matches the router port, you will get the Apache test page. Gettign nothing is typically a router<->Apache port mismatch as Apache is listening on what you told it but that is not what the router is using to NAT things to.

Normally, BOTH should be set to 8080 if this is a legit server. and make sure the router is not talijng to its own NIC using 127.0.0.1 please (this is not a flame, typical newer user thinks that the Lin-box or BSD-Box's default 127.0.0.1 is a real IP-- but not so, it is a loopback port for the NIC local to whatever is told to use that IP (if you program that into a router as an outbound IP, router will happily loop test port all day, ROUTE zilch out of itself, and outsiders will get no messages whatsoever that browser can find or display as router thinks it is testing ITSELF and says zilch\nada\zip\zero to browser that is browsing in unless browser is coming in through admin login).

So, could be BOTH, also could be just router or just Apache. Note, server needs either a proxy server or a STATIC IP plus NAT to be at all secure and to serve correctly. I would also take a server OFF a hub if at all possible and connect to router.

John Danielson