>> I can't see how having a private IP address would result in the admin
>> server throwing errors that appear to be about PHP not being able to
>> open shared object files.
>
>
> Personally, I once installed a 32bit version@private IP with no problems.
>
> But, there were several posts in the past, some of them by Brian from
> Nuonce, I think,
> that warned against installing with private IP because it could break
> Apache.
> Thought, it could be your case.
There is nothing wrong with running private IPs on your BlueQuartz box. I
have a slew at home, and a couple that are reachable from the outside
world using PAT. Never an issue.
Private IP will NEVER break Apache!!!
NOW, what will break it is a shitty firewall that re-writes the HTTP
header incorrectly. Per HTTP spec, the header should include the hostname
of the virtual site your wanting to connect to.
That is how it is possible to run 20-200 sites on a single IP, and why it
is impossible to run SSL the same way.
If the firewall doing the NAT removes the HTTP header, the server gets it
and has no idea what to do, it will try to use the default virtual site
instead, which usually results in some crazy content and the developer
saying WTF.
A proper firewall doesn't change the header, just re-writes IP
address/port, and forwards in, and then Apache answers the call and
responds with the content.
Just my two cents for the day!
Brian
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.