|
Jacob W Anderson wrote:
>
> Hey Michael!
>
> Are you using virtual hosting on the HTTP server? If so, then you will need
> to use the real IP of the server as the virtual name. SO, say you have your
> www server on 10.75.1.11, but you are routing 216.45.234.12 as the real IP
> of www.mikesdomain.com, your config file would look something like the
> following:
>
> NameVirtualHost 10.75.1.11:80
> <VirtualHost 216.45.234.12>
> ServerAdmin foo@xxxxxxxxxxxxxxx
> DocumentRoot /home/httpd/foo
> ServerName www.mikesdomain.com
> </VirtualHost>
>
> it's ALSO important that the www servers can do a lookup on
> www.mikesdomain.com via dns, otherwise, as I found in my pursuit of a
> similar setup, the httpd reports that it's a bad domain (found out with the
> 'httpd -S' command).
http on VS-NAT is really fiendish. Maybe I'll not recommend VS-NAT as a first
setup for new users in the HOWTO anymore.
> Hope that helps. It's funny ... I have http working just great, but can't
> get anything ELSE to work! you're the exact inverse of my problem. (big
> laugh) Although, I have not been able to get https to work correctly.
did you read the part in the HOWTO on https about setting up the certificates
properly?
(This also wasn't obvious to me).
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
