Set up Named Based Virtual Hosting on 10.4 Server

First, sorry for the stupid question. I've read through Apple's WebTechnologies_Adminv10.4/10.5 manuals and still don't feel like I have a clear answer to this question.
I am trying to set up named based Virtual Hosting on an Xserve running 10.4. I have read a lot of instructions on the web on setting up named based virtual hosting on Mac 10.4/5 Client computers by manually adjusting the host and httpd.conf files and I'm confused as to whether I need to do this in 10.4 Server as well. I have successfully set up virtual hosting on a client computer and it works but I can't get it to work on 10.4 server. I have set up two sites in Server Admin with two site folders in /library/webserver/documents but no luck. Do I need to do what I did in the files above on the server to get it to work or should it work by just creating seperate sites in Server Admin? What am I missing? Thanks in advance for any guidance.

You can do this entirely in Server Admin - no need to edit the config files directly.
You just need to create each site in Server Admin -> (server) -> Web -> Sites
For each set you need to specify the hostname for the site in each site's Domain Name field.
As long as each site has a unique name (and that name maps to your server's IP address) that's all there is to it.

Similar Messages

Apache, name based virtual hosts and multiple servers.

Hi,
Ive been playing with Apache and name-based virtual hosts for a while now, but, ive been doing it with one single server... now i have the need to forward a name-based request to another server inside the intranet (wich doesnt have a public IP, but a private)...
Something like this:
internet -----> Webserver (name based vhosts) ----> intranet-webserver
Where "webserver" has several domains resolved via name based virtual hosting, and one of those needs to be redirected (or forwarded) to another server on the LAN.
Any ideas on how to do this? i tryed searching the web, but i dont know under which keywords, so i always end on single server virtual hosting help sites.
thanks in advance!

you need to define a virtual server for it..but inside that definition.. define a proxy.
Then the middle webserver, will actually handle the request to the intranet server, on behalf of the internet client..and then pass the traffic to the internet client.
this looks like a reasonable example..
http://www.linuxfocus.org/English/March … le147.html
namely, the section "Mapping Virtual Servers"

Using Name-based Virtual Hosts on Apache

Hi!
We have Novell SBS 6.5, a tree with 3 servers:
1. Border Manager sp1
2. GroupWise (NAT) sp1
3. WEB (NAT) sp6 - Apache 2, MySQL, PHP.
My site is at http://www.kalmanovitz.co.il.
I want to try to add a new sub domain and\ or a Domain using Name-based Virtual Hosts (2 or more domains on same IP number).
1. My BM server use SSL. Will it influence SSL? How?
2. What I need to change on my servers?
3. What my ISP need to update\change on his system?
4. Can i try to experience the changes without my ISP intervention?
Please help.
TIA
Nanu

Nanu Kalmanovitz,
> 1. My BM server use SSL. Will it influence SSL? How?
Not protocol wise, but you will get asecurity warning that certificate
and host names do not match.
> 2. What I need to change on my servers?
Httpd.conf
> 3. What my ISP need to update\change on his system?
DNS, pointers to the domains
> 4. Can i try to experience the changes without my ISP intervention?
>
Yes. Add the names to the workstation's hosts-file
- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
Using VA 5.51 build 315 on Windows 2000 build 2600

Virtual Hosts in Apache HTTP Server

How to configure virtual hosts in Apache HTTP Server httpd.conf file.
If I want to access my server with some other name(alias), how can I do this ?
Suggestions in this matter would be highly helpful.
Thanks
Vidhyut Arora

Following is a note explaining how to setup
Virtual hosts.
Hope this helps
Ranga
Note:70647.1
Subject: Apache Server Virtual Hosting
Last Revision Date: 07-JUN-2001
PURPOSE
This document discusses considerations for setting up virtual hosts on an
Apache machine, to include how to get the hostname working and how to
configure Apache.
SCOPE & APPLICATION
The information in this document is intended for those who manage multiple sites
using an Apache machine.
REFERENCES
First published in Apache Week issue 31 (6th September 1996)
Last update 20th September 1998
Using Virtual Hosts
Virtual Hosts let you run multiple independent Web sites on a single host with
a single Apache setup.
One of the most important facilities in Apache is its ability to run virtual
hosts. This is now the essential way to run multiple Web services - each with
different host names and URLs - that appear to be completely separate sites.
This is widely used by ISPs, hosting sites and content providers who need to
manage multiple sites but do not want to buy a new machine for each one.
Picking an IP address
There are two types of virtual hosts: IP-based and non-IP-based. The former is
where each virtual host has its own IP address. You must have a new IP address
for each virtual host you want to set up, either from your existing allocation
or by obtaining more from your service provider. When you have extra IP
addresses, you tell your machine to handle them. On some operating systems, you
can give a single ethernet interface multiple addresses (typically with an
fconfig alias command). On other systems, you must have a different
physical interface for each IP address (typically by buying extra ethernet
cards).
IP addresses are a resource that costs money and are increasingly difficult to
get, so modern browsers can now also use 'non-IP' virtual hosts. This
lets you use the same IP address for multiple host names. When the server
receives an incoming Web connection, it does not know the hostname that was used
in the URL. However, the new HTTP/1.1 specification adds a facility where the
browser must tell the server the hostname it is using, on the Host: header. If
an older browser connects to a non-IP virtual host, it does not send the Host:
header, so the server must respond with a list of possible virtual
hosts. Apache provides some help for configuring a site for both old and new
browsers.
Picking a Hostname and Updating the DNS
Having selected an IP address, the next stage is to update the DNS so that
browsers can convert the hostname into the right address. The DNS is the system
that every machine connected to the internet uses to find the IP address of host
names. If your hostname is not in the DNS, no one can connect to
your server (except by the unfriendly IP address).
If the virtual hostname you are going to use is under your existing domain,
you can just add the record into your own DNS server. If the virtual hostname
is in someone else's domain, you must get them to add it to their DNS
server files. In some cases, you want to use a domain not yet used on the
internet, in which case you must apply for the domain name from the
InterNIC and set up the primary and secondary DNS servers for it, before adding
the entry for your virtual host.
In any of these cases, the entry you need to add to the DNS is an address record
(an A record) pointing to the appropriate IP address. For example, say you want
the domain www.my-dom.com to access your host with IP address 10.1.2.3: you
must add the following line to the DNS zone file for my-dom.com:
www A 10.1.2.3
Now, users can enter http://www.my-dom.com/ as a URL in their browsers and get
to your Web server. However, it will return the same information as if the
machine's original hostname had been used. So, the final stage is to tell Apache
how to respond differently to the different addresses.
How Apache Handles Virtual Hosts
Configuring Apache for virtual hosts is a two-stage process. First, it needs
to be told which IP addresses (and ports) to listen to for incoming Web
connections. By default, Apache listens to port 80 on all IP addresses of the
local machine, and this is often sufficient. If you have a more complex
requirement, such as listening on various port numbers, or only to specific IP
addresses, then the BindAddress or Listen directives can be used.
Second, having accepted an incoming Web connection, the server must be
configured to handle the request differently, depending on what virtual host it
was addressed to. This usually involves configuring Apache to use a different
DocumentRoot.
Telling Apache Which Addresses to Listen To
If you are happy for Apache to listen to all local IP addresses on the port
specified by the Port directive, you can skip this section. However, there are
some cases where you want to use the directives explained here:
- If you have many IP addresses on the machine but only want to run a Web
server on some of them
- If one or more of your virtual hosts is on a different port
- If you want to run multiple copies of the Apache server serving different virtual
hosts
There are two ways of telling Apache what addresses and ports to listen to:
- Use the BindAddress directive to specify a single address or port
- Use the Listen directive to any number of specific addresses or ports
For example, if you run your main server on IP address 10.1.2.3 port 80, and a
virtual host on IP 10.1.2.4 port 8000, you would use:
Listen 10.1.2.3:80
Listen 10.1.2.4:8000
Listen and BindAddress are documented on the Apache site.
Configuring the Virtual Hosts
Having gotten Apache to listen to the appropriate IP addresses and ports, the
final stage is to configure the server to behave differently for requests on
each of the different addresses. This is done using <VirtualHost> sections in
the configuration files, normally in httpd.conf.
A typical (but minimal) virtual host configuration looks like this:
<VirtualHost 10.1.2.3>
DocumentRoot /www/vhost1
ServerName www.my-dom.com
</VirtualHost>
This should be placed in the httpd.conf file. You replace the text
10.1.2.3 with one of your virtual host IP addresses. If you want to specify a
port as well, follow the IP address with a colon and the port number
(example: 10.1.2.4:8000). If omitted, the port defaults to 80.
If no <VirtualHost> sections are given in the configuration files, Apache
treats requests from the different addresses and ports identically. In terms of
setting up virtual hosts, we call the default behavior the main server
configuration. Unless overridden by <VirtualHost> sections, the main server
behaviour is inherited by all the virtual hosts. When configuring virtual
hosts, you must decide what changes to make in each of the virtual
host configurations.
Any directives inside a <VirtualHost> section apply to just that virtual host.
The directives either override the configuration give in the main server, or
supplement it, depending on the directive. For example, the DocumentRoot
directive in a <VirtualHost> section overrides the main server's DocumentRoot,
while AddType supplements the main server's mime types.
Now, when a request arrives, Apache uses the IP address and port it arrived on
to find a matching virtual host configuration. If no virtual host matches the
address and port, it is handled by the main server configuration. If it does
match a virtual host address, Apache uses the configuration of that virtual
server to handle the request.
For the example above, the server configuration used is the same as the
main server, except that the DocumentRoot is /www/vhost1, and the
ServerName is www.my-dom.com. Directives commonly set in <VirtualHost>
sections are DocumentRoot, ServerName, ErrorLog and TransferLog. Directives
that deal with handling requests and resources are valid inside <VirtualHost>
sections. However, some directives are not valid inside <VirtualHost> sections,
including BindAddress, StartSevers, Listen, Group and User.
You can have as many <VirtualHost> sections as you want. You can
leave one or more of your virtual hosts being handled by the main server, or
have a <VirtualHost> for every available address and port, and leave the main
server with no requests to handle.
VirtualHost sections for non-IP Virtual Hosts
Non-IP virtual hosts are configured in a very similar way. The IP address that
the requests arrive on is given in the <VirtualHost> directive, and the
host name is put in the ServerName directive. The difference is that there
(usually) is more than one <VirtualHost> section handling the same IP address.
For Apache to know whether a request arriving on a particular IP
address is supposed to be a name-based requests, the NameVirtualHost directive
addresses for name-based requests. A virtual host can handle more than one
non-IP hostname by using the ServerAlias directive, in addition to the
ServerName.
null

ORMI Connect Exception with IP-Based Virtual Hosts

I currently am using OAS 10.1.2 and have a virtual host setup with the Oc4j mounted at the root of the domain.
i.e.
http://mydomain.com (Takes you straight to the application)
as apposed to
http://mydomain.com/myapplication (Which appears to be the default configuration)
When I setup my ormi url to the following ormi://mydomain.com:12500/ I get java.net.ConnectException: Connection refused. error.
If remove the Virtual Host configuration then specify the ormi url to be ormi://mydomain.com/myapplication I do no get the error.
Does anyone know how to setup ormi with oc4j applications mounted to the root of a domain.
Thanks

you need to define a virtual server for it..but inside that definition.. define a proxy.
Then the middle webserver, will actually handle the request to the intranet server, on behalf of the internet client..and then pass the traffic to the internet client.
this looks like a reasonable example..
http://www.linuxfocus.org/English/March … le147.html
namely, the section "Mapping Virtual Servers"

Using SSL with Apache Virtual Hosts

I am configuring Apache to use 3 virtual Host(Named base virtual Host).
I would like to run SSL on two of the 3 virtual host.
Do I need to gen a certificate for each virtual host or can I just use 1?

William,
I thought I'd give my 2 cents on this...
Is there any particular reason as to why you are using named based virtual hosts?
Apache recommends using IP based virtual hosts over name based virtual hosts.
Go to http://httpd.apache.org/docs/dns-caveats.html and read the discussion on IP based virtual hosts and name based virtual hosts. The document describes the drawbacks to using the name-based approach.
Hope this helps!
-Manjeet

Weblogic, Apache and Virtual Hosts

Hello,
I have apache set for name-based Virtual Hosting (I'm serving 2 domains from the
same IP) and am running into the following problem:
Even though DOMAIN 2 has its own document root specified in the Apache httpd.conf
file, that is different than the document root for DOMAIN 1, both URLs are serving
up the same index.jsp from WebLogic (v. 5.1).
If I change the httpd.conf entry for DOMAIN 2, to serve up index.html instead
of index.jsp, it works????
Is there some setting I need in weblogic.properties???
Any help would be appreciated!!
Thanks,
Mark Mangano

Hello,
I have apache set for name-based Virtual Hosting (I'm serving 2 domains from the
same IP) and am running into the following problem:
Even though DOMAIN 2 has its own document root specified in the Apache httpd.conf
file, that is different than the document root for DOMAIN 1, both URLs are serving
up the same index.jsp from WebLogic (v. 5.1).
If I change the httpd.conf entry for DOMAIN 2, to serve up index.html instead
of index.jsp, it works????
Is there some setting I need in weblogic.properties???
Any help would be appreciated!!
Thanks,
Mark Mangano

Setting Up Virtual Hosts

Presently I've got Mountain Lion and Mountain Lion Server.app running and successfully hosting a live website. I've got mail running fine and profile manager, but I've not yet been able to figure out how to host a secondary site on a subdomain of my primary domain (though I suppose www is technically a subdomain).
I'm guessing the main thing I don't understand is if I need a secondary Primary Zone and other DNS settings requirements. Also, anything else I need to do inside Server.app and possibly any items that need to be taken care of in Terminal. I sure wish someone was doing tutorials that went beyond the inital domain out there, but I'm not seeing them.
I just need the steps to walk through, or a link to a tutorial, that I could use.
Thanks in advance!!!

Yes, www.example.com needs a translation that leads to an IP address, as does xyz.www.example.com.
Here's a writeup on DNS on OS X Server and here's one on Apache virtual hosting on OS X Server.
There are a number of ways to set up internal DNS — I'm here assuming you're using NAT — and external DNS.
In general, I'd recommend using one registered domain inside and another registered domain outside, and a firewall that can "reflect" references to your external IP address back into your internal network. This means you can maintain your internal (private) DNS completely separately from external (public) DNS.
But read the articles above and see if you understand a bit better — or if you should have questions on either, ask away.

Setting up multiple web sites (virtual hosting).

Dear members:
I am considering OS X Server for a personal project and would like some advice to help me decided what route to take.
My computer will soon be turned into a server hosting my web sites and some other services at my home office. I am thinking about OS X Server as I have done some research and found OS X to require quite a bit of work so that it can do virtual hosting.
How simple is it to configure virtual hosting in OS X Server ? I am considering the latest Leopard version in case it matters. I am not experienced and wish to employ an application that will simplify this process.
Any help will be very appreciated.
Thank you,
Joseph Chamberlain

You could create local PAC file <http://findproxyforurl.com/pac_file_examples.html> where you can return multiple PROXY servers. You would create text file with your PAC script in it. Then specify System Preferences -> Network -> Advanced -> Proxy -> Automatic Proxy Configuration, and click "Choose File".
If you choose to take BDAqua's advice and create multiple Network Locations, you can then use either
/usr/sbin/networksetup -switchtolocation "MyCompanysProxy1"
/usr/sbin/networksetup -switchtolocation "MyCompanysProxy2"
/usr/sbin/networksetup -switchtolocation "MyCompanysProxy3"
or
/usr/sbin/scselect "MyCompanysProxy1"
/usr/sbin/scselect "MyCompanysProxy2"
/usr/sbin/scselect "MyCompanysProxy3"
you can put them into a script of your choosing. Shell script, or Automator Run Shell Scirpt, or Applescirpt do shell script (or Perl, Python, Ruby, etc...)

Apache virtual host with OSX Server?

I have been running OSX Server for a while now, and just recently I decided to get McMyAdmin for my Minecraft server. The web client for McMyAdmin runs on port 8080, but I wanted it on port 80. I wanted to use it with my domain, so I just created a sub domain and pointed it to my server. The problem is that OSX Server apparently doesn't let me use port 80, even when websites are turned off. I decided to delete Server and just use plain apache. This worked until I realized that my website was only accessible locally. I have all the correct ports forwarded, etc. But I get the error:
Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.
when I try to connect from outside my network. This is probably just some simple thing I missed but it would be nice if someone could just point out what I did wrong here. Back to the point, I want to know how to run the proxy to my web client on port 8080 AND ALSO run OSX Server with or without apache virtualhost.
Thanks in advance,
Eamon

Web is stupidly easy - Apache has extensive support for multiple virtual hosts in a single server and will happily support as many domains/hostnames as you can throw at it.
Mail is a little trickier since it needs to hook into some kind of directory server to validate user addresses.
Mac OS X's Open Directory does support this, but it's a little cumbersome (basically every user has to exist in the main Open Directory domain as well as having a secondary email address(es) in the other domain(s).
This can get especially tricky when you have users with the same shortname in different domains - for example if you give [email protected] a secondary email address of [email protected] and you then get a new user [email protected], you can't give the third 'joe' the address 'joe' in Open Directory since that's already taken. This means he'll have to login using different credentials from his email address. Confused yet? You bet.
If you're prepared to eschew Open Directory you can just use Postfix's built-in support for virtual hosting, but it's a little more complex to setup and support and is entirely command-line based (i.e. there's no GUI for setting it up or supporting it).
So, for that reason you might be prepared to setup multiple virtual machines for each domain. It really depends on how much the domains are related (if at all).

How to create and access a Virtual Host on the J2EE WAS?

Hello, I have searched through the Forums and help.sap.com and found a lot of information on how to set up a Virtual Host on the J2EE server but am having issues with it working.
The goal is to provide a simple virtual host on the J2EE Portal server to host some static image and HTML files. Previously I had stored these files in the standard publicly accessible SAP J2EE folder location /usr/sap/<SID>/JCxx/j2ee/cluster/serverx/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/. This location is resolved to when using the URL <host>:50000 for example.
The main issue here is that during Portal support pack applications this folder gets wiped out and we have to remember to save off any custom files and folders in this location and replace them.
I would like to create a virtual host to store these static files (i.e., branding-image.jpg, etc...).
I have run through the process of creating the virtual host both using Visual Administrator and <host>:50000/nwa but am not able to get the virtual host name to resolve properly.
The following are the steps that I have taken. Let's assume the standard SAP portal (i.e., xSS, etc...) is running properly on <host>:50000.
1. create virtual host via Visual Administrator/NWA called 'sapwebserver1' by using the Create Host option (takes on the attributes of the 'default' standard virtual host)
2. change the root directory for this virtual server to a custom folder at E:/tmp/mimes (where E:/usr is where the J2EE files are all installed), no start files were set up and nothing else was changed in the new virtual host record, no permissions were changed on the /tmp/mimes folder from whatever the default Windows user permissions are normally set, I am using a local Windows administrator account but I have not seen any reference in the help files or the examples that indicate that any specific permissions updates need to be made on the virtual host root folder
3. restarted the J2EE server as well as the HTTP Provider service
4. before updating the company DNS, I wanted to test this locally on the server and so have updated the server's local HOSTS file with a <host IP address> sapwebserver1 entry
5. from that server I can ping the sapwebserver1 virtual host name and it resolves properly to the machine's physical IP address
According to all of the documentation and examples I have seen I should now be able to (from that server) launch a browser and access the static files in the virtual host by referring to http://sapwebserver1:50000/branding-image.jpg for example. This is not working and the browser just brings up a Cannot display the web page error in IE. By referring to the virtual host name sapwebserver1:50000 it's supposed to hit the J2EE server and based on the host name sapwebserver1 realize that it should resolve to the root directory E:/tmp/mimes. This is not happening. Just as a test I have created a copy of the 'default' virtual host and called it sapwebserver2, updated the local HOSTS file for this entry, and tried to see if that would work like the 'default' host. My expectation was that http://sapwebserver2:50000 would behave the same was as http://<host>:50000 but it too fails to resolve just like the sapwebserver1 virtual host refernce.
Would anyone happen to have any pointers on what to do next? I just want a simple virtual host to be able to serve up some static images and files.
Thanks for any insight or assistance you might be able to provide here.
Graham

This defeats the purpose of trying to centralize SAP-related web resources on the SAP server. Typically IIS/Apache or other non-SAP servers are under the control of IT and not the SAP BASIS group.
We simply would like to have a centralized location to store static web files so that they are not overwritten during Portal support pack applications.

The essential guide to DW cs4... by D. Powers: when from wamp to xampp+virtual host and having problems :(

Following the book in chapter 2 I think Ivé followed everything correctly, but have encluded all the things I've edited below.
I was using wamp with no problems but after trying to set up a virtual host and now using xampp im abit lost its probabsomething stupid but I can find the prob.
(This post is abit long and dragged out so I used some colour to try ease the reading..)
When I try to view a dynamic page in live view or in firefox I get the following error:
**when using:
<VirtualHost *:80>
DocumentRoot c:/xampp/htdocs
ServerName localhost
</VirtualHost>
result:
Access forbidden!
You don't have permission to access the requested object.     It is either read-protected or not readable by the server.
If you think this is a server error, please contact the webmaster.
Error 403
thegoodlife
2009/10/13 12:47:48 PM
Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
*when using:
<VirtualHost *:80>
DocumentRoot c:/htdocs
ServerName localhost
</VirtualHost>
result:
Object not found!
The requested URL was not found on this server.          If you entered the URL manually please check your     spelling and try again.
If you think this is a server error, please contact the webmaster.
Error 404
thegoodlife
2009/10/13 12:32:58 PM
Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
This is what I've done, blue indicating where I have or was meant to edit, red being the relivant context. (hope it helps )
1. Created a new folder called htdocs (C:\htdocs)
2. Changed the pathname to:
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "C:/htdocs"
and
# This should be changed to whatever you set DocumentRoot to.
<Directory "C:/htdocs">
3. Created vhosts folder; with a sub-folder called thegoodlife (C:\vhosts)
4. entered new vhost:
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
127.0.0.1 localhost
127.0.0.1 dwcs4
127.0.0.1 thegoodlife
127.0.0.1 bin.errorprotector.com ## added by CiD
5.It says uncomment the command by removing the #, (Supplemental configuation.), but this is the origional file; already uncommented?
# Real-time info on requests and configuration
Include "conf/extra/httpd-info.conf"
# Virtual hosts
Include "conf/extra/httpd-vhosts.conf"
# Distributed authoring and versioning (WebDAV)
Include "conf/extra/httpd-dav.conf"
6.Set the permissions and changed the code as instructed, unsing (c:/xampp/htdocs) as advised.
# You may use the command line option '-S' to verify your virtual host
# configuration.
<Directory C:/vhosts>
Order Deny,Allow
Allow from all
</Directory>
# Use name-based virtual hosting.
##NameVirtualHost *:80
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
<VirtualHost *:80>
DocumentRoot c:/xampp/htdocs
ServerName localhost
</VirtualHost>
<VirtualHost *:80>
DocumentRoot c:/vhosts/dwcs4
ServerName dwcs4
</VirtualHost>
<VirtualHost *:80>
DocumentRoot c:/vhosts/thegoodlife
ServerName thegoodlife
</VirtualHost>
Then creating the site definition:
local root forlder: C:\htdocs\thegoodlife\
testing server folder: C:\vhosts\thegoodlife\
URL prefix: http://thegoodlife/
hope i've covered all area's where I could have gone wrong

Just one more thing - the description of what i did while first Kernel appeared:
Happened 2 days ago. Wasn't turning it off for like a day, only sleep mode by closing it. Worked fine all day, wasn't doing anything, except for checking mail 2-3 times and having windows 7 virtual machine opened but doing nothing, everything was going fine. Then closed it without turning off.
Opened 3-4 hours later, everything was working fine for 30 minutes of checking mail, then Kernel appeared. After that pretty much everything i did is described in part 1-5.
Note: all the time MBP was connected to internet via wifi, so updates to both MBP and virtual machine of all programs were possible.
I only shared downloads and desktop folders, so windows couldn't have access to system folder of Mac Os.
Hope this might help...Thanks again.

Virtual hosts in apache defaults to first host

On my MacMini I have set up apache to use virtual hosts I and use a mounted USB drive to host the sites (in my case /Volumes/Work1/www as root). I have configured 3 sites and switch on the subdomain (in my case and in order in the virtual hosts file: hbc1.helsted.net, consulting.helsted.net, store.helsted.net).
On the MacMini I have inserted the urls in the hosts file to point at localhost for two of the entries and all work beautifully on the MacMini for those two. Anywhere else (and from the MacMini on the one not in the hosts file) the system defaults to the first entry in the virtual hosts config file (as the documentation says it will if the url is not recognized) which is displayed in the browser and which has entries in the log file.
After some time the server occasionally refuses to serve the pages and I get a 403 error (access denied). Again not on the MacMini with the hosts file entries. Looking at the error log from apache in that case it appear that it has got the full url served as it is in the log file.
Restarting the web share removes the 403 error (until next time).
Any hints on how to to resolve my two issues?

Thanks for the reply, my vhosts config file contains the following (note that the viewer in the forum browser removes the initial #es on the comment lines):
# Virtual Hosts
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
# Please see the documentation at
# <URL:<a class="jive-link-external-small" href="http://">http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
# You may use the command line option '-S' to verify your virtual host
# configuration.
# Use name-based virtual hosting.
NameVirtualHost *:80
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/hbc1"
ServerName hbc1.helsted.net
ErrorLog "/private/var/log/apache2/hbc1.helsted.net-error_log"
CustomLog "/private/var/log/apache2/hbc1.helsted.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/consulting"
ServerName consulting.helsted.net
ErrorLog "/private/var/log/apache2/consulting.helsted.net-error_log"
CustomLog "/private/var/log/apache2/consulting.helsted.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/store"
ServerName store.helsted.net
ErrorLog "/private/var/log/apache2/store.helsted.net-error_log"
CustomLog "/private/var/log/apache2/store.helsted.net-access_log" common
</VirtualHost>
<Directory /Volumes/Work1/www>
Options Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
Message was edited by: skhelsted

Creating Virtual Hosts in Weblogic 8.1

How to create Virtual Host in WLS 8.1
(i.e) , if i type WWW.myapplication.com, the WLS8.1 should fetch the page........

Use the Administration Console to define a virtual host.
Create a new Virtual Host.
Expand the Services node in the left pane. The node expands and displays a list of services.
Click the virtual hosts node. If any virtual hosts are defined, the node expands and displays a list of virtual hosts.
Click Create a New Virtual Host in the right pane.
Enter a name to represent this virtual host.
Enter the virtual host names, one per line. Only requests matching one of these virtual host names will be handled by the WebLogic Server instance or cluster targeted by this virtual host.
Click Create.
Define logging and HTTP parameters:
(Optional) Click on the Logging tab and fill in HTTP access log attributes (For more information, see Setting Up HTTP Access Logs.)
Select the HTTP tab and fill in the HTTP Parameters.
Define the servers that will respond to this virtual host.
Select the Targets --> Servers tab. You will see a list of available servers.
Select a server.
Click Apply.
Define the clusters that will respond to this virtual host (optional). You must have previously defined a WebLogic Cluster. For more information, see Using WebLogic Server Clusters.
Select the Targets tab.
Select the Clusters tab. You will see a list of available clusters.
Select a cluster.
Click Apply.
Target Web Applications to the virtual host.
Click the Web Applications node in the left panel.
Select the Web Application you want to target.
Select the Targets tab in the right panel.
Select the Virtual Hosts tab.
Select Virtual Host.
Click Apply.
You must add a line naming the virtual host to the etc/hosts file on your server to ensure that the virtual host name can be resolved.

WAS and multiple virtual Host

I am currently evaluating Oracle WAS on Linux.
It works fine except if I try to have Spyglass serve more than
one virtual host. When I do this it stops with an Internal error
after serving a few files.
Q. Does anyone have Spyglass serving for more than one virtual
host on the same port.
Q. What could be the problem
I use RH 5.1
Johnny Verhoeven
null

Web is stupidly easy - Apache has extensive support for multiple virtual hosts in a single server and will happily support as many domains/hostnames as you can throw at it.
Mail is a little trickier since it needs to hook into some kind of directory server to validate user addresses.
Mac OS X's Open Directory does support this, but it's a little cumbersome (basically every user has to exist in the main Open Directory domain as well as having a secondary email address(es) in the other domain(s).
This can get especially tricky when you have users with the same shortname in different domains - for example if you give [email protected] a secondary email address of [email protected] and you then get a new user [email protected], you can't give the third 'joe' the address 'joe' in Open Directory since that's already taken. This means he'll have to login using different credentials from his email address. Confused yet? You bet.
If you're prepared to eschew Open Directory you can just use Postfix's built-in support for virtual hosting, but it's a little more complex to setup and support and is entirely command-line based (i.e. there's no GUI for setting it up or supporting it).
So, for that reason you might be prepared to setup multiple virtual machines for each domain. It really depends on how much the domains are related (if at all).

Set up Named Based Virtual Hosting on 10.4 Server

Similar Messages

Maybe you are looking for