Karl Cunningham wrote: > On 5/28/2008 12:52 PM, herb Kornfeld wrote: > > I hope this helps >> Set up: >> I do want my webserver connected to the world. I have my cable modem >> connected to my router. The router is connected to the linux box. I >> configured the router to set the linux box's IP address to be in the >> DMZ (I assume this opens up the ports). I have other devices >> connected to the router as well. >> Step1: When outside of my home and away from my private network I >> open a browser and type in the public IP of my home system 76.88... >> and the standard Apache Fedora test page displays on the browser (yay, >> just as I expected). >> Step2: I have my wordpress blog located at http://76.88..../wordpress >> and when I try to access it, the browser trys to open the private IP >> address of my webserver 192.168.... instead of the public IP >> 76.88.../wordpress . I am a newbie and don't understand why it seems >> to try and redirect the request. > > I just tried to access the wordpress page (using the full IP from the > first email). I hope this was ok. I used wget, a command-line program to > grab web pages. It returned the following: > > $ wget http://76.88..../wordpress > --2008-05-28 14:11:20-- http://76.88..../wordpress > Connecting to 76.88....:80... connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: http://76.88..../wordpress/ [following] > --2008-05-28 14:11:20-- http://76.88..../wordpress/ > Connecting to 76.88....:80... connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: http://192.168..../wordpress/ [following] > --2008-05-28 14:11:20-- http://192.168..../wordpress/ > Connecting to 192.168....:80... failed: No route to host. > > Apparently Apache is returning a 301 error and the browser is faithfully > trying to go to the new (private) IP, and naturally failing. I don't > know why it takes two tries to get the private IP returned. > > My experience with Apache is very limited, and zero with wordpress. > Perhaps someone more up on these can help.
So, it sounds like apache is misconfigured, eh? The localhost test I proposed, probably even works (since it would be running on that redirected IP). Nevertheless that test would still be good for verifying that wordpress works. Time to look at what wordpress did to apache when it was installed. Maybe I'll try installing it and see how it does its configuration. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
