Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Dr. DOT on
Running 6.14
I added a new domain in domain access. I updated my httpd.conf file with the new virtual host and restarted apache. I get a 404 error. So I hopped in the server and looked in the /sites directory and was expecting to see a reference to the new domain I setup.
Does Domain Access automatically create my server directories or do I need to do that manually?
Is there documentation what walks you through the steps to setup a new domain in D.A.?
Comments
Solved
Ok, the problem ended up being that the DocumentRoot setting in my httpd.conf file for the VirtualHost was set to /../../drupal/ because I was thinking I needed to set the DocRoot right into Drupal. Yet when I stared at the URL it was pointing to http://mydomain.com/drupal/?q=content/the-page-i-created. So, in essence, the page that was trying to resolve was /../../drupal/drupal/. I ended up removing the /drupal directory from the URL and the page resolved. Since I published the test page across multiple shared domains that I setup in the Domain Access, I was able to revolve the same page under another Domain.
So I am beginning to see how D.A. works.
MOTS = be careful with the DocumentRoot setting in httpd.conf relative to the URL address in your browser.
Note
For the record, Domain Access itself does nothing to your server configuration or DNS. You must do that yourself.
You are correct Ken. I wasn't
You are correct Ken. I wasn't real clear in my post. I manually set my DocumentRoot in the httpd.conf file to /path_to_web_root/drupal/ when I could have actually just set it to /path_to_web_root/. Then the URL could continue resolve to http://domain.com/drupal/ -- either way you need to sync your DocumentRoot in the tag in the httpd.conf file to the Druapl URL pattern to make it work.