Ubuntu
apache2 package

apache2 301 response and port forwarding

Asked by Matthew H McKenzie on 2012-02-23

Clean Oneiric 64 server install as SSH+LAMP. Webmin amd PHPMyadmin.

Apache2 is version 2.2.20-1ubuntu1.2

Site is accessible from console as http://localhost from elinks.
Site is accessible from LAN as http://192.180.0.108.

Using public port 8091 to private port 80.

http://public:8091/phpmyadmin works.... (stock alias).

but http://public:8091 does not (expected to find /var/www) and bounces to http://public

125.253.3.57 - - [23/Feb/2012:08:45:46 +1100] "GET / HTTP/1.1" 301 404 "-" "Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0) Gecko/20100101 Firefox/10.0"

nnn.nnn.nnn.nnn - - [23/Feb/2012:10:59:22 +1100] "GET / HTTP/1.1" 301 360 "-" "Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1"

It's more of an Apache question, but is is a clean install. Does anyone recognise this ? Is the 301 a red herring ?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu apache2 Edit question
Assignee:
No assignee Edit question
Solved by:
Matthew H McKenzie
Solved:
2012-02-25
Last query:
2012-02-25
Last reply:
Matthew H McKenzie (f-launchpad-swellhunter-org) said : #2

I will go back and re-install again, but this time with no SSH, and no LAMP.
Installing only APACHE2, I will test "It Works !".
This should work out of the box, if not I will post my observations, I do not think this is a cache issue, nor do I suspect the package maintainer. I am hitting this with a few clients too.

Matthew H McKenzie (f-launchpad-swellhunter-org) said : #3

OK, this is functioning as expected. This is a similar problem to that created by placing "wordpress" behind NAT, pre-processed addresses that do not take into account public and private not being the same.
No issue with Apache, no issue with PMA.