Site crashes after enabling the module

Misconfigured host files is the likely issue. I cannot help you troubleshoot this on Windows.

If it helps, Windows' hosts file lives at

C:\Windows\System32\drivers\etc\hosts

First of all, thanks for creating this module and for providing so much support for it. You seem to be updating it and providing support quite regularly.

Unfortunately, I am having the same issue with version 5.x-1.6 on Linux.

I was trying to set up siteadmin.example.com as the base domain because example.com is already in use for something else. The other sites will just be at other subdomains, e.g. one.example.com, two.example.com, etc. In the DNS I created A records for each subdomain and pointed them to the IP address for the server where Drupal is installed. Then I set up virtual host configuration files for siteadmin.example.com and several of the other subdomains.

Here is a sample of the virtual host configuration file:

<VirtualHost 172.21.0.10:80>
    ServerAdmin webmaster@example.com
    ServerName siteadmin.example.com


    DocumentRoot /srv/www/vhosts/siteadmin


    # Logs are also separated out by market and station name
    ErrorLog    "|/usr/sbin/rotatelogs2 /var/log/apache2/Corp/siteadmin.example.com/error_log.%Y%m%d 10M"
    CustomLog   "|/usr/sbin/rotatelogs2 /var/log/apache2/Corp/siteadmin.example.com/access_log.%Y%m%d 86400 -480" combined

    HostnameLookups Off
    UseCanonicalName On
    ServerSignature On

    Include /etc/apache2/conf.d/rewritetoiis.special

    <Directory "/srv/www/vhosts/siteadmin">
    Options Indexes FollowSymLinks
    AllowOverride All
    Order allow,deny
    Allow from all
    </Directory>

</VirtualHost>

I had the same experience as vinod.jain: I set up a fresh installation, enabled clean URLs, and the site seemed to be fine. Then, I enabled the Domain Access module, and I just saw a blank page. Oddly enough, my browser took me to http://admin/build/modules instead of http://siteadmin.example.com/admin/build/modules .

After trying to muddle my way through the Apache documentation, ( http://httpd.apache.org/docs/2.2/vhosts/name-based.html ), I decided to declare a NameVirtualHost in the siteadmin.example.com.conf file. I commented out:

# <VirtualHost 172.21.0.10:80>

and added:

NameVirtualHost *:80
<VirtualHost *:80>

to the top of the file. After restarting Apache, http://siteadmin.example.com/admin no longer redirected me to http://admin ... instead it gave me a 404 error.

While I was still logged in as administrator, I found that I could also browse to http://siteadmin.example.com/?q=admin and at least get the HTML portion of the page. The path to external files (images and CSS) did not seem to be getting set correctly, however.

Does it seem as though I am misconfiguring the virtual host? Or could something else be the problem? Any suggestions you can provide would be a huge help. Thanks! I am really excited to use this module!

My configuration:
Drupal 5.10, MySQL 5.0.26, Apache2.2.3, DomainAccess 5.x-1.6 on Linux/SUSE

I can confirm I am having an almost identical issue.

I am running 5.10 and the latest stable release of domain access.

Running WAMP on XP. VHOSTS seems to be set up fine, as domains resolve perfectly.

The only different thing that has happened to me, is that whenever I try to enable it hangs. Then, as with the OP every page is white.

I have looked under watchdog in the databse and found over a thousand entries for:

Duplicate entry '1-0-domain_site' for key 1
query: INSERT INTO domain_access (nid, gid, realm) VALUES (1, 0, 'domain_site') in C:\Program Files\wamp\www\enj\includes\database.mysql.inc on line 172.

This would explain why it's hanging, but not why it's doing this. Im not really sure how to proceed in debugging this, I doubt it is a problem with the module, so I'm left wondering if I've done something wrong.

NOTE: This is on a local test copy of a site I have running live currently.

NOTE: This happens regardless of what modules I enable at the same time, or if I only enable domain access.

danobrienmuzyka: Your problem seems to be the same as what I mention in this issue. I've provided a patch, but it's for the D6 version of the module; still, if you know your way around PHP, you may want to try making the tweak in the patch yourself and seeing if it fixes things.

This is what happens when other people don't test patches!

It looks like #293453: Wildcard DNS - default domain broke this. BUT NO ONE TESTED IT.

See #300311: Fresh installation causing nasty problems.

For now, comment out line 63 domain.module:

      drupal_set_message(t('You have followed an incorrect link to this website.  Please update your links and bookmarks to <a href="!url">!url</a>.', array('!url' => $request)));
   #   drupal_goto($request);

This is fixed in 6.x.1.1 and 5.x.1.7.

The other patches need testing -- lack of testing is what caused this issue.

See #298696: * ROADMAP * Please read this first for a list of current patches that "need review."

Or see http://drupal.org/project/issues/domain?projects=99990&states=8

Ideally, each point release is stable, and does not require patches. That is why we had 5 release candidates before 6.x.1.0. That is also why I sound so angry in this thread.

Thank you so much for fixing this in version 5.x-1.7! I am so excited to start using this module!